Multiple issue types + workflows vs. Single issue type + workflow + validations Edited

I've created an issue type that contains a single choice field (values urgent or planned) and based on which value the user chooses, it enables certain transitions in the workflow, namely an "urgent" issue skips QA validation. This actually means skipping 7 out of a 12 statuses workflow. Also, certain fields won't be mandatory either (not marked as required in the field config, but validated at a certain status transition).
But I'm hesitating about pushing this change forward or proposing a new one:
- Why not having 2 issue types, "Urgent" and "Planned", with their own screens (mandatory fields configured accordingly), with their own workflows, which wouldn't have validations now.
I find that having multiple simpler workflows are easier to maintain than a more complex workflow, with validations.
Can I have your 2 cents on this?
Cheers,
Luis

0 comments

Comment

Log in or Sign up to comment
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

26,286 views 2 7
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