I'm a CI/CD engineer who spends more time in Jenkins, GitHub Actions, and terminal windows than I'd like to admit. But like everyone else, I still have to wade through Jira tickets for requirements and approvals.
The new Jira interface is actively slowing my team down. It feels like a regression disguised as a refresh.
* The information density is worse. I need to click or hover to see details that were previously visible at a glance.
* The new "split view" for tickets is jarring and makes it harder to follow a linear workflow. I just want to read a description and the comments in order.
* It feels slower. The old UI wasn't snappy, but this new one adds noticeable lag when switching contexts, which kills flow.
I'm evaluating whether we can push our project management metadata into the repo (via something like `catalog-info.yaml` for Backstage) and keep Jira interaction to an absolute minimum. I'm here to find others who are:
* Automating away tedious UI workflows.
* Building dashboards that pull data from APIs to bypass the frontend.
* Generally applying engineering principles to the mess of project tracking.
If you've found a way to pipe Jira data into a CLI tool or have scripts to bulk edit tickets from a spec file, I want to hear about it. Concrete solutions only, please.
Build once, deploy everywhere