Linking Production defects to Sprint/ Iteration

[Tom Geo]

Hi - I am struggling with this fundamental scenario (described below). If any of you have a suggestion, please revert.

We have planned an MVP with 5 Sprints and Sprints are being delivered in a sequential manner and getting accepted by PO. These Sprints, in isolation is not being delivered to Production. We plan to complete the Iteration (of all 5 Sprints) and then move to Production. Before moving to Production, there will be a UAT as well (on top of the acceptance by PO at every Sprint). I know this might sound a little Hybrid approach, please excuse. (If there is any other suggestions, let me know.)

In the above scenario, how can I track the UAT/ Production defects on Jira? How can I establish a traceability of these latent defects to a Sprint?

Currently, we use Bug (issue type) to report all In-sprint defects.

Thanks in advance!

[Radoslaw Cichocki {Deviniti}]

Hi @Tom Geo ,

If you need to track traceability then TestFLO has this in the form of a tree-like requirements traceabillity report.
That's if you're looking a tool that's flexible to suit any kind of process, integrates with any requirements management approach, and supports auotmated tests, but exists for server and data center deployments only.

If, on the other hand, you need a tool that exists for all kinds of hostings, including Cloud, and comes with a built-in requirement management module, quick setup, great user interface, easy to use, and you can live without automated tests integration (temporarily, since it's on the roadmap), then RTM is the way to go. It has a traceability matrix.

Regards,
Radek

[Bill Sheboy]

Hi @Radoslaw Cichocki {Deviniti} 

Just wanted to confirm: have you used these products or are you a marketplace vendor, perhaps for one of the products you are recommending?

Thanks!

[Radoslaw Cichocki {Deviniti}]

Hi @Bill Sheboy

I am the product manager of TestFLO, and both products come from the Deviniti group.

Regards,
Radek

[Bill Sheboy]

Thanks for clarifying.  It helps the community in reviewing answers when they know if the source is a product user or a vendor.

Please see here for more information.

Atlassian Community online guidelines for Marketplace vendors and Solution Partners

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Atlassian-Community-online-guidelines-for-Marketplace-vendors/ba-p/689723

Thank you.

[Radoslaw Cichocki {Deviniti}]

Thanks @Bill Sheboy , I'll remember about it the next time, and thank you for the link, I will apply what's mentioned there.

Regards,
Radek

[Bill Sheboy]

Hi @Tom Geo 

Your approach may depend on how you are managing UAT scenarios...

• If you are executing UAT scenarios independent of JIRA tooling, you could just create defects (bugs in JIRA), identify the Story that was the source of the defect, and then link the Bug to the Story.
• If your tests are somehow stored in JIRA and linked to the stories, you would link your Bugs to the tests, which would then link to the stories and their sprints.  (You could do the test management with native JIRA or with add-ons.  Please see here for more information: https://confluence.atlassian.com/jirakb/using-jira-software-for-test-case-management-136872198.html )

In either case, you cannot create a traceability report (Bugs to Stories to Sprints) with native JIRA.  You would need one of the marketplace add-ons, or export to a spreadsheet to perform your own analysis by joining on the linked fields.

Best regards,

Bill

[Tom Geo]

Thanks Bill for your suggestion!