Haddon Fisher Expert

It would have to be a Jira Service Management project. Otherwise, no; the permissions are not granular enough.

I could see a theoretical path to building this using Automation (a multi-user picker field that gets set when a user is mentioned, they get removed when they comment; another rule to find everyone and then message them), but I think you might be better off with a checklist add-on if one supports assigning or mentioning.

I don't have that exact config but if they use the built-in DVCS stuff does the development JQL work?

I'm excited to see how they managed to whittle a list so big down to nine! 😂

@Aaron Geister inherited instances are the worst. 😂

HA @Dave Liao ! I think I disagree with you though; you're not going to have a lot of customers left if you keep optimizing for "cheap" over "needed" 🤣 I'd also be really curious why it would cost that much. Smells like maybe someone's been forgetting to pay off their tech debt...

@Kim MooneyMany people have mentioned this above and it's been a source of friction for as long as I've used Jira, but at the risk of stating the obvious: Jira really doesn't do a lot to help with keeping itself not messy. * Already mentioned specifically, but the cruft created when you spin up a new project is…

Check the history tab and see.... - Was the issue always an epic? If it started off as something else and was moved, it could have been set prior to the move. - Was it always in this project? It's possible another project put the field on there (cannot speak to why though 😁). - Was it bulk updated? You can update a field…

As someone who spent 8+ years on Server before moving to Cloud, there's a lot to miss...they are functionally two different applications 😂 . Off the top of my head... - The greatest thing about Server\DC was, if the application didn't do something you wanted it to do, there was almost always an add-on that would fill the…

I'd really love some clarity on this from Atlassian. I think we've all been pretty patient and accommodating, but this crossed the line from ridiculous to absurd a while back. Please: * Give us some kind of update, both here and on the ticket, about the progress of this solution. * Stop closing tickets on JAC by saying…

Just a suggestion but... The portal functionality (and the accompanying non-licenced-user-access mentioned above) is the main reason JSM licences are more expensive than (and distinct from) JWM\JSW ones. If you're not using it, I'd look at using one of the other types of projects for this?

Sisyphean - as in "denoting or relating to a task that can never be completed." :) * Jira is big. It can solve lots of problems if you take the time. * Jira is complicated. It can almost always be optimized closer to the goal. * Jira is in flux. Atlassian is always futzing with something; sometimes it's even in need of it.…

Only a wee bit jealous that you're syncing groups :) Someday...someday...

I'd +1 the "teams" picker field. I have in the past included the Jira project key of that team's project - this is very useful when you want Automation to do something like make a ticket in that project or projects :)

I haven't played with it extensively but I think it's mostly useful for @mentioning groups at once. You can't use it in project roles, automation rules, user-picker picker, or anything like that as far as I know.

There are a lot of different template workflows, but you can always customize them or just build one from scratch. This is a deep pool though, and there's a lot that this question could cover...it might be easier if you listed specific requirements you need to support.

I was not a fan of Atlassian slapping a new field into all of your company-managed JWM projects despite it not being configured (or really useful in any way right now). I figured I'd do everyone a favor and just pull it from all of the screens. "Let Atlassian keep monkeying around but let's not impact my users", I thought.…

I get that this method involves less clicks, but I'm not sure how this is more intuitive than the old process, especially when the "template" button is right there next to "create".

Congrats! - Pick a framework. They're all great and all not great in their own special ways, so don't be afraid to try each and see if one speaks to you. I have found having something as a starting point is better than nothing; its easier to tweak than to design from the ground up! - Once you have a process you like, come…

One other question: any update on Insights\Asset Management integrations for Cloud? Putting aside for a moment that this new nice-to-have feature is sapping development energy from higher priority, more fundamental, and ultimately more needed work...it's got some interesting potential. However it's still minimally viable…

Forgot to shamelessly plug JRACLOUD-78620

+1 to @Amir Katz (Outseer) and @Nic Brough -Adaptavist- when they point out the naming issues. I have less of an issue with allowing Jira instance admins the ability to name custom fields the same; they at least understand what they're getting themselves into, and I could see a few places where contexting alone would not…

Being flexible enough to tackle almost any use-case was never going to result in a simple tool, but it does seem like they're leaning into confusion in a deliberate way in the past few years, particularly on Cloud. Other people have pointed out how many of these choices seem to be self-inflicted, but I'd add in that not…

I love the engagement. It's frustrating to hear you say you cannot improve functionality because you are focusing on scalability and performance. These are important and do need work, but the fastest search in the world is not going to help me find my original sprint commitment out of the box, or on Cloud. Y'all bought…

Love the engagement. - Can +1 the ask for "Atlassian Analytics" to extend beyond Enterprise; everyone needs this. Happy to show you the plethora of google sheets based reporting we have to do right now. - Would also +1 the sentiment that it's a little frustrating to see so much effort being put into new shiny toys while we…

Hey @Jehan Gonsalkorale , we have two types of teams using JSM: * The actual IT and service teams enjoy it quite a bit - there's a ton more promised than delivered (almost all of the newer, purpose-built functionality seems only 50% complete) but the stuff that works is useful. * People who saw the sexy customer portal and…

I am a big fan of the add-on "Rich Filters" for this type of thing. You can build a custom value and display it directly on your dashboard as a number. This is displaying different JQL-based categories, but it would appear visually the same: (I am not an employee of this vendor, just an aficionado of good reporting…

It's wildly exciting to see movement in this area and I don't want to be negative...but as cool as this is, there's nothing here I couldn't already see on a dashboard. Are there any plans to introduce any kind of exporting to this? Historical or trend analysis outside of the very limited "velocity report"? Any more…

I suppose it confirms I am losing my mind, but thanks y'all!

Yeah, this is another one of those "we're making it better for us by making it worse for you" features.