Automation to align status between JPD and Jira
Asked by Rebecca Graf:

Hey all,

I'd like to create an automation, which checks if a status of delivery tickets in Jira is aligned with the JPD ticket (only in a certain JIRA project).

The challenge: Our workflow in Jira is different from JPD, meaning that I need a mapping like

if status in JPD is A please set status of linked issue in Jira project X to B

if status in JPD is C please set status of linked issue in Jira project X to D

and so on...

The automation should run regularly without being triggered by a status change. How do I set it up properly?

Thanks for your help :-)

Best

Rebecca


Answers:
author: Nick H
body: Hi [@Rebecca Graf](/t5/user/viewprofilepage/user-id/3020706) ,

An automation like that one below should work for the use case - which uses multiple IF / ELSE components to map each JPD status to Jira status:

![status1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346634i8DF836A008EB9392/image-size/large?v=v2&px=999 "status1.jpg")![status2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346635iC81485F4D59B1351/image-size/large?v=v2&px=999 "status2.jpg")

1) WHEN: Issue transitioned

2) IF / ELSE

* Status = "JPD status A"

3) Branch rule / related issues

* Type of related issues = Linked issues
* Link types = is implemented by

4) THEN: Transition the issue

* Destination status = "Jira project X, status B"

5) IF / ELSE

* Status = "JPD status C"

6) Branch rule / related issues

* Type of related issues = Linked issues
* Link types = is implemented by

7) THEN: Transition the issue

* Destination status = "Jira project X, status D"

\^ And so on depending on how many JPD idea statuses you want to map to Jira issues statuses.

So each *IF / ELSE* component should be tied to the top *WHEN: Issue transitioned* component, and each *IF / ELSE* component branches after to look for the delivery ticket.

If an *IF / ELSE* component does not match (Ex: steps 2-4 above), the automation will then check the following (Ex: steps 5-7 above), and so on, until a there is a match - then stop reviewing the following *IF / ELSE* components after the match.

Hope that helps! Let us know if you have any questions.

comments: author: Rebecca Graf
body: Hi [@Nick H](/t5/user/viewprofilepage/user-id/2540930) , thank you so much for your explanation, that definitely helps.

Just one more question: Would it be possible to run this automation without a specific trigger (step 1) but on a daily basis? There can be usecases, where we'll have a mismatch between the two tools and I'd like to cover them as well (without waiting for a transition in JPD).

Haven't done anything like this before and didn't find an explanation how to run an automation regularly without trigger.

Best regards

Rebecca


author: Nick H
body: Hi [@Rebecca Graf](/t5/user/viewprofilepage/user-id/3020706) ,

Yes I believe that should be possible with something like this is as the main trigger instead:

![sched1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346854iA4E7F51EC0499897/image-size/large?v=v2&px=999 "sched1.jpg")![sched2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/346855iC13A33D72A9A8F9E/image-size/large?v=v2&px=999 "sched2.jpg")

\^ Where the automation is scheduled to run daily (or depending on your use-case).

Notice I also added a [JQL](https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/) to specify that this automation only executes for my JPD project / ideas - which will help narrow down the number of times this actual runs.


Tags: automation

linked-issue

status