You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Has anyone out there created a RAID log on Jira?
If so, do you have any practical examples of your RAID log? Would there be an Instruction and/or 'Idiots' guide you wrote to inform people on how to create a RAID log on Jira and then to report off Jira or link it to Confluence??
Hi Richard,
I've created something like it for my company: i've been able to track Risk, Issues, Dependencies (but for this i recommend the standard features like issue linking or the dependency report if you use Portfolio). We didn't find much usage for assumptions since it's usually a static-type of information, but you could have a new -> accepted kind of flow.
Technically I've defined new issuetypes, with all the configuration stack around them, to create a completely custom life cycle of information, with custom fields to identify programmes attribution, escalation paths, and of course report boards in confluence (made with the Jira macro + ad hoc filters).
My suggestion is to use this map https://confluence.atlassian.com/jira064/configuring-fields-and-screens-720412098.html as a reference to guide your decision as you define the items you need piece by piece. A testing environment is suggested too. :)
By using new issuetypes, you'll be able to add RAID logs to standard team projects or in dedicated standalone registers.
Hope this helps!
Create "RAID Register" under the backlog (defined iteration path), then create Features as "Issues, Risks, Dependencies and Assumptions" referring Fiscal Year Cycle. Under these Features create respective User stories as per PI cycles duration.
hope this would help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.