When I click the 'back' button, I never know if I'm a) closing the ticket I have in a split screen, b) going back to the search results, or c) going back to Confluence and losing my search results and wondering how I was in Confluence to begin with.
You'd think this would mean there was a healthy market for native client apps using the JIRA API with a more pleasant UI (as there certainly is for Git, e.g.), but strangely not.
At my gig, everyone grumbles about Jira, because it sucks; see above. But, we have workflows built primarily around it with various integrations, and it works for coordinating ~200 folks in a starting-to-get-there "Agile" model.
It is actually the worst for the managers - they spend a surprising amount of time noodling around in Jira to feed the workflows. For individual contributors, it works and isn't too much overhead.
From an administration standpoint, it is OK (we run the on-prem version). More stable than some enterprise monstrosities, but the with occasional problem. The plugin-store-thing is annoying - somehow it manages to entice nearly every new business-side user into asking for some random thing, they usually get what they want, and then they sit unused aside from occasionally breaking things.
It must have gotten a lot of stability improvements since I stopped managing jira clusters a few years ago because, from the ops side of things, JIRA was one of our main "make a cron job that restarts tomcat every night" running jokes at multiple companies over the last decade.
I've also had wonderful (/s) experience with the unicorns in Gitlab but that's another tale.
Most of product teams still don't function with any kind of actual agile process. Many try to fake it by endlessly throwing all of their work into the JIRA agile boards, which constantly have sprints rolling over, and are impossible to track any kind of actual velocity with. On our team we just said screw this and went back to getting things done, and tracking things how we wanted to track them.
Don't even get me started on the nightmare that is JIRA TCM, which my company is currently still stuck with for test case management.
It works alright.
Thanks for putting this into words for me. This is exactly how I feel about Jira. Incompetent middle management automates their micromanaging and enforces bad ideas about how their subordinates should do their jobs.
Is there any other way?
That said, I don't really mind mentioning the ticket in the commit. It's relevant to what one is doing when one makes the commit.
But then I use gerrit at my job, so I don't have room to complain about others' systems.
Not sure if that's better or worse, though.
Let me repeat that.
Your ticketing system is Turing-complete. I don't remember where I heard this first, but someone at my company (at least supposedly) proved it once.
Jira has managed to grow into such a bloated, complex, incredibly pointless piece of software that I've never met someone who likes it. It's like software design by committee, where every manager involved had some pet project that NEEDED to be included for some asinine reason.
Personal anecdote time: I had my interns start on Jira this summer. Three days in, I realized they weren't "getting" it because of how many damn buttons and knobs there are in the Jira UI. So, I switched all their issues to GitHub issues, and they went from having ~20 tickets in the project to over 100, and began adding, grooming, and closing their own without any input or direction from me. Sure, it's lackluster from an automation perspective, but they developed their own tagging system in the span of a few days and maintained their own board all summer.
I loved Atlassian for BitBucket in college, but when I entered the workforce and was forced to use Jira and Hipchat, I lost all love for them.
https://twitter.com/HackerNewsOnion/status/98160924222131814...
It's funny because it's true.
GitHub Issues is just so much more straightforward to use; throw Waffle on it for added functionality and your team is good!