I am trying to make an automation that creates a specific type of link when an issue is linked to another. For example, we have issue types R (risk), A (assessment) and M (mitigation). Issue R is an epic type.
I would like to make it so that when A is made a child of R, it also creates a link with type "is assessed by," but when M is made a child of R, it creates a second link with type "is mitigated by."
Hi @Lana Kelly,
While this is technically possible, why would you want to do this? The parent - child relationship already identifies that the two issues are connected, so I am not really seeing the added value of the additional link.
Can you elaborate a bit more on the goal you are trying to achieve?
In the meantime - for a technical answer to your question, you can set up an automation that looks like this:
I don't have the same issue types and link types you mentioned in your initial ask, but those are the only things you would need to adjust to your scenario.
Hope this helps - but still very much interested in your use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The long and short of it is that we have an app that tracks (for example), how many risks are linked to a risk category and displays links to those risks. It counts based on the type of link. I want to make an automation that will automatically apply a certain type of link to an issue when it's made a child of an epic, depending on what type of issue it is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is what I have so far, but the {{destinationIssueType}} isn't the right key, I don't think.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Lana Kelly, no indeed it isn't 😅 - if you insist on using smart values instead of the approach I shared in the screenshot above, try:
{{destinationIssue.issueType.name}}
to refer to the issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Walter Buggenhout I tried your approach, and it works, but we didn't have the parent field in this issue type, because we wanted to call it "risk category" and just use the linking function. I was just wondering how it would be done if we did it that way. Thanks for your help.
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.