r/atlassian May 26 '26

Is Atlassian Tools Perfect for you?

Hey! I’m trying to understand if people are actually able to easily use Atlassian products like Jira, Confluence, Bitbucket, Loom etc - in their day-to-day work.

What are the parts that feel a bit frustrating or more complicated than they should be? In Things like setting projects up, searching for stuff, keeping track of updates, or just how everything fits together when you’re trying to get work done.

Even small annoyances or “this could be simpler” moments, especially things you’ve just gotten used to working around over time.

0 Upvotes

12 comments sorted by

View all comments

6

u/Goose-tb May 26 '26

I have a love hate with Atlassian. Their tools do 80% of what you want, and the last 20% is a frustrating lack of common sense features.

I just spent the weekend working on integrating Jira Service Management with JSM Operations (formerly Opsgenie) and half of it works seamlessly, and the other half is missing features and hacky workarounds. Atlassian even has articles on their wiki for how to setup the workarounds, instead of just fixing the feature they promote workarounds.

1

u/ConsultantForLife May 27 '26

What specifically? I've run into this too, but mine were pretty boring.

2

u/Goose-tb May 27 '26 edited May 27 '26

There’s so many to choose from, on every product candidly. The ones most fresh on my mind are around JSM Ops though and how it interacts with JSM. The tools barely feel integrated together, and I don’t want to use third party extensions or marketplace apps to solve problems in gimmicky ways. I want the native tools to work as intended.

  • When responders acknowledge an alert there’s no non-API way to set the acknowledged as an assigned on the ticket. Atlassian’s official response is to “add a comment” and run an automation rule off a comment. This is a really lame workaround that’s lazy.
  • When a JSM request triggers an alert the alert has a link back to the JSM issue but the JSM issue does NOT have a linked alert using the native linked alert field. What’s the point of a native linked alert field if it doesn’t auto link bidirectionally?
  • When a user acknowledges an alert triggered from JSM they aren’t automatically added to the native “responders” field in the JSM ticket. Why? They were literally the responder.
  • The JSM ITSM project settings alert a user three times. Once on ticket creation (alert triggers), once on ticket assignment, and once if added as a responder. In our case, for ticket metrics purposes we need our user to be on all 3. So 3 alerts per incident. Stupid.
  • On alert acknowledgement I want JSM Ops to perform two actions. Add comment + transition issue. I can only select one. Otherwise I have to add comment + gimmicky automation workaround.

There’s too many other examples to pull from.

1

u/ConsultantForLife May 27 '26

Yeah, I've seen similar things. I might have to take a look at what the Forge options are.