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 Join to comment
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,336 views 14 20
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot