Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Root cause analysis of the defect or incident

Hello JIRA community,

I am looking for a process or methodology or an tool that will serve purpose of my team. We often get defects and incidents during the software development projects.

And we resolve the defects ideally.But we never go for the root cause analysis of the defect.

Like asking why the defect occured ? What is the root cause ? and so on

Ideally would be good to have such a process that find the root cause of the defect and offcouse documentation of these reports is always is good idea.

How do u look for this problem ? Is there any solution to this problem ?


Looking forward for the answers.



1 answer

0 votes
Craig Nodwell Community Leader Sep 01, 2022

Hi @vinayak biradar documenting the bug well.  Linking it to the change ticket that created the bug.  Linking Jira to your version control system and build system.  Developers put Jira ID's in commits, allowing the build system to read the changelog, the build system can then report what went into a build these details can also be passed to any package retention system re: nexus/artifactory .... Have a look at Atlassians Open DevOps. 

Hei @Craig Nodwell 

I appreciate ur fast response. But however I am looking for some tools or processes that support the problem.

Namely the methodology or a systematic process.

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events