I have an epic workflow that 95% of my epics follow but the 5% can start anywhere along the workflow.
Currently I have the project set up with automation to create tasks for the respective group on the transition of the epic.
So manually going through each step would create tasks that are not needed.
I also do not want to create a transition from every status to every other status and add conditions to those transitions (a lot of work and could cause confusion or accidental moves)
Is there a good solution?
Hi Jeremy,
If you are only creating the children when it transitions to that particular status, then just bypass that one with a new transition and a Condition on it. It's really the simplest way to go. Call the transition name something that is very obvious so mistakes will not happen - USE THIS TRANSITION ONLY MANUALLY or whatever causes you not to miss it.
The only other option is the CSV import and that's way more complicated and time consuming to execute every time.
You can't bypass the workflow, even as an Admin, without some additional effort.
I'd think native options are...
---
I purposely avoided the additional transition option (with a condition limiting the transition to a specific user Group) based on what you said in the question.
This would also require additional logic in the Automation Rule anyway, which I assume is based on Status and doesn't reference the transition itself.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you create your epic via CSV you can create a column in your excel file called "Status" and start the epic in your chosen status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.