The new JIRA experience has proven to be disruptive in the way we do business. It now tries to simplify boards by assuming that all issue types should have the same workflow but that is not tied to real life.
We have an internal Marketing project which has several different issue types. Within our team, we have marketing specialists, designers, and developers. Why should a design issue have the same workflow as a content development issue?
I sense that this new JIRA experience has more to do with Atlassian's attempt to try and capitalize on different scenarios and nothing to do with actually providing a better experience for their users. In doing this, JIRA will lose its strongest advantage, its ability to fit within any business workflow!
Atlassian, do not tempt me to look elsewhere for an application that will allow me to stay in control of my business!
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot