Activity
Mon
Wed
Fri
Sun
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
What is this?
Less
More
Memberships
Atlassian Everything
275 members • Free
12 contributions to Atlassian Everything
5d •
When a Jira work item gets blocked mid-flight by another item, what does your team actually do?
Curious how different teams handle this in practice. What's your approach, and what drove that decision?
1 like • 5d
I introduced regular syncs with teams to have a health status on each of the work items - anything that was potentially at risk of delivery, would be surfaced early. The impact would be discussed across all relevant stakeholders and a clear line of sight on what the mitigation plan would be is most important.
0 likes • 4d
@Denise Ellis we created a new tab in our notaries which was solely for capturing health status (R/A/G) with an assigned owner and mitigation path. Having these as custom fields rather than labels was a useful mechanism for building out reports which could be shared with the essential team reps, it worked extremely well to the point we improved release commits within 6 months
Feb 16 •
Velocity Reporting at scale?
Hey everyone, Wanted to get people's thoughts on what they might have used from a reporting perspective to show performance (such as velocity) at org level without the use of paid gadgets? I've only thought of adding i-frames into confluence (but this is a poor offering to exec teams and the format is bad as it shows the entire page not just the velocity report. The AI savvy people in our teams are starting to use MCPs such as Claude, but the connection and effort required to get the correct prompts required is too much in my eyes (but I'm becoming old school in that regard) I'd like an out of the box solution instead of coding AI to get me various results. Any help appreciated, this won't be just a one and done requirement, I envisage that it'll be an ask for almost every other metric that we can get from Jira
0 likes • Feb 16
@Sara Tucker thanks for the input - we're on premium so those options aren't available to us unfortunately
0 likes • Feb 17
@Sara Tucker Yeah we have custom charts, it’s very good! Might explore and see what it could give me on velocity - thanks!
1 like • Feb 9
Has Rovo not been rolled out to all premium and enterprise customers yet? I was sure it had but my new org only shows the number of rovo credits we have (all unused ofc) but I can't see Rovo as an enable option anywhere!
Feb 2 •
New site or cleanup?
What's your preferred way of work? Especially for work or Atlassian Jira, when you inherit it all from prior colleagues. :) You like to set up everything anew and customize from there, or you rather organise, cleanup and optimise the inherited "mess"? :)
0 likes • Feb 9
I'm currently living through this. I have inherited a Jira instance that is by far the most chaotic I have ever seen. Trying to keep a calm approach and look at it holistically, find out what I have to focus on, implement changes there and then potentially look down the road at the rest of the chaos :D I have never considered spinning up a new instance, but this situation made me double think that for sure. Curious to know, does anyone work in a large scale operation that has an extremely tidy configuration that can span across multiple value streams/engineering teams? Is small and simple still scalable?
Jan 14 •
Jira Workflow/Scheme Configurations for larger scale orgs
Hey everyone! As I was brushing my teeth this morning (which is usually the time I'm most reflective), I wondered how other orgs that you guys work in or have consulted with like to manage your workflows and schemes? I've worked in both a very disciplined and totally chaotic environments, and really see how essential it is to have consistency across teams. In the past, we have leveraged that by having a single scheme and workflow across multiple spaces (and with some minor exceptions for non tech teams kept a like for like mirror image of those items with some minor adjustments based on their individual team needs) But on the flip-side, if you need to put mandatory fields or validations on workflows to improve the discipline of some teams but not others, would you feel that having several duplicate schemes works best in these regards? Or do you just apply a one size fits all approach and stick with one single instance?
0 likes • Jan 15
@Sid Pathirana thank you this is super interesting! I've not really had to dive into the post/validation functions on workflows very much but you're saying that you can put a condition in that only specific users/functions could as an example see a status when others possibly couldn't? If so, it goes into more detailed configuration but definitely can see the value of it when as you say, you want to reduce maintenance overheads. I'll definitely look at that as an option!
0 likes • Jan 15
@Sid Pathirana wow that's amazing, never thought of this as an option to reduce duplicated workflows! Thank you for this, I'll definitely consider it. And agree regarding comms, people get nervous when they spot something they don't understand, I'm a huge advocate of documenting everything and making sure supporting comms goes with every change. Appreciate the recommendation!
1-10 of 12
@orla-mears-5016
Hi I'm Orla! Based in Ireland, very much a self taught Jira Administrator, trying to navigate through the chaos of Jira and try not to break things
Active 4d ago
Joined Nov 6, 2025
Powered by