User
Write something
Weekly Discussion / QA is happening in 46 hours
Business Space or Software?
I have not deep dived fully yet in the world of the Business Space, but I'm aware of it, which is causing doubt for me. I'm starting fresh with a setup for Large Construction Programme and Project Managers, and the cross-space/functional delivery teams and I'm wondering if I should pivot to Business spaces, or stick with Software spaces which I know well and have used succesfully in the past. The use case is a construction cross-functional teams involved in the full life cycle incl planning, pre-construction, build and handover. Keen to hear thoughts, which type is your go-to for this use case, and main reason why?
0
0
Concerning Marketing Email from Atlassian
We have now received two emails from [email protected] that are focused on this: Shaun, stay on top of your work with these prompts. What follows is a list of three AI prompts that reference data and functionality unique to our business, our systems, our own AI tooling. What deeply concerns me is Atlassian was never given permission to use our tenant data for ANYTHING. I explicitly rejected their request to share our tenant data with others when they put that out a few months back. I checked again today and that setting has not changed. Of course the deeper concern is that I have no one at Atlassian that I can even reach out to for this. Does anyone else get these messages and do they also contain data exclusive to your tenant?
Great webinar on Atlassian and Jira as a company OS!
@Josh Golosinskiy , I made it to your webinar this morning, it was really good! Just based on this video and the "Stop Asking 'What's the Status'" video, I think we can improve our environment and make it more efficient. Thanks for your time to do this and share it.
Jul 2 • 
Jira
Researching KTLO Work In Jira
Hey everyone, This is a fairly specific piece of research I'm kicking off. As individual product/engineer teams scope out their quarterly planning in Jira, We successfully completed a rollout of a hierarchy structure which connects Initiatives>Epics>Stories etc. This is giving us cross vertical visibility on all work. One topic that's arisen is how cross vertical teams such as platform, security etc who need to ensure that essential work is done by the individual Product & Tech spaces. This is essentially classed as KTLO work (essential security/maintenance/enhancement) work that falls outside of new feature delivery. Some suggestions are that the security team would manage their own backlog from a ticket perspective, and clone these work items (epics/tasks/etc) and these would sit within the corresponding project spaces to be picked up and accounted for in sprint planning. Has anyone had first hand experience of a similar situation and how was it managed, did tickets get cloned like the scenario above (which sounds very over-engineered) or is there a simpler solution? I get the cloning aspect so the Plat/SEC teams can track progress, but would love to hear any other perspectives!
Getting granular with Issue/Work Item history
We have a specific use case that is giving us fits. Here's the gist: - jira query with status transition and assignment history (assuming it's possible) of CRs - analyze with codex to create a report which would contain, at a minimum Backlog Metrics - Total "Active": the total number of CRs not in status "done", "rejected", or "in prod". - Untouched: the number of CRs which have no comments and no changes in status - Wait and Rejection Metrics (90 Day Rolling) - 90 Day Average Wait Time: the average amount of time a CR currently in status "development backlog" or beyond spent in "waiting for customer" status over the last 90 days - 90 Day Rolling Rejections: the total number of CRs moved to status "rejected" over the last 90 days - 90 Day Rejection Reasons: of those CRs rejected over the last 90 days, how many of each "Rejection Reason" occurred - Goals - Mean time to resolution (MTTR): across all CRs which are currently in status "development backlog" or "sprint backlog" or farther along in the workflow, what is the average amount of time they took to go from status "delivery backlog" to "done" In the past I looked a couple of marketplace apps but they didn't really fit our use case with specificity. So my big question is: can Rovo or a Rovo agent pull this data that I can then feed into Codex/Claude Code/Gemini for analysis. I'm thinking if we could just get the raw history of the work item the AI could do the rest.
1-30 of 72
Atlassian Everything
skool.com/atlassian-everything
An exclusive unofficial community for Atlassian users to learn, share, and build smarter solutions that make work simple. We talk Jira, Confluence
Leaderboard (30-day)
Powered by