Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Add repository name to 'Component' field when branch is created

Background:

Currently, the way our workflow is set up is when a developer is working on a ticket, they must add add the release that the ticket will be apart of to the "Fix Version" field on the Jira ticket. The name of the release is based on the name of the repository where the branch is created to work on the ticket. So basically, our release name format is "[repository name][Repository Version Number]". 

We are trying to automate this process using a mixture of Jira automation and jitterbit functionality. Ideally, what we want to happen is:

  1. When a branch is created, the repository name of the created branch should appear in the Components field.
  2. Jitterbit should then be triggered to look to the Component field and then identify the latest release with that repository name and add that release to the 'Fix Version' field. 

Problem:

We are currently having trouble with the first step in this process and hoping someone could help us. We currently have the following automation rules set up:
2022-01-13 15_55_11-Automation - Jira.jpg

When a branch is opened, the repository name should be added to the components field and the labels field (with the labels field acting more as a check to see if its working since it doesnt rely on pre-filled choices like the components field.)

We then added all of our repository names to the list of components and tried running the automation. Unfortunately, we are having some weird mixed success where repository names are working and some are not. 

For Example, api-usage, one of our repository names works correctly and writes to the component field when the branch is created:
2022-01-13 15_58_47-[AT-3765] Test Jira Automation with Craig - Jira.jpg

However, p44, another repository does not work, despite being included in the components list and the label field updating correctly:2022-01-13 16_03_01-[AT-3765] Test Jira Automation with Craig - Jira.png2022-01-13 16_01_55-[AT-3765] Test Jira Automation with Craig - Jira.png

Would anyone be able to help figure out what we may be doing wrong?

 

1 answer

0 votes

Hi Craig,

Are you able to share what you're seeing in the Audit Log when the rule is running?

You can read more about using the Audit Log to troubleshoot here: 
https://support.atlassian.com/cloud-automation/docs/what-is-the-automation-audit-log/

Cheers,

Charlie

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

👋 Looking for 15-20 volunteers to test Atlassian training content

Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...

395 views 19 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you