nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As an System Admin can I shortcut between status?

Jeremy Schrek

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?

Accepted answers

Ste Wright

Hi @Jeremy Schrek

You can't bypass the workflow, even as an Admin, without some additional effort.

I'd think native options are...

Put an additional condition into the Automation Rule - which exempts the action based on user type, or some other exemption (eg. a Label)
Allow issues to be created in any Status. This is a platform-wide setting though, and would apply to all Users and Projects.
- You can activate this setting via Settings > System > General configuration > Edit Settings
Upload these Epics via CSV. As an Admin, you can set the Status in the import

---

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

All comments

Cliff Stovich

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.

MattD_6wbwou

A global transtion to each status from any other status, plus some conditions based on the issue type perhaps?

Ste Wright

Hi @Jeremy Schrek

You can't bypass the workflow, even as an Admin, without some additional effort.

I'd think native options are...

Put an additional condition into the Automation Rule - which exempts the action based on user type, or some other exemption (eg. a Label)
Allow issues to be created in any Status. This is a platform-wide setting though, and would apply to all Users and Projects.
- You can activate this setting via Settings > System > General configuration > Edit Settings
Upload these Epics via CSV. As an Admin, you can set the Status in the import

---

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

John Funk

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud