Auomation for fix version and issue

Narsha Bac May 19, 2024

Hello Team,

I am working on an automation and I needed some help. I will try to explain the use case for it to be simpler.

  1. An issue (issuetype milestone) is created automatically via an automation when a version is created. The version's name is copied in the issue's summary and the dates (start & release date) are also copied in a custom field respectively. This is working fine.

    Screenshot 2024-05-20 090529.png
  2. When a version is added to an issue (issuetype initiative), I have to link the milestone (which corresponds to this version) with the initiative. For e.g if a fixversion with the name 'Go live' was created, a corrresponding milestone was creating with the name 'Go live'. When I add the fix version 'Go live' on my initiative, this initiative must be linked with the milestone Go live.

    Screenshot 2024-05-20 090525.png

I have attached both automations. For the second point, I have tried building something but nothing is happening with no error.

Can you please help?

Thanks.

1 answer

1 accepted

1 vote
Answer accepted
Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2024

Hi @Narsha Bac 

As per your image, for the trigger "Fix Version Changed" in "Initiative", so I'm assuming you're tracking only one issue type in this change, further in your automation you're using the branch JQL-> "issuetype =Milestone", this might not work since the trigger issue is a Initiative and the current branch falls out of it's scope.

In order to identify each step and the values it's running with I'll suggest you use the " Log Action" to print the tickets at each step, see if the jql you're using is giving you the actual value you need.

Narsha Bac May 20, 2024

Hi Jehan,

Actually the JQL is fine but the comparison is not working. Can you please advice what is the best approach for this automation, based on what I explained? Maybe I am using the wrong conditions.

Regards,

Narsha

Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2024

Tried the automation at my end too, the "TriggerIssue" smart value doesn't seem to work for this use case, you need to use the {{fieldChange.toString}} instead. Below is a snippet of the automation that worked for me: (used EPIC instead of Milestone)

image.png

 

I haven't tried linking the issue, but the Log Action worked, so I'm assuming the Link issue should work as well.

Narsha Bac May 20, 2024

I tried but it is not linking the issue. Can you please confirm what smart value is used here?

Screenshot 2024-05-20 132330.png

 

Thanks.

Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2024

Sure, I've used the "lookupIssues" smart value which lets me reference the Lookup table's issues from the previous step :image.png

Ref: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

Narsha Bac May 20, 2024

This is working perfectly! The milestone is being linked with the initiative.

I am attaching the automation for any future reference for the community.

Thanks a lot for your help!

Screenshot 2024-05-20 145352.png

Regards.

Like Jehan Bhathena likes this

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