I understand that the number "custom fields" plays a factor in the performance of the Jira application.
Does the same apply for statuses?
I am looking to gauge whether my users can "go nuts" and create any number of statuses in their workflows without performance impacts to the system.
Welcome to the Community!
Technically, yes, every status does add overhead. Every different one needs to be indexed, displayed and used by your people.
But their load is insignificant compared with the other things you might have been reading about. A system with 1,000 status won't have a noticable performance degredation from the same system with 10. The impact on your reporting is going to be bigger than the impact on your usage - does it make a lot of sense to have eleventy twelve status that mean "we haven't looked at it yet", when one would do?
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event