How to organize regression bugs effectively?

[asadiq]

I wanted a piece of advice to organize the regression bugs. 

If sprint issues are found, they are usually listed under relevant user story. When some regression issues are found during sprint testing then we can list them as an independent bug as they don't belong to any particular story.  At the end of the sprint, it might be challenging to keep track of such bugs. Alternatively, some of the regressions issues might not be fixed at the end of the sprint or spill across the next sprint.

Moreover, I can create a user story and list all the regression issue under this user story but again, it is likely to carry forward at the end of each sprint as regression is ongoing effort.

Can anyone help me with the best advice to keep and organize such regression issue.

[Atlass Monster · Accepted solution]

@asadiq  How you doing mate?

Make a new issue type. Call it for example "Regression issue". 

How to make a new issue type: https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/

Associate it to the project scheme: https://support.atlassian.com/jira-cloud-administration/docs/associate-issue-types-with-projects/

In the Sprint board make a swim lane just for that type so you can't really miss it from the view. 

I suggest you utilize dashboard for weekly reporting on those issue types. 

I hope that helps. 

[asadiq]

Thanks buddy!!!

[asadiq]

Hello

I have realised, I need permissions from Admin to do so. 

Is there any workaround on top of your head?

[Atlass Monster]

No mate, you can to ask your Jira Admin to do it for you. 

Not sure but if you are on a "team-managed" project you may do it without being org Admin.

[asadiq]

Unfortunately, I am in a company-managed project.