Custom workflows & schemes
Workflow, permission, notification and issue security schemes pile up until nobody understands which one fired.
What people actually say
✕Jira is incredibly easy to over-engineer with too many required fields, rigid permissions and confusing menus — the same flexibility that's a feature becomes the main pain.
Source: G2 — Jira pros and cons ↗✕Jira is a 'tracker construction kit' rather than a ready-to-use tool, forcing teams to build opinions on top of generic abstractions with no documentation.
Source: Hacker News — I fucking hate Jira ↗✕Permission schemes have interdependent rules — to resolve an issue a user needs both Transition Issue and Resolve Issue, and that's before you layer in issue security schemes.
Source: Atlassian docs — Jira permission schemes ↗
Workflow states and transitions live as a typed state machine in your repo — diffable, testable, reviewed in a pull request. No more four overlapping schemes; one TypeScript file describes who can move what, and a CI test fails the day someone breaks it.