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?
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.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that should work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.