Creating issues and tracking in JIRA

[Chimena Ijeh]

What is the best approach to capture and track issues identified during app development as they get resolved? Can issues to be resolved or clean ups done during a sprint be sized as part of the Sprint backlog item?

[Bill Sheboy · Accepted solution]

Hi @Chimena Ijeh 

You appear to asking a question that depends upon how your team does work.  For the community to help, you may need to provide more details.  For example...

• Some teams consider finding and resolving defects as part of the original request, and so there are no separate work items created
• Other teams track each defect found and addressed as sub-items of the original request
• Others may track defects as independent of the original request.  That can allow them to fix items, defer items considered for later fixing, or even to abandon them as "won't fix".

The matter of sizing is similarly dependent on how your team works: some teams never size them, some teams always size, and some size based upon whether or not a defect was within the original request's work scope.

If you can clarify how your team works the community will be better able to offer ideas.  Thanks!

Best regards,

Bill

[Chimena Ijeh]

Thanks Bill_Sheboy for your answer to my question. I guess I was trying to find out what is best approach out there.

We are currently doing a bit of the first and last approach listed in your response depending on the situation or amount of work required to fix the issues.

[Bill Sheboy]

Thanks for explaining that, @Chimena Ijeh 

I personally do not believe in "best" practices; only better ones.  :^)  I have found that as teams improve, something that worked earlier could be less helpful later.  Please discuss with your team and consider when a practice needs to evolve to support the team.

Best regards,

Bill

[Chimena Ijeh]

Absolutely true @Bill Sheboy 

[Mariana_Pryshliak_Saasjet]

Hello @Chimena Ijeh 

You can try both Time in Status for Jira Cloud and Time between Statuses. 

Time in Status for Jira Cloud calculates the time an issue has been spent in each status.  Also, you will get the Assignee Time report, which shows the time that a particular assignee was assigned to each issue. And the Average Time report – a grid with average time issues have been spent in statuses during a specific period.

Time between Statuses calculates how long it takes an issue to move from one status to another. To set calculation you need to create status groups by choosing Start/Pause/Stop statuses through which issues have been moving in your workflow. So you can choose any start and stop statuses you want. These can be even the first and last statuses from the workflow.

If you have any additional questions, feel free to contact me:)