Haddon Fisher Expert

I definitely used your post as reference material, and if I didn't have AI I almost certainly would have ended up doing something nearly identical :) I am having a hard time getting an honest sense of how much extra the pricing change is going to cost us, but agreed that whatever the actual number is, I'm not excited about…

Yet another super frustrating experience from Atlassian. Your Beta feedback helped refined the experience and we appreciate it. This page remains the best place for more feedback, FAQs, and ways to reach our product teams. If you are going to ask for this, then it's sort of implied you're going to do something with it.…

Don't get to say this enough but I love the community so much. There's so many people helping each other - it's become probably the best resource on how to use Jira outside the docs themselves. Thank you for all the hard work making it work!!!

Is that why the Automation usage changes are being announced on the 10th? 😂 But seriously, excited for the new home!

Des Kelly yes that's a great point! If you want to make "Create" a better experience, enhance forms and let admins turn those on optionally as the create screen instead. It's boosting functionality that already exists, doesn't break existing patterns, solves a decent chunk of the problem, and is one more reason to…

"As always, Jira administrators tend to comment on changes from their perspective, not from that of the end users. Our users think it's great." Wurm Peter I would agree that administrators tend to worry about things from their perspective, but I would argue that they probably have a more balanced perspective than the end…

Hey @Kanad Dagaonkar - first, thanks IMMENSELY for the engagement here - as others have mentioned, this is not what we've been trained to expect but its AWESOME and I love it! I truly believe this is how we all succeed. I feel terrible "thanking you for your engagement" by being negative, so I want to make it clear that…

To be fair, they always sat on a lot of very valid feature requests @Ryan Gillespie but I agree 100% with the rest. At least prior to going public there was a very obvious capacity problem - the change velocity has skyrocketed since going public, but its a firehose of hot garbage.

This is a bit of a stretch, but the "feature" I'd love to see Atlassian unwind is being a publicly traded company. The proof is all circumstantial, but it feels like this is the moment when they secretly changed the company value "Don't f&$@ the customer" to "Don't forget to fleece the customer."

@Viktoriya Kazunka it 100% depends on your needs but in general I would tend to agree with @Ignacio Pulgar that "any automated port is good in a storm" and that trying to shoehorn into Atlassian's actual "invite" process may end up making more work than it saves. That being said, it does look like…

I wrote some instructions for users on this a while back if it helps. I had one for project search but Atlassian recently broke the URL pattern by adding in what "flavor" of Jira the project is, so there isn't a consistent path for all projects anymore.

It's been a minute since I did this, but the pattern is I believe to have your directory map users into a group which automatically grants Atlassian seats to members. One word of caution - I have had plenty of fun detangling permissions from licencing, so if you are just starting out, I would try to avoid granting access…

I'm using Codex for as much Jira administration as I can throw at it these days; I have found a lot of success in a couple of specific areas: 1. Vibe-Coded SPA's I can document it a little more thoroughly if the sleeping pills aren't working for you anymore, but TL;DR: our quarterly planning process involves a…

- Disable "team managed project" creation. - Naming conventions for everything. - Create a Confluence space to hold documentation about how your org uses Jira. - Create a Jira space for your org to use to track & manage Jira requests. 2026 was actually a bit of a game-changer as far as Jira admin for me: - VIBE CODE YOUR…

* This post went up on February 15th, with the explicit ask for people to provide feedback in comments. * People agreed that:* The page does indeed load faster. * Not treating this as a custom field means we have very predictably lost all of the additional functionality associated with custom fields. * Atlassian makes one…

I'm a little confused by this announcement. The way it's written, it sounds like you are saying: "We are no longer going to release things 'whenever we feel like it'; instead, we're going to have a real schedule and make announcements and enable things on specific dates which will be communicated to you beforehand and…

Over the last few years, we’ve heard a consistent message from admins, champions, and power users: you like that Jira keeps improving, but it’s too hard to keep up with what’s changing, when it’s landing, and how to get your teams ready. Almost all of this seems true.

Darryl Lee it's amazing - I had completely forgotten about these! It's funny what a mind will do to protect itself from the pain and suffering caused by Atlassian Cloud applications 🤣 My 2013 self is rolling in it's carefree grave, but damn, did we have it good on server.

+1 to Darryl Lee's comment - I pretty much gave up reading these for any other reason than "what should I (generally) expect to see in my instance at some point in the next six months". In some cases what you read about does show up as advertised...but I have also seen things change shape before it hits our instance, or…

This is really cool! I really appreciate the thought put into field management here, it's majorly useful. One question: do we know when we'll actually be able to use all of the global field types in JPD? It makes total sense to me that JPD might have some unique additional needs which require it to need to support some…

I'd love to live in a world where this isn't needed, but I really appreciate y'all taking this hard but absolutely necessary step. One ask: please make double-check that everyone internally is still opted into notifications...it seems that someone has managed to miss one already.

I personally am ambivalent about this change from a "is this better" perspective - I'm not a developer in my day-to-day, and frankly this just isn't an area of the platform I engage with enough to have a valid opinion there. That being said.... * As is Tradition, the way I found out about this change was a user saying "hey…

This is definitely my "garage band dad getting a shout-out from Bruce Springsteen" moment. ::tries to play it cool:: Full disclosure, I: * Am working on my phone so I don't have access to Jira to actually test this theory...I can't remember how clone works and I am worried about how to feed it an issue in a branch or how…

I've been using Claude to handle some tasks and been really enjoying it. There's a class of work that is conceptually pretty simple to understand but hard to execute for some reason or another which it can handle extremely well - bulk archiving issues, for example. However, I have to admit that most of the use-cases I can…

@Tanya Maddalena I am not sure if this is your team as well or not, but the new "Bulk Operations" UX and flow...and apologies for the bluntness here, but it's a straight-up abomination. I'm at the point now where I wonder if Atlassian legitimately dislikes its users because as janky and old as the old bulk update was....it…

Love this change. There's a lot of duplicative functionality in Jira and reporting is an area that needs a lot of love, so excited to see the attention and focus.

I am glad that y'all are conceptually focused on making something difficult to use less so. And yet it really feels like y'all haven't really learned anything from this year's "experiences" with UI changes. "From the feedback, especially from Confluence users, we learned that the expand/collapse button was hard to find…

+1 to Federico Vecchiarelli's comment: I am conceptually (somehow) totally OK with this one specific terminology change...but this is never going to fly with me: If you can't be bothered to put the work in to actually complete the terminology change, or even "hey here's a parallel structure for you to get used to while we…

Thanks for the update Carol Low! After thinking about this a lot more (and doing a bunch of field work) and I think the real issue is less about the screen size itself and more the first issue "It doesn't feel like a scalable solution that can actually fit all of the controls, particularly for the more complex custom field…

Thank you @Dave Meyer and your team for making this change. I know this whole episode has been tough for everyone but I hope we can use it as the foundation to build something better. I know the last thing anyone wants is "more complaining from the users" but if you are looking for ideas about where to begin a…