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:
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:
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:
However, p44, another repository does not work, despite being included in the components list and the label field updating correctly:
Would anyone be able to help figure out what we may be doing wrong?
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:
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...
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