Linked issue status syncing

Aron Entler February 14, 2024

I've looked through all the other questions related to this challenge I am having but I haven't found one that matches what I am trying to do. Hope the Jira brain trust here can help me.

Here's what I am trying to do. 

When a new issue is created (alert issuetype) one of the first steps an analyst will do after acknowledging it is to see if there an existing alert that is already being worked on. 

If one exists the analyst will use the the outward relates link of "relates to parent". 

I am trying to create an automation that'll then update the issue to match the status it is being linked to. 

My lizard brain would think that this automation rule would work but I am getting this error.

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):
SCRT-152 (Work in Progress - 10145)
2024-02-14_12-02-37.png
No idea what the error message is saying. They are the same issuetype and workflow so I wouldn't think there'd be much of an issue.
If I can get this sorted out within the same rule I want to create one going the opposite direction where the analyst is in the parent alert and is adding a "relates to child" inward link to a new alert.

Hope this is simple. Appreciate the assistance.

3 answers

0 votes
Aron Entler February 15, 2024

Just to make sure the issue could transition from Open -> Done using automation I created a basic manual trigger transition. This worked correctly.

2024-02-15_10-46-56.png

I also tried the applicable suggestions mentioned in this article with no success.

Solved: Destination status could not be resolved. If using... (atlassian.com)

0 votes
Kai Becker
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 14, 2024

Hi @Aron Entler 

how does your workflow look like? Is there a transition going to this specific status in the issue the error occurs? Jira Automation can only use valid transitions between statuses. 

Aron Entler February 14, 2024

Hi Kai,

Yes there is one. I also tried using my own account in the rule. I saw the question on the error code and ran that down already. Really hoped that would solve it. 

Aron

Like # people like this
Kai Becker
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2024

Hi @Aron Entler 

it might have something to do with the parent. I actually do not fully understand the rule or hierarchy of your issues. 
But if I'm getting it right, the related issues should get the status of the trigger issue, right? If so, you could try to transition to the status of the trigger issue instead of the parent.

Aron Entler February 15, 2024

Thanks for the response @Kai Becker

 

Here's what I am trying to do. Hope it adds the clarity you're looking for.

I have 2 issues (ISSUE-30 and ISSUE-40). They are the same issuetype and using the same workflow.

The workflow allows the transition to happen but is hidden to only automation-addons-admin.

ISSUE-40 (status "Open") similar to ISSUE-30 (status "Pending Customer").

I want to link them together so ISSUE-30 is the parent of ISSUE-40 and for ISSUE-40's status to change to ISSUE-30's status.

I am using the "Relates to" link with outward being "relates to parent" and the inward being "relates to child"

I need this to happen whether I am in ISSUE-30 and link ISSUE-40 (relates to child) or if I am in ISSUE-40 (relates to parent). Therefore i can eventually make it so wherever ISSUE-30 goes in its transitional adventure ISSUE-40 follows along.

Using the original screenshot above and change it to "trigger issue" from "copy from parent". If I am in ISSUE-40 and set the link to "relates to parent" to ISSUE-30 then ISSUE-30 status is changed to ISSUE-40. The opposite of what I am looking for.

Hope this helps. Really appreciate the assistance.


Aron

 

Like Kai Becker likes this
Kai Becker
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 16, 2024

Hi @Aron Entler 

thanks for clarification. I guess the other way round should also work, with checking for the opposite link type and also copy from trigger issue. I guess you could add it to the branching as well.

AFAIK the problem with parent is, that it is only working for hierarchy that is known to Jira, for example Task -> Sub-task or Epic -> Story
You basically just linked two issues of the same level. Even though it is a parent link type, this is not a real parent child connection.

Kai Becker
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 2, 2024

@Aron Entler hope you are doing fine. has this been resolved? If so, please make sure to accept an answer to mark the question as resolved.

If it has not been resolved, please feel free to get back with an update.

0 votes
Uday Kiran Bhaviri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 14, 2024

Hi @Aron Entler 

I guess first you need to get the parent issue status and then transition this issue to that status( make sure it exists) using some smart values.

Aron Entler February 14, 2024

I have no idea how to even do that to test it. ;-) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events