nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation for GitHub branches for multiple Jira tickets

Joshua Hong

I'm looking for a solution to be able to handle multiple Jira tickets from the actions of a single GitHub branch.

Scenario:

You have issues JIRA-1, JIRA-2, and JIRA-3

You create a GitHub branch JIRA-1. You make changes for JIRA-1 but also find some easy and quick fixes for JIRA-2 so you stick it in there as the work is similar as a separate commit. So you have the GitHub branch JIRA-1 with commit #1 JIRA-1 and commit #2 JIRA-2.

Now a PR is opened for branch JIRA-1 with these changes, and merged into the release branch. Once the GitHub Action completes and deploys the changes, I would like to transition both issues JIRA-1 and JIRA-2 into a new workflow such as "Deployed and Ready for testing".

In the given scenario, I am able to handle 1 ticket very easily through Jira Automation. Is there any way to also transition JIRA-2 along? I've tried setting up an automation to link these issues but haven't found a way to. The only options I have are linking to the "Triggered Issue" or "Latest Created Issue" which would be JIRA-3 in this case.

Accepted answers

Bill Sheboy

Hi @Joshua Hong -- Welcome to the Atlassian Community!

Without seeing your entire rule for context...

In automation rules, you may type in a smart value for the target issue's key for the link. That is not obvious from the rule editor as it only lists the options you note in the dropdown list.

Just type in the smart value, and when it appears below the field, select it to use it.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Joshua Hong -- Welcome to the Atlassian Community!

Without seeing your entire rule for context...

In automation rules, you may type in a smart value for the target issue's key for the link. That is not obvious from the rule editor as it only lists the options you note in the dropdown list.

Just type in the smart value, and when it appears below the field, select it to use it.

Kind regards,
Bill

Joshua Hong

Thanks Bill, ultimately I'm trying to do something like this:

The goal being
1. When a deployment is successful:

2. For every commit message as part of the deployment
2a. If the commit message has a Jira issue key
2b. Then move the Jira issue to QA Deployed

3. Move the issue in branch name to QA Deployed.

The problem for me here is being able to grab the issue key in the commit message. This checks that one exists but I'm unable to understand how to reference it.

Bill Sheboy

Thanks for that information.

I am not using the dev automation features of rules currently. From what you show, I believe you will need to extract the key(s) and then use a branch on JQL to access them.

To do this, you will need to use the text functions to produce a list of keys, and then use JQL like this: key IN ( extracted list of keys separated by commas )

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud