As much as this is overly simplistic, there’s a sort of appeal here…
The good news when you have proper issue management is that you don’t lose any issues. The bad news is you don’t lose any issues.
In my work, the issue tracker has issues that are over 5 years old. Any time someone dares to just purge those, some one comes out of the woodwork to suddenly passionately care about this thing they have forgotten for years until the jira notification triggered them.
Projects that have pristine issue discipline tend to suck, as they waste so much energy on things that didn’t matter whether or is fixing or engaging in an argument about the value. The better projects tend to say “fine, we will hold that issue in low priority backlog and get to it if we ever run out of better stuff to do”, and the submitter is placated and everyone knows we will never run out of better stuff to do.
I’ve suggested to my team a few times that we should start a new business developing “Atlassian, but good”. They’re up for it. So many of our wider business have never used “anything but Jira”, and they can’t see it for the steaming pile of shite that it is. Not just that it’s a bad tool for developers, QE, project management or customer support, but they couldn’t imagine anything that’s better in any way, or how it would look if it didn’t have so many issues.
Problem with being a business is that Atlassian isn’t so much really a software company as much as they are a marketing thing that pretends to be software.
Agile consultants say “Atlassian”, companies lap that up at the executive level and the employees roll with it because selecting Atlassian is “thought leadership”. The people picking Atlassian are not the people using Atlassian. Paradoxically typical Atlassian rooted workflows are about as far from being actually agile as you can get.
As a future customer, please include high quality connectors to import legacy data from Jira and Confluence. We’re going to need them. Thank you in advance.
Nothing, personally. Jira at our place only serves the bean counters in the programme management department. The data is a mess anyway, it just gives them the illusion of control.
I work in a large enterprise and most of our work is just stupid red tape satisfying processes and other teams’ rules, many of which just exist to keep those teams employed. There’s so much unnecessary work and BS going on.
That’s definitely not a problem of Jira. You’re hating the product, when most likely your ire would be drawn to any application you were using for such a fucked up process.
Considering they are talking about making a replacement service, probably just GitHub/codeberg/etc and collab edit docs and discussions at the start, and then eat your own dogfood.
Atlassian now circling the drain.
I hope they will go down the drain. No more Jira! 🙏
What would you use instead?
Nothing. I really hate the agile thing anyway.
As much as this is overly simplistic, there’s a sort of appeal here…
The good news when you have proper issue management is that you don’t lose any issues. The bad news is you don’t lose any issues.
In my work, the issue tracker has issues that are over 5 years old. Any time someone dares to just purge those, some one comes out of the woodwork to suddenly passionately care about this thing they have forgotten for years until the jira notification triggered them.
Projects that have pristine issue discipline tend to suck, as they waste so much energy on things that didn’t matter whether or is fixing or engaging in an argument about the value. The better projects tend to say “fine, we will hold that issue in low priority backlog and get to it if we ever run out of better stuff to do”, and the submitter is placated and everyone knows we will never run out of better stuff to do.
We can only hope so.
I’ve suggested to my team a few times that we should start a new business developing “Atlassian, but good”. They’re up for it. So many of our wider business have never used “anything but Jira”, and they can’t see it for the steaming pile of shite that it is. Not just that it’s a bad tool for developers, QE, project management or customer support, but they couldn’t imagine anything that’s better in any way, or how it would look if it didn’t have so many issues.
Problem with being a business is that Atlassian isn’t so much really a software company as much as they are a marketing thing that pretends to be software.
Agile consultants say “Atlassian”, companies lap that up at the executive level and the employees roll with it because selecting Atlassian is “thought leadership”. The people picking Atlassian are not the people using Atlassian. Paradoxically typical Atlassian rooted workflows are about as far from being actually agile as you can get.
Hi mate, fingers crossed for you and your teams.
Maybe start with Trac if it’s still available. Freeware.
Hm. Bear with me. I’ve used jira on prem for a very long time and have used a multitude of other products.
Jira was quite good in comparison.
What am I missing?
(aside from the whole cloud requirement and atlassian behaving AI-shitty)
As a future customer, please include high quality connectors to import legacy data from Jira and Confluence. We’re going to need them. Thank you in advance.
If you were starting a new company what would you use instead of Jira?
Nothing, personally. Jira at our place only serves the bean counters in the programme management department. The data is a mess anyway, it just gives them the illusion of control.
I work in a large enterprise and most of our work is just stupid red tape satisfying processes and other teams’ rules, many of which just exist to keep those teams employed. There’s so much unnecessary work and BS going on.
So then how would you document changes, work, etc. as is required by SOC2, PCI, SARBOX and other auditing frameworks that businesses require?
We don’t do any of those things. We’re not even developers. We just use Jira to log hours (which is basically one big fantasy obviously)
That’s definitely not a problem of Jira. You’re hating the product, when most likely your ire would be drawn to any application you were using for such a fucked up process.
Probably but Jira makes it so hard.
For example if I type 1h 33m it’s ok but 1h33m is not. It’s just a really awkward UI.
Considering they are talking about making a replacement service, probably just GitHub/codeberg/etc and collab edit docs and discussions at the start, and then eat your own dogfood.
Check out what microslop is doing to github. Codeberg though, that’s an option!
I’d want better tickets for dev and bugs than github has, not sure the codeberg offering there if any