Problem transitioning Status from JSW issue in JSM issue

Mario Capellari February 13, 2025

I am attempting to:

  • Change a JSM issue status to match a JSW issue status when it's being changed

Current working setup:

JSM (project A)

  • Issue is created

Automation:

  • Create a new issue in JSW
  • Link the new issue as "relates to" to the JSW issue

JSW (Project B)

Automation:

  • BRANCH
  • When: Issue transitioned
  • Then: Transition the issue to COPY FROM TRIGGER ISSUE

Here the automation configuration which is in a Multi-project scope for both the projects Project A and B.

2025-02-13-Audit log - Automation - Jira-002697.png2025-02-13-Audit log - Automation - Jira-002698.png

The problem is I am getting this error when changing the status in the JWS issue.

2025-02-13-Audit log - Automation - Jira-002696.png

I also created all the matching status fields in the workflow in the JSM project.

Do you have any ideas what the problem is? The error message is not really that helpful...

1 answer

0 votes
Fernando Eugênio da Silva
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 13, 2025

@Mario Capellari , Welcome to the Atlassian Community!

Things that you may need to consider:

- If you have an available transition to the destination statuses

Let's say that your current status in your JSW issue is To Do, so Jira will not to make an auto transition for the same statuses.

Now let's say that your current status in the JSW issue is In Progress, you need to make sure that you have an available transition connecting the In Progress and To Do statuses.

If you don't have available transitions connecting your statuses, the automation will not be able to operate your transition.

Have you checked this?

Mario Capellari February 13, 2025

Hello Fernando!

I did check to make sure the structure of the transitions match - here both workflows - JSM on the left, JSW on the right. 

snapshot-0213_1938.jpg

Mario Capellari February 13, 2025

Instead of using the Branch iterative values for all statuses, I replaced it with specific "In Progress" and "Done" statuses. Same setup otherwise, and that works now. 

So the problem seems to be in the list the Branch is sending to the Transition node.

Suggest an answer

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

Atlassian Community Events