Where can i find already built workflows for bug management?

[Elinor Brucker]

I'm looking for a best practice workflow process for tracking bugs in jira that i can just copy to my project.

we use this project only for bug tracking and it is not part of kanban/scrum process.

[John Funk]

Hi Elinor - Welcome to the Community!

I would suggest you still follow a Kanban process to handle your bugs. Not all bugs get worked immediately and should be a part of your backlog until ready to be worked. Plus, by having it as a part of a Kanban process you get full visibility into all of the things your team is working on. 

You can create an easy workflow for the Issue Type of Bug that goes to Backlog -> Develop -> Test -> Deploy -> Done. You can decrease or increase the number of steps if you like. That way you are following a process and can still report on Bugs. 

I hope that helps!

[Elinor Brucker]

Thanks John, I appreciate your reply and suggestion yet for now i'm looking for a bug management workflow specifically . I have searched the web and couldn't find such scenario that is described in details and only related to bug life-cycle :\

[John Funk]

Here is what we use. It is a little more involved than most. We also use a flexible process where the issue does not have to go through Code Review, Merge, or Package Review. Package Review is used for iOS and Android app changes. 

Let me know if you have any other questions. 

[Elinor Brucker]

Thank you John for being so responsive. sharing is caring.. :)

however this is still not what i'm looking for. I only need a workflow for bug life-cycle.

I started working on it on my own but i'm new with Jira and I'm not sure i'm doing it right so i was hoping to find some kind of template or use case online.

the statuses should include: new, open (not sure if i need assigned as a status), fixed, reopen, verified, closed. i'm not sure how to handle negative scenarios where the defect is rejected for "as designed", "duplicate", "not relevant" "deferred".

it's important to me that the development team will be limited with handling the defect so they would only be able to open a new defect, change status to duplicate, not relevant, need more info and fixed and of course assign. verify and closed should be done by QA at the moment (no product manager in sight for now).

i hope i was more clear this time :)

if you or anyone else know of a relevant available workflow i'd love to learn from it.

thanks :) 

[John Funk]

Hey Elinor,

It looks like you still need to create your own workflow with the statuses you desire (what you have listed in your last post). Then you can control who can do what based on conditions on the transitions.