How can I automate change of status between two projects?

[Aaron Mccollough]

In Jira Cloud, I am working with 2 projects:

1. Customer Service Project (CSUP)
2. Repo Prioritization (RP)

When certain types of issues are raised in CSUP (a  service management support project), I clone them and move the clone to RP (an internal product kanban project).

I want to set up an automation that will watch these cloned issues in RP and, when the status changes on one of them, will automatically change the status on the original issue in CSUP (which is automatically linked as part of the cloning process).

I’ve tried setting up rules for this several different ways, but the status of the CSUP original issue doesn’t change when the RP clone of that issue changes.

This is a basic recipe I've tried:

This is a more complicated attempt:

I seem to be getting hung up on 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)”

I’ve tried sharing globally and with only the two projects in question (CSUP and RP).

I’ve also checked to make sure “atlassian-addons-project-access” has permission to transition issues, which it does.

I’m starting to get frustrated… thanks for any help anyone can offer.

[Mark Chaimungkalanont]

Hey there Aaron,

Yeah, the error here is interesting... "Destination status could not be resolved" the issue is likely that the Status in CSUP and RP may be different, even though they are superficially the same? Are they sharing the same Workflow?

Cheers,

Mark C

[Fabian Lim]

Hi @Aaron Mccollough:

Thanks for the screenshots of the workflows. I think I understand what you are trying to accomplish. Based on your requirements, you will have to create several rules that are similar in nature. You have to think about how the statues in RP map to CSUP.  I have taken a stab at how I would do it. The following rules would be created from the RP Project and set to multiple projects.  

1.RP moves from to do to In progress -> Original issue Transition to In Progress (Rule assuming that you have cloned the issue manually and it's linked via the clones relationship from the RP issue to CSUP Issue).

2.  RP moves from in progress to Done -> Original Issue transition to Done

3. RP moves from any status to Future Sprint Queue or Unprioritized Work -> Move original issue to Pending

I hope you get the idea. You may want add extra conditions for issue types if needed.  

Fabian

[Aaron Mccollough]

Ooops... deleted.... still testing...

[Fabian Lim]

Hi @Aaron Mccollough

Do the linked issues have a transition thst allows you to move to "copy from trigger issue"? Especially for csup-28.

[Aaron Mccollough]

Hi @fab

I'm nor sure, but I suspect no. I know how to edit workflows in a basic way, but I haven't seen reference to that particular allowance. How does one create such a transition? Do you create "copy from trigger issue" as a step name? 

[Fabian Lim]

@Aaron Mccollough:

You may want to take a look at the rules here: https://www.atlassian.com/software/jira/automation-template-library/rules#/labels/global/customLabelId/21570

You are basically looking for a rule that updates the following way:

From the RP Project:

1. trigger: issue transitioned

2. conditions: a specific condition to ensure that you pick up the cloned tickets

3. branch: to original issue through linked issues

4. Action: Transition issue to the corresponding status

Note: In order for this to work you have to ensure that the status matches in both projects. Or you will get transition errors.  

I hope this helps.

[Aaron Mccollough]

I'm still not having success. I suspect the problem is a mismatch between workflow transitions and or status correspondence, but I can't figure out how to get them to match.

I am able to set up an automation on RP that will transition the CSUP-original linked cloned issue from "Open" to "Pending," but I can't get it to work with any other status (such as "Open" to "In Progress"). 

Here is the workflow for CSUP:

And here is the workflow for RP: