3 ms·
The workflow thing is why the usual advice with JIRA is to keep to Atlassian-supplied workflows instead of developing your own. The custom workflows are often
by p_l 3y ago
The workflow thing is why the usual advice with JIRA is to keep to Atlassian-supplied workflows instead of developing your own.
The custom workflows are often mandated by clueless managers, and often even if you have clueful JIRA admin they will silently try to fix manager's dumb idea instead of having the manager eat the turd sandwich.
Once, a coworker of mine decided that enough is enough, and decided to implement a workflow exactly as specified by management.
After week or two of totally lost productivity and reporting, system-supplied workflow was returned to and the manager never again tried to play with workflows.
- DrBazza 3y agoAbsolutely this. Useless product managers adding custom fields and values that make zero sense. Developer issues (eg. github issues) aren't the same as helpdesk requests, and aren't the same as customer enquiries. Yet Jira happily smashes them all together.
- vinnymac 3y agoThe UI problems are a symptom that Jira is complex, and they push that complexity onto the user rather than offering a simple product that forces everyone to operate how they recommend you should. The freedom Jira offers managers is not for the benefit of any workplace I’ve ever been. I much prefer every single tool I’ve used that isn’t Jira for this reason.