Does anyone know if it is possible to create a monday.com board, as a form, that can capture an item description (on the form) and display the description as an update (in the conversation), rather than having to add another large text column.
I know the Zendesk integration can do this, when submitting tickets in zendesk the description comes through as an update on the item. But I can’t seem to do it with a monday.com form?
As Matias mentioned, you could use the monday API to do that.
In my opinion, the easiest way to use the API for small tasks like that is with Make. You can find out more about Make here: What is Make & How can it help you?
We will definitely consider to add this to our Extract app (link below) would you be able to share more information about your usecase is it for ticketing? Any other data extraction triggers needed?
Yes our use case is pretty much a ticketing system.
We would like staff to be able to complete a form, which submits a request directly to our Action List board (backlog). The developer team can then review the board in the weekly sprint meetings, prioritise and action the work.
If the form had a description field (allowing the requester to discuss the request/bug in detail), which then came through as an update on the board item that would be great!
It would also be cool if Monday forms had conditional logic, to hide/show/automate different options depending on user selection. For example,
Request type: Bug | New Feature | Question Priority: Urgent (if bug) | Normal (if new feature) | Low (if question)
I’m not sure this solution would work. To me it looks like all items created would have the same update text? The idea is to allow each item to have its own update upon creation, defined by the user creating the item.
@Dazski, not sure if I’m understanding your use case or what you are ultimately trying to achieve other than the item name being included as an update. The automation provided would create an Update on the item with the text that the form submitter entered in the Item Name field. It is a dynamic to each item.
Updates are comments. Like @Dazski, I would much prefer the details of the ticket in the item description like it does for Asana, Hive, Jira, Notion, and every other project management software on the planet. It’s helpful to have some data indexed like status and priority, but steps to reproduce or expected behavior doesn’t exactly fit in a column.