It can be easy to create tickets in Jira using company-managed projects. The problem is the people who set up Jira see all of these knobs and buttons and feel like they need to use them. Creating tickets in my department require two things: ticket type, summary. We use procedures, not software to enforce the rules.

Once I finish our migration to Jira, other departments will have different screens that require a few more fields like description. My goal is to keep these to an absolute minimum.

Configuring this stuff is a massive pain in the ass but the day to day use is manageable by creating custom boards and saved searches. A some training and documenting for my team takes care of the rest.

For my coworkers, it’s no more painful than the workarounds needed to make a “simpler” system work. GitLab and Github do fuck-all to support our workflow. Jira allows me to tailor it so both my team and management can understand what’s happening.

I've got to say that this is a problem with relying on the UI itself. When working with a development team I always provide as many options as possible to automate that worklflow.

This might take the form of integrating bitbucket with Jira such that you can assign a commit to a ticket or advance or close a ticket.

A few years ago I was looking at the jira API and managed to dig into the documentation. The result was a small gist which contains some of the harder to figure out actions. Including creating a new ticket.

https://gist.github.com/TheMightyLlama/9427202

Definitely going the GitHub route next time time I'm moved onto a new project. The past two have used Jira and Trello and both are just a continuous source of frustration for me.