Bug and Development Request Management

[Joseph Gillis]

Hi Everyone, 

I am pretty novice at this so far, and haven't been able to search my way into an answer. Likely due to not knowing the right terms to search for. 

I am trying to sort out a good process for managing development requests and bugs within the teams backlog.  If there are any articles that can be referenced it would be greatly appreciated. 

We were thinking of using project for intake, with "done" being an item created within the proper project & prioritized appropriately. Is that a common practice, or are we headed the wrong direction?

Thanks, 
JD

[John Funk]

Hi Joseph - Welcome to the Atlassian Community!

Can you give us a few more details in what you are actually trying to accomplish? Is your question about Bugs as they relate to Development tasks that are identified during testing? Or are you asking about how to handle the list of all of the Bugs that have been identified along with new development? Or is it something else?

[Joseph Gillis]

Hi John, 

Thanks for the reply and sorry for the ambiguity.  I am trying to set up a process to triage customer facing bugs, internally identified bugs and feature requests, so they are assigned to an appropriate Jira project and prioritized appropriately.

We are pretty ad-hoc on this right now, and I would just like to have a defined process so the proper fields and labels get filled out and we have some consistency in how things are handled. 

Does that help?

[John Funk]

Mostly  :-)

Here's what we do - we have different issue types in Jira for Bugs, Defects, App Features, Landing Pages and Software Engineering (generic dev only tasks not apart of the others).

Here's a little guidance on defining a Bug and a Defect for us during the QA process. If a QA Analyst finds something that doesn't work, there is a decision made as to whether the code can still be shipped with the problem or not. If it can still be shipped, a new issue is created as a Bug and placed in the Backlog to work later. 

If the problem prevents the code from being shipped, a new issue is created as a Defect which is a sub-task type of issue and is directly related (child) of the app feature, landing page, or software engineering type. The parent cannot be marked Done if any of the children (i.e. sub-tasks/defects) are still open (not in Deploy or Done statuses). 

The product manager (or senior lead developer) will determine what gets worked between the bugs, and non-defect development issue types.  Then the team agrees to this before work is started. 

As a side note - problems found in production (no matter by whom) are created as Bugs in the system and worked according to the previous paragraph. 

Does that help address what you are trying to do?

[Joseph Gillis]

Thanks John, that does help. 

The last missing piece for me is how feature requests are handled. They come from the field or internal customers, and I am not sure how to backlog the requests so they can be screened for viability before moving into an appropriate project backlog.

Do you have any suggestions for that?

[Vladimir Taranchenko]

Y can move REQ issues betweeen projects or use addittional project for high level bussiness requitements.

[John Funk]

We handle feature requests by using the issue type App Feature. You can create one with whatever name you like. But that work just goes in the mix with everything else each week when the team determines the new priority of items to work on for the week.