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!

Hi team, We're looking at running a full audit of our Jira instance and have been talking to a local solution provider. To be fully transparent, our instance is chaotic and there is (was) no governance whatsoever. Outside of duplicated fields, schemes etc, I wonder what should we be looking for from the consultant, I am probably too focused in on the Jira cloud instance but really need to get best value from this audit and then look at our broader Atlassian accounts. Thanks all!

Hello community! I'll be running a webinar on April 14th and would love it if you could sign up and attend. I'll be sharing some personal painful stories about Atlassian user management and working with Open Source Consulting to demonstrate how their Atlassian cloud user management app (Flexible User License) works to help avoid the problems I've had in the past. Consider signing up -> http://bit.ly/4trLLVO

Hi team! Looking for recommendations on any plug in apps that would be good for executive level Roadmaps? Ideally something that would encompass multiple aspects (outcomes/risk/progress to completion/link to objectives/capitalization) It would need to be more narrative than just progress of work/burndowns etc), like a layer above that would be more exec friendly, or do I just Claude it?

Curious how different teams handle this in practice. What's your approach, and what drove that decision?