nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the "Best Practice for Sharing Bug Information across multiple Jira Projects?

DSell

Scenario: A code block is used across five Jira projects and customers. In project 1, customer A identifies a bug and creates a bug ticket within that Jira project. The need is to ensure this is fixed in the other four projects.

There have been multiple internal suggestions for this, and I was wondering how others suggest this is handled.

A suggestion I hear a lot from the engineers is to create four bug ticket clones and then move one clone to each of the other projects. I see several apparent problems with this one.

Thoughts?

Accepted answers

All comments

Craig Nodwell_7eve9b

Hi @DSell couple questions.
Do you have integration between Jira and the version control system?
Does the bug(s) have to be fixed in multiple code repositories?
When a bug ticket is logged does it always follow that pattern of fix in 5 projects, or are there exceptions?

John Funk

Hi @DSell

I can think of a couple of approaches. One is to do the clone thing as you describe in your question. However, I would link all of the tickets together when they are cloned using automation. Then setup another automation rule that when one of them transitions to another status then all of the others transition with it. That way everyone sees who is working on the bug and the status it is in.

The other option, and I believe better one, is to use a single board that shows bugs from all of the projects. Then I would add a custom field - probably a checkbox type field - with each of the projects affected by the bug. Then you could add quick filters to the board based on each project to quickly only see bugs affecting that project.

DSell

Hi @Craig Nodwell

Do you have integration between Jira and the version control system?
1. No integration between Jira and GitLab yet.
Does the bug(s) have to be fixed in multiple code repositories?
1. Same Gitlab repository (I think)
When a bug ticket is logged does it always follow that pattern of fix in 5 projects, or are there exceptions?
1. There are expectations, such as project-2 may have a customer that does not want the fix or wants it fixed differently.

DSell

@John Funk I think I like your second option. Instead of using a new custom field, could the "affects version" field be used for this? Assuming that each project has, its own unique version naming.

John Funk

Yes, that should work.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server