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
272 members • Free
5 contributions to Atlassian Everything
25d •Â
Data-driven ways of working
Hi everyone! I’m curious to hear your best practices when it comes to being data-driven in Jira. - What reports or dashboards do you rely on most — and why? - How do you use Jira data to support retrospectives and continuous improvement? - Any tips for improving data quality or avoiding misleading metrics? - What’s something you’ve seen work really well (or not work at all)? All perspectives are welcome! (Scrum, Kanban, hybrid) Best regards Simon
1 like • 25d
My first reaction to this avoid Jira outputs reporting from becoming the focus of leadership. Their focus should be on outcomes. Building reporting at the output level should be kept for working teams to improve their processes and not for leadership reviews/readouts as this can lead to bikeshedding
1 like • 10d
@Tei M. Law of triviality https://en.wikipedia.org/wiki/Law_of_triviality Basically focusing too much time/effort on not the most important thing or unimportant things.
22d •Â
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 • 22d
If you have Jira or Confluence on enterprise, you should have access to Atlassian Analytics which is a reporting tool that uses sql and the Atlassian data lake. There are templates for site wide reports that are pretty good as well. Jira also has a beta version of dashboards they are working on but I haven't explored that a lot yet so not sure that would address what you are looking for.
1 like • 22d
@Orla Mears ahh sorry. The other thing I commonly use is the Custom charts app but that of course is a paid gadget 🫤. Seems like the MCP route might be good to explore in this case. I have seen some discovery projects that use Jira data into AI tools for reporting that look pretty promising.
25d •Â
Silent bulk updates?
Has anyone come up with a magical hack that allows you to update in bulk without sending any notifications (no emails, no slacks, no in-app notifications, etc)?
0 likes • 24d
@Alex Ortiz cloud
0 likes • 24d
@Alex Ortiz True that you can disable emails but what I am really struggling with are the slack notifications. They can be from: - A space integration setting with slack which in theory I could go into every impacted space and mute them but this would likely take so much time to do it hardly seems worth all of that effort of finding all the impacted spaces to mute and then go back to them all and unmute. - Automation rules with slack web-hooks which in theory I could also disable but finding all of the related ones seems pretty impossible. - Personal slack app integrations where people can select their own settings and that's not something I could disable/mute.
Feb 5 •Â
How do you stay informed of cloud updates?
What’s the best/most efficient way to stay informed of updates to Atlassian’s cloud products? What’s your strategy?
2 likes • 25d
In addition to the roadmap, I use the Feedbro browser extension and sign up for RSS article feeds on as many of the forums as I can. I also use that to sign up to the RSS feed from Atlassian status page for incidents.
Feb 3 •Â
JSM emailed requests - best practices
We’re planning to set up a Jira Service Management (JSM) project to handle internal (business) requests in a standardized way. Today, these requests come through a shared mailbox ( Shared mailbox is Microsoft 365 outlook.), but as the team has grown it’s no longer sufficient for tracking ownership, prioritization, reporting, or SLAs. Question: What’s the recommended/best-practice approach for setting up JSM for internal requests? Set up email forward rule ? or add external email address ? What are the prerequisites, if we need to add shared mailbox as " add external email" ?? Common pitfalls when moving from email to JSM If you’ve done something similar, please help share your ideas. Thanks in advance!!!
2 likes • Feb 4
1. Agree that moving away from email submissions is the best path 2. Document the new process and add a link to it in the form! 3. If you have some sort of Go or URL shortener, use that to give people a quick memorable way to jump to the portal/form. 4. Communicate users can find their requests after they submit (this one can be a struggle for teams that aren't use to using Jira so I recommend comms/documents/videos. 5. Outline the expect SLAs so there is an expectation of updates and users don't feel like they end up in a void.
1-5 of 5
@sara-tucker-2406
Atlassian org admin - Knowledge management nerd
Active 6d ago
Joined Nov 11, 2025
Powered by