I would like Asana to have the ability to create a discovery process flow within the Asana application instead of having to rely on an external tool like MIRO, or even MS Visio. I feel this ability would enhance the productivity of the application and perhaps also add the ability to create Workflows from the Process Flow too to enable quick wins and automations.
Big +1 to this. In a tool like JIRA you build a process flow diagram connecting the possible statuses together with transitions, which actually defines which statuses a user can send a task to from any given status (or you can set them all to “from any status”).
This solves 3 issues:
- Creates a visual diagram explaining the process (@Simon_Filmer 's original request above).
- Allows the process designer to actually enforce process by dictating possible status flows, if desired.
- Avoids situations where static process diagrams fall out of sync when processes change because, in this approach, the act of creating the diagram is not an after-thought to document the process, it’s how you actually define the process in the tool.
@cosmo - have you tested the workflow view in projects? It doesn’t fully accomplish the request in the OP (it’s not particularly dynamic visually), but it does kind of mirror what you’re used to in jira (using sections as statuses), albeit with some limitations.
@Stephen_Li - no, I hadn’t tested that out before—thanks for flagging!
Just took a quick look and it seems helpful from an Admin/Setup POV, but doesn’t really explain to an average user the full flow of how things are meant to move through a process and is cluttered with actions for an admin like adding triggers, etc.
Sounds like you’re already familiar including a screenshot from JIRA docs for other people’s benefit:
Workflow view (and Asana generally) is also still missing the ability to enforce process by dictating possible transitions. For example, in the screenshot above tickets cannot move from Closed to Open because those actually need to go to the Reopened status. In Jira, just but drawing the line to connect those statuses (or in this case not drawing it) makes it impossible for the end user to do something we don’t want them to do. No amount of announcements, trainings, re-trainings, reminders, etc will ever get the same level of adoption as simply leveraging the system to prevent errors.
1 Like