Meanwhile, a company I used to work at keeps on using self hosted MantisBT.
Its maintenance takes like 2 engineer days per year total, if that. Its initial setup with all the plugins ( of note are those for project management and release tracking) and integrations (e.g. git) took one engineer week if I remember correctly.
And it works just fine for 7 years now, to the point that the only advantage of Jira I see is a slightly fancier looking interface for the regular user. Whilst costing peanuts.
I even prefer the old school Mantis BT look and feel.
Lots of discussion here of whether Jira is any good or not. Almost none about the actual contents of the article.
None at all about how the changes are bad for all but enterprise customers. It's not obvious to me - and it would be nice to have an explanation.
On September 18th Atlassian announced a new license model for Jira automation that severely limits automation for all but enterprise customers starting November 1st. Many customers will be forced to give up their automation or upgrade to expensive enterprise tiers. Since there is no enterprise tier for Jira Product Discovery customers using automation in this product don’t even have the option to pay more.
To be "that guy", the submitted title is heavily editorialized
I am the ultimate smart tech man at my company.
Warned them about Jira.
Warned them about M$/Sharepoint/Power Automate.
Jira and New M$ services are at bait pricing. They will all be extortionary levels at some point.
Kind of amazes me people are paying for inferior closed off services, but I imagine the people making the purchasing decisions are more concerned about which concert or sports game the sales person is taking them to.
I was a big proponent of Jira over all other PM systems because of its functionality but now? Gitlab is better, and isn't enshittifying as quickly as the rest.
I've been hosting Taiga for a small team and it's been a pleasure to work with. Can't tell how it'll work for a 100 developer team with multiple product managers, scrum masters etc, I'm hoping someone else here has an idea. But for a small team of 25-30 people everything's smooth.
Website: https://taiga.io/
Docker: https://github.com/kaleidos-ventures/taiga-docker
Docs: https://docs.taiga.io/
We're using azure dev ops and recently started leveraging their Pm tool for our requirements management.
So far, I've been impressed. It took a little time to figure out how to operate within their paradigm. Once we tackled that, I don't see is going to another solution.
For better or worse, 365 is a pretty decent suite. Integration across their stack is a little schizo at times but it works well enough.
The only Achilles heel right now is ms project. They're planning on EoL it but in true Microsoft fashion are cagey when they plan on doing it and the replacement is lack luster at best. We're switching to Wrike instead which has so far been what we want.
Just like code smells, there are workplace smells - practices that indicate a place is meh.
Use of atlassian Jira is one such smell.
Interestingly Slack Workflows also introduces pricing. So it seems both companies are targeting charging for automations / charging for things which used to be free.
I don't use Jira but any bad faith move (as claimed) is a serious concern for users of other Atlassian products.
I've always been a champion of Trello and really don't want to be having to add cautionary notes about corporate sharks owning it, and functionality taken for granted being whipped away. Not cool.
Jira's APIs are bloated horrid nightmares and I hope this drives people away from actually leveraging them.
you can also use open-source automation tools like n8n or windmill.dev, or github and gitlab workflows as mentionned above.
Why would you use tools/olatforms that was clearly made for enterprise as non-enterprise. Plenty of free tools and platforms around. Github for an example has really good F2U workflows.
GitHub and GitLab workflows are much more convenient in my opinion. They were made with actual workers in mind: developers, QA, release managers, DevOps, etc. Jira, on the other hand, is purely manager's toy with all it's useless features that often stand in a way of daily routine. I never saw any developer who was happy about Jira.