New ask Hacker News story: Ask HN: Are you allowed to configure Jira to suit your team's needs?

Ask HN: Are you allowed to configure Jira to suit your team's needs?
2 by dandare | 2 comments on Hacker News.
This is my third experience with a big corp not allowing me and my team to configure JIRA to support our development process. The things that are usually misconfigured include: limited or unsuitable ticket status workflow, redundant or unsuitable ticket fields, unsuitable ticket types, mandatory fields not being mandatory and vice versa, chaotic Components, meaningless Priority and inability to use templates in ticket descriptions. The excuses I usually hear include: we need to update to a new version first, this would cause a performance issues, other teams like the way it is configured now, or, my all time favourite, JIRA is configured to support project tracking by management, not to support some software development. Misconfigured JIRA leads to all kinds of time waste, including cloning tickets with the correct template, or using fake sprints or labels as buckets for tickets that are ready for grooming, waiting for UX, blocked etc.