Automating state transition on PR merge based on target branch in a next-gen project

[Emlyn]

Hi,

I've started automating our project issue transitions and have them happily transitioning for when a PR is created. We use bitbucket cloud and have integrated it with Jira.

We have multiple states once a PR has merged, based on the branch name. I don't see a way to do this in the automation rules yet.

I would have hoped that (following https://support.atlassian.com/jira-software-cloud/docs/smart-values-development/) I'd be able to use something like {{pullRequest.targetBranch}} but that doesn't appear to exist.

Am I missing something or is there some other way to get the target branch (or originating branch) of a PR? 

Thanks in advance!

[tomas]

Hey Emlyn, currently we have no support for target branch yet via smartvalues.

[Emlyn]

Thanks tomas.

Is there any time line on when there might be expanded PR tags available in Jira?