Traceability of UAT/ Production defects to Sprints

Question

Hi All - I have raised the following Qn few days back and I haven't seen any response to this. I am wondering and thinking, did I answer something stupid or this is something which none of us have an answer! I felt, this is a valid usage scenario of JIRA and hence asked to get an expert opinion. Let me know.

/ George

----------- my original ask

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!

Bill Sheboy · Answer

Hi Tom,

If this approach works out for you, please consider posting some details of your solution and then marking this question as answered.  That will help others learn and try to apply it themselves.  Thanks!

__Bill

Tom Geo · Answer

Thanks Bill! Your suggestion is a good work around - playing with label and component option.

/ Tom

Bill Sheboy · Answer

Hi @Tom Geo

There are probably marketplace tools to enhance testing and traceability support.  I haven't used any of those for JIRA Cloud, so my thoughts are how to support your idea with out-of-the-box JIRA.

You note the team is using the Bug issue type during sprints.  The team could also use Bugs to track defects found after a sprint closes.  The key is how to trace back to the stories which comprised the MVP/MVPe, and so back to the sprints.  To help, the Component and Label fields could be added to stories to identify areas of the feature.

When the stories are well-composed (aligned with INVEST), it should be straightforward to add a link to the found Bugs which trace to the story using the type-ahead search to find them with the story Summary.  You can then use filters and dashboards to report on what you need for defects, referring back to the Component and Label information.  For more advanced reporting, consider exporting the relevant items to spreadsheet tools or use the REST API to access the data.

Best regards,

Bill