I wish I could be off of Jira and all of Atlassian. Sadly, that is not my decision to make.
Atlassian's antics with Jira, Confluence, and BitBucket have really started to make me mad.
Jira is changing it's editor... slowly. The old editor had nice shortcuts, like h1. - h6., {code}, {blockquote} etc. When you create a ticket - it's the old editor, but when you edit a ticket or write a comment, it's the new editor! This new editor has none of the markdown-ish shortcuts the old editor had.
Confluence is also changing it's editor and the old wiki pages do not have a 1:1 match to the new wiki pages. This means you have to go through each page, convert it, and edit it to fix the broken things - because depending on what you use, it will be broken. For example, there is no longer a note, warning, or error macro - instead it gets turned into a info macro that you have to go in and edit it to the style you previously had. Code blocks no longer let you pick the color scheme you had, instead they're all generic. There's even more here I'm not listing.
Confluence has also just been wonky lately. It's supposed to automatically format a link into something nice (e.g. https://confluence/page-name -> Page Name or https://jira/AAA-1234 -> AAA->1234) and this only happens sometimes. Other times I'm finding the page frozen or slow and the only thing that fixes it is refreshing the page or publishing the page and going back to edit it.
Of course with BitBucket I dislike that they're dropping Mercurial. I understand why, but I am really going to miss it. Git is way more powerful but Mercurial is (at least to me) way easier to use and pick up. The infuriating part is that they offer no tool for converting existing repositories whatsoever. Github has a tool that will turn your BitBucket Mercurial repo into a Github repo!
For any tool that aims to be an alternative to Jira / Confluence / BitBucket, please don't do what Atlassian does. If you are going to make any transitions or any major change - please make it as easy and seamless as possible for your users.
Definitely. From a buyer’s perspective, Atlassian is awesome. It checks every single box of requirements a development team could give to an “IT department”.
This is particularly prevalent where you have software teams working in a non software business. That’s an environment where you get execs pushing for ‘unity’, whatever that is, and every team must use jira (or Monday/notion etc).
Even worse, often they’ll expect you to use jira without the software specific features.
When my org tried this, it was a good test of my influence outside the dev team.
Why do you think it’s a silly reason? I don’t want to spend a lot of hours every day working with something I genuinely dislike.
Don’t get me wrong, I know I’m fortunate enough since I get to pick and chose, but the time we spend on project management, even as developers, isn’t exactly insignificant.
Having come from a JIRA/Github/Confluence setup in my previous role to a Phabricator setup in my current role, I can't believe I'm saying this but I'd give anything to have JIRA back.
Would you like to elaborate? I haven't properly used Phabricator yet, but have so far had no problem (maybe even a bit of joy) browsing https://phabricator.kde.org/
I've found that phabricator seems to lack support for more complicated workflows so you end up having to hack together things using tags/workboards/milestones to mirror how your process works. This could be a positive though if you've suffered through really crappily configured JIRA projects.
To phab's credit, the web UX of phab is more respectful than JIRA (10 second load times anyone? constantly (re)moving things) but I've used go-jira[1] for the past 2 years to great effect and there's simply no equivalent of that for phab.
It could also be that I'm just stuck in my habits and don't like change - or the way my current orgs phab install is configured (I've never been a JIRA or phab administrator so I don't have much insight here)
I'm happy that you are able to open Jira editors. Today I wasted half an hour to discover I can only open "My Work" (the timesheet summary page) if I'm on an issue page, not from the blank main page.
Atlassian's antics with Jira, Confluence, and BitBucket have really started to make me mad.
Jira is changing it's editor... slowly. The old editor had nice shortcuts, like h1. - h6., {code}, {blockquote} etc. When you create a ticket - it's the old editor, but when you edit a ticket or write a comment, it's the new editor! This new editor has none of the markdown-ish shortcuts the old editor had.
Confluence is also changing it's editor and the old wiki pages do not have a 1:1 match to the new wiki pages. This means you have to go through each page, convert it, and edit it to fix the broken things - because depending on what you use, it will be broken. For example, there is no longer a note, warning, or error macro - instead it gets turned into a info macro that you have to go in and edit it to the style you previously had. Code blocks no longer let you pick the color scheme you had, instead they're all generic. There's even more here I'm not listing.
Confluence has also just been wonky lately. It's supposed to automatically format a link into something nice (e.g. https://confluence/page-name -> Page Name or https://jira/AAA-1234 -> AAA->1234) and this only happens sometimes. Other times I'm finding the page frozen or slow and the only thing that fixes it is refreshing the page or publishing the page and going back to edit it.
Of course with BitBucket I dislike that they're dropping Mercurial. I understand why, but I am really going to miss it. Git is way more powerful but Mercurial is (at least to me) way easier to use and pick up. The infuriating part is that they offer no tool for converting existing repositories whatsoever. Github has a tool that will turn your BitBucket Mercurial repo into a Github repo!
For any tool that aims to be an alternative to Jira / Confluence / BitBucket, please don't do what Atlassian does. If you are going to make any transitions or any major change - please make it as easy and seamless as possible for your users.