Workflow drafts limitations

I was curious why workflow draft editing had these limitations. I've had cases where these changes are big time sinks if a large majority of projects share a workflow (workflow scheme drafts are slow).

The limitations:

* Workflow statuses cannot be deleted.

* If a status has no outgoing transitions (Global transitions are not considered), it cannot have any new outgoing transitions added, regular or global.

With the first limitation, shouldn't it be safe to do this if no issues are using that status?

For the second limitation, I'm not sure why adding a new outgoing transition isn't possible.

 

 

 

1 comment

This limitation is absurd. The reason we share workflows and schemes between projects is to manage them in one place. This eliminates that benefit. Yet another usability crime committed by Atlassian 😫

Comment

Log in or Sign up to comment
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

575 views 25 15
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you