Can we Set JIRA Issue Field Value Equal to Bitbucket Repository Name

Question

We run a single project for all new feature work, defects, and improvements for our product. There are somewhere in the vicinity of 30 repositories that make up our product, which is likely to grow over the coming months.

We are looking for a way to automatically add a label, component, or otherwise set some other field value to match the repository (or repositories) name when a pull request has been merged.

I've had a look at the OOTB Jira Automation possibilities and not really seeing much there that would be able to get the repo name from our connected Bitbucket then set that value on an issue. It seems I can detect when a PR was merged, which is fantastic (I'll use this for other things) and gets me part of the way there.

Any help would be great.

TLDR; Trying to get repository name from bitbucket after pull request merged, to the set this as a value in a Jira issue.

Darren Marshall · Answer

Thanks Wes! Some good tips in there I'll put to use today and see if I can work out my situation

wwalser · Answer

@Darren Marshall You should be able to test an automation rule using a few different techniques.

It's a bit to type out, so I've just shot a quick video for you: https://www.loom.com/share/2987c5e4879f481996b074126b49d19e

Darren Marshall · Answer

I have tried the following rules in Automation, but have not had any luck in getting the label field to be set:

1.
WHEN: Pull request merged
THEN: Edit issue fields LABEL {{branch.repository}} (also tried {{pullRequest.sourceBranch.url}})

2.

WHEN: Issue transitioned from In Progress to Deployed to Dev
THEN: Edit issue fields LABEL {{branch.repository}} (also tried {{pullRequest.sourceBranch.url}})

I have set up email alerts to tell me if the rule fails, but I have received no alert and no Label fiel set. Without some sort of feedback on why this works, it just seems like this feature simply doesn't work. @Jira Guru is there somewhere I can poke around to find out why this rule seems to not have run? Or am I using smart values incorrectly, perhaps against a field that doesn't support it?