[jtdev]

I'm convinced that the only thing keeping people using Atlassian products is naive managers and antiquated IT/Ops staff who've learned that mentioning "Jira", "Confluence", etc. in the presence of their seniors results in some micro-fractional justification of their existence.

To paraphrase Thomas Sowell: "The least productive people are usually the ones who are most in favor of [using Atlassian products]".

[taude]

I think this is overly simplistic, and extremely naivive speaking as a manager. You sound like someone who's a year out of college (or suffering from some other immature personality characteristics) and/or working for a company with very few employees.

I routinely orchestrate tech delivery between anywhere from 3 to 10 dev teams across our organization. I'm totally open for suggestions on better tooling that: a) don't require me to schedule a ton of meetings instead to get status on all the various teams dependencies, dragging everyone into meeting hell b) don't require me to use multiple tooling for different teams c) don't require me to make project plans in other legacy tools like Microsoft Project, or even the newer "spreadsheet" tools like Smartsheet or Airtable, etc...

EDIT: Some other features I use all the time (speaking mostly in JIRA land): 1) one click linking from the JIRA issue to the Github PR 2) Partitioned Kanban/Sprint boards for each team, as well as easy ability to rollup to master board for entire project 3) Ability to Search, advanced search, filtering, custom dashboarding, etc. 4) Array of plugins to work with other tools like Slack (I can one-click create JIRA tickts from slack conversations), and I can additionally run JIRA queries and bring in the results into my EMACS workflow. 5) I won't go into all the bigger company things like user management, integration with SSO providers, etc, since that doesn't impact me and my team(s)...

In short-every one has their use cases. And orgs of various sizes will have their own.

[jtdev]

Ask yourself if any of the things you mentioned actually result in a materially significant improvement in delivery of working software, in comparison to say... sticky notes and sharpies.

[dsr_]

You start with sticky notes and a whiteboard, and then you note that nobody remote can change the whiteboard unless somebody else does it for them. And when you work from home, you can't see the updates unless someone sends you a photo. And Ralf's handwriting is terrible.

So you look for something that replicates the whiteboard on the web, and it's either too freeform or too rigid or too expensive...

[marcind]

Sorry, can't resist: you've perfectly teed-up ShareTheBoard. Solves the exact problems you've listed here. https://sharetheboard.com

[stnmtn]

I think it's incredibly obvious that just about any tool that can used remotely will be orders of magnitude more effective and helpful than sticky notes.

[yoz-y]

When I was using it i quite liked it. Speed was not great, but custom workflows for Jira worked nicely and confluence was fine.

[zucked]

I actually quite like Jira and Confluence. They are the pure distillation of garbage in, garbage out, though.

[robertlagrant]

We've kept them because they link well and through to GitHub, and you can generate decent regulatory documentation through querying Jira, which we need to do.