As a Jira administrator, you have the power to create order — or total chaos.
Some mistakes may seem harmless at first but can lead to performance issues, broken workflows, and frustrated users. To help you avoid these pitfalls, here’s a list of the worst things you can do in Jira.
Are you guilty of any of these sins? 😈 Let’s find out!
- Creating custom fields with the same name as system ones (e.g. "Summary").
- Creating fields with a global context that are used in no more than a couple of projects.
- Renaming an existing status.
- Not setting a resolution when transitioning to final (mostly green) statuses.
- Not clearing the resolution when exiting a final status (mostly green).
- Renaming the Create transition and changing its event.
- Creating resolutions that aren't resolutions (e.g., "Not Done").
- Running automation rules on a schedule every 5 minutes.*
* - this may be acceptable in rare cases, but in most situations, it is unnecessary.
What do you think? Have you encountered any of these mistakes, or do you have others to add? I’d love to hear your thoughts!
