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; } } }

Can you create issues that are 1 to many?

John Popovecz

I have need of having a single issue that needs to be implemented in multiple versions of software. I have been playing around with JIRA and all I have been able to figure out is to create a main issue and then link it to multiple sub issues. The sub issues allows me to track the resolution of the main issue on the multiple different versions of software. This is extremely time consuming and is not scalable.

Is there a way to automate the creation of sub issues?

Can you set bulk edit so when you update a description it will update all the sub issues that have been checked (that seems pretty dangerous if you forget to check one of the sub issues, then it won't be kept updated with the same information and now the sub issues will have different information.)?

Is there a way to create multiple instances of an issue and drag that issue to multiple project backlogs?

The main reason I don't want to create multiple issues at the same level is that all the information (i.e. Title, Description, Root cause...etc) would need to be copy and pasted into the multiple issues. This will become a maintenance nightmare trying to keep all the issues up to date with the same information.

I am looking to create an issue, decide which software versions need the issue, and the track that issue in the necessary software paths without major overhead.

Is this possible?

Accepted answers

All comments

Ivan Tovbin

Hi John,

I think this is definately possible, not out of the box however. The kind of automation you described will require the use of 3rd party addons to implement. Please check this thread for a quick run down on the most popular addons. Given the potential amount of conditions I'd personally go with scripting as it gives you that much more flexibility.

Alexey Matveev

Do you use the version functionality of Jira?

https://confluence.atlassian.com/adminjiraserver/managing-versions-938847201.html

If so then there is a field called Fix Version and it is a multi select field. You can attach one issue to multiple versions.

But anyway it seems odd to me, that you solve one issue in multiple releases. I guess, you solve a part of an issue in each release. That is why I think you should create subtasks for the issue and resolve subtasks for the issue. The summary and description of the subtasks will not be the same as the summary and description of the parent task. Subtasks would define the functionality which you fix. In this case you do not need to synchronize statuses of subtasks and the main issue. You only have to resolve the main issue, if all subtasks are closed. You could do it with an add-on like Power Scripts, ScriptRunner, Automation for Jira.

For example, if you had Power Scripts, you could find a script, which would let you do it here:

https://confluence.cprime.io/display/TR/Post+Functions#PostFunctions-Auto-transitionparentwhenallsub-tasksareresolved

Matthias Gaiser _K15t_

Hi John,

you could also use an issue sync solution for that.

You would configure integrations between all the projects where you want to share the copies of your issue and the solution will take care that all the issues stay in sync. You can furthermore control which fields you want to keep in sync and more config options depending on the solution.

As a member of Backbone Issue Sync, I'd be happy to give you a demo & discuss how you could solve your use case. Let us know via support@k15t.com if you like.

Cheers,
Matthias.

John Popovecz

Alexey...thank you for your response. Sorry for the lateness of mine.

Imagine you have a group of s/w modules that go on the car. Each performs different tasks...one could be for ignition control, one for the sun roof control, one for locking. Each of these modules has some similar features that build the foundation (I am not talking about the drivers and such) for example something that monitors the voltage to the module is within a tolerance. This feature is common to all the different modules.

What I am trying to solve is if in our example there is an issue in the voltage monitoring feature in one of the modules then it is probably in all the modules because it is a common feature across all the modules. I do not want to have to add an issue for each module with the same information and same discussion as eventually they will get out of sync with each other and then which issue is correct.

I am trying to find a way that an issue on the voltage monitoring could be logged and I have a single repository for all the information detailing that issue. I would like to have a way to tie the multiple modules to this issue so the different teams can review their software for that issue and track the resolution.

I know I can do a main issue and then create child issues. This is quite tedious and screams for automation to create the child issues. The team is investigating that now.

Is there a more efficient way to resolve this problem?

I will investigate your links

John Popovecz

Thank you Mattias. I will pass your information to the JIRA team.

John Popovecz

Thank you for your response Ivan. I will check out the referenced thread.

Jack Brickey

So why not just use Jira Automation to create the sub-tasks based on say Component?

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

issue-link