Haddon Fisher Expert

+1 to Michael Bachmann's question. Would really love someone to explain the north star behind "List". It is literally just less-good "Issues". 

First, the obvious questions....why this, why now, why bother. The "issue" isn't really an issue, hasn't really been an issue in literally the entire history of Jira, and it's potentially the least of the issues Jira has. Lots of people have asked these questions; it is telling that we're still asking. Second, why this…

Dirk Lachowski these are solid call-outs. - Around the new UI....I also have been a Jira admin since the early days (first started administering Jira in 2012, Confluence in 2008) and have stuck with it pretty consistently. I have to admit, there are a lot of times I miss the old Server\DC UI - it wasn't sexy but it was…

Hey Andy Heinzer - It's funny that you bring up the "`issue` to `work`" topic, because this is sort of the same issue in a different expression. I am absolutely not intending to nitpick something you said, and none of this is personal, but I do think "...these products tend to serve different audiences" sort of hits the…

Based on the output I've seen since Atlassian went public, I am not even sure they know there are other products, let alone talk to the people who make them.

This is a consistent (bu-dum CH) problem across Atlassian's product stack. Jira using the term "project" to refer to what in Confluence would be called a "space" is already a constant low-level confusion. It encourages people who don't have a lot of experience with the tool to treat these as ad-hoc boxes for ad-hoc…

I once worked at a super-large financial information company...not naming names, but it started with a "B" and ended in a "oomberg LP". Their core product was "the terminal" and when they call it that there's a good reason: it looks like someone reinvented DOS with a bit more colors. My first day, I was so shocked I…

@Todd Thomas hit the nail on the head here - this concept is so exciting, but it's hard to build a process on top of something when it's support is so piecemeal. To pile on some things to Todd's list: - Instead of the 'Team' custom field, a 'Team Picker (Single Select)' and 'Team Picker (Multi-Picker)'. Ideally we'd be…

I very much appreciate the effort Atlassian has taken thus far in informing the community about this change. The chrome extensions, many beta offers, and direct conversations all show a strong willingness from Atlassian to create spaces for feedback. The reaction (at least from what I can see) has been to deliver that…

Hi April! I'd be curious if you could share Atlassian's long-term vision for "Teams". With this change, the difference between a group and a managed team is (as far as I can tell) just where you can use them. If this is true, what is the intention of having two distinct and somewhat non-overlapping solutions to the same…

This entire idea both utterly shocks me and does not surprise me in the slightest. * Why is this a problem? This "problem" has been around since literally day 1 of Jira and it doesn't seem to have been a major barrier to using the tool. It's been said ad nauseum above but 99% of users think they're called "tickets", learn…

I'd love if Atlassian would validate the "success" of some of these UX changes. Every time we raise concerns, we kept being told "oh all of our feedback indicates that this is a good change." From who? Because this change continues to bite us in the ass, 2 years on. In the exact same ways we raised when you pitched it.

Fields context don't work with team-managed projects. Even in Jira Software, if you create a team-managed project, you will not be able to use a field that has a context in it. Jira Product Discovery projects are team-managed, which is why context are not supported. For a Jira custom field to work in a team-managed project…

Beat me to it Marc Koppelaar - Devoteam :)

Hey Sherif Mansour, thanks for the follow-up! * We did a lot of unscientific poking-around-testing, but there were two cases we saw a lot of value in and ran some more controlled experiments. In both cases, we hit the same trust-related catch-22:* Creating Automation rules* Context: Its not feasible for admins to own all…

Hey @Sherif Mansour - loving this energy and the transparency here! One question for you: AI technology holds a lot of potential, but beyond any other considerations, just may not be a good fit in all use-cases, even down the road. For example, in our testing of prompts we expect our customer-facing departments would use…

Elizabeth Nixon I am not sure about Atlassian-generated documentation; it feels like it should be on this page, but it clearly says the opposite...maybe out of date? However doing it should be pretty trivial: * Open your team-managed project, and go to 'project settings' * Go to 'issue types' and select the issuetype you…

Elizabeth Nixon there will still be issues trying to cross-project reporting using TMP's, but it is now possible to use instance-wide fields in a team-managed project.

This is AWESOME, thank you! One note Sam Knight - it would be great if we could use 'teams' and Jira project roles in addition to individuals and groups. Individuals isn't really scalable if you have a lot of people, but groups can only be edited by Site Admins, which isn't scalable either. Management of the 'teams' and…

It's always been a bit of a challenge to get good insights out of Jira. It's definitely getting better, but at the end of the day I've still found a need for Sheets. * Realtime only - Jira itself only makes the "current state" of datapoints available, so it's impossible to track anything over time. * Getting the Set - Just…

My favorite approach to reporting in Jira is to use Google Sheets.

I use Google Sheets to do pretty much any complex reporting on Jira data. I'm not super proud of this approach; it evolved it more out of necessity than anything else, but as much as I try to get away from it I always come crawling back. I'm still fleshing this out, but there's some basic outlining of how I've found…

Hey Saskia van der Peet, There's a bunch of different use-cases in there depending on how you read your question, but the short answer for all of them is "painfully" 😂. Generally I do this one of two ways, depending on whether I'm looking at a single project or "holistically": * If I am analyzing a team-managed project for…

I know you haven't typically done this in the past, but do y'all have any plans to "show receipts" here? * I'll own I'm just one loud rando who has only his own tastes and experiences to work off of, but "the simplicity and intuitiveness of the layout" and "The persistent left sidebar with easily collapsible/expandable…

For those of you who have actually invested any time in Compass or Atlas....is it any better than Portfolio 1.0\Portfolio 2.0\Align or any of the other attempts they've made to chase this dragon? To be honest, at this point I just take it on faith that these tools are too data-heavy to work and will be quietly dropped in a…

I almost didn't want to mention change management comms at all here...it's such a big issue in and of itself it's worthy of it's own topic. To Gary Spross's point, "Here is a change; the window for your instance to receive it started a week ago and runs for 9 months" is not helpful. I've also heard the whole "we can't be…

I am a site admin and lead business\app admin for a company of just under 2k people, Agile train lead for 6 teams, and scrum lead for 2 teams, so I hit this change from a couple of different ways. After a few days and putting aside all of the unsupported areas and known issues, I'm still not enjoying finding things in the…

Hey all, tossing in my 2 cents. arajah, it may be true that the last UI change Atlassian considers "major" was 5-6 years ago but users see changes to the UI on a near-continuous basis. I would agree with @John Funk wholeheartedly that change fatigue is a real problem, particularly for admins. I'd also agree with him that…

I am absolutely loving the attention paid to user testing here - early access AND a chrome plugin!? NICE. As far as the change itself goes...uh...not a fan.

This is great news! There's a basic expectation set by the last 20+ years that custom fields are instance-wide, so seeing this start to be addressed is great. One callout: You keep trying to delegate custom field access to project managers (team-managed projects and now this "field management page") without really…