In our Jira we have things set up like this:
Feature Issue in Project #1
>Epic Issue in Project #2
>>Risk Issue in Project #2
The Epic issue is linked to the Feature issue in a Parent/Child relationship. While working on the project, we will add Risks to the Epic issue using a Risk relationship ("Exposes risk to"/"Incurs risk from"). The goal is to have this Risk automatically linked to the Feature issue using a Risk relationship at the same time.
I have used the Automation system to monitor for any time the Risk issue link type is used and, if the destination issue type is also a Risk, run an action that's intended to link the Risk issue to the Feature Issue via the Risk issue link type, as well, but I'm having issues making it happen in a targeted manner
I either can't get it to work at all or I can get it to link to all of the issues linked to the Epic issue, but we have other issues linked to the Epic via other link types; there is only ever a single Parent/Child link assigned to the Epic, though, so if I can target that link type specifically I could get this to work the way we need it to.
I know that I'll need to write some JSON to accomplish this and I can find examples of how to add issuelinks that way, but I can't find anything about how to target it properly.
Hi @Josh N.
Can I confirm the feature issue and epic issue are in different projects? I didn't think it was possible to have a cross project parent/child relationship (unless this relationship is a type of linked issue?)
I'm also a little bit hazy on what the goal is. I'll state my understanding to provide context to the suggestion below. When 2 risk issues are linked you want to automatically link them to any feature issue that is linked to either of the risk issues. I'm a bit lost on how the epic fits into all of this?
When you're liking 2 risks issues you could try something like this (I've used the bug issue type in replacement of risk and the story issue type to replace feature)
The reason I put 2 link issue actions is I assumed that each risk could have a feature linked so you would want to update both risk issues with the missing feature link.
Hope that helps
Thanks for checking on on this John! We changed the way we're approaching this situation so the issue I'm having is no longer happening, but I'll provide some additional context since I think you're getting close to what I would have needed before and someone else might need to know.
It might help if I explain some of the terminology used a bit:
Risk - Actual risk to the project; created within my team's Jira project.
Epic - The method of tracking the project for my team; created within my team's Jira project. Will have a linked issue relationship with the Feature, as well as Epics from other teams.
Feature - The method of tracking the project for the whole department; created within the department's Jira project. Will have a linked issue relationship with Epics from multiple teams.
The idea is that our standard team members are just working in our project and the automation is taking care of linking the project risks into the departmental tracking system.
Hi @Josh N. ,
When you view a Feature, you want to see at a glance which Epics and associated Risks there are?
Could the Issue Matrix add-on be an alternative?
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events