Identifying multiple issues by commit message

[Deleted user]

I would like to respond to commits based on finding the issue key in this format: (BOARD-1) - where there may be multiple commits being merged or tagged in a release. The objective is to automatically create JIRA releases from Github releases as well as move JIRA cards around based on Pull Request status.

We are moving to this from a branch based approach to identifying the JIRA issue key because we use a rebase workflow and the branch names are not available in releases, but also to allow us to transition multiple cards on a single commit. 

If a rule matches multiple keys, will it run for each key on a single webhook request? If so, what would a rule look like to query the message of every commit in a webhook for the issue key formatted as above?

[Simmo]

Hi David,

First of all, check out our blog post on this topic if you haven't already as it should be pretty helpful.

From having a quick glance at the GitHub webhook events, I imagine that you'll need to subscribe to Push webhooks to do this, which gives you a list of commits from which you'll need to find the attribute containing the issue key and parse it out (probably using some of our string smart values). Have a look at our docs on working with lists so that you can use that to end up with a smart value that produces a list of issue keys - format these in a way that will work with a JQL in clause.

With that in mind, you can then use that smart value in a Related Issues branch of the type JQL which will let you act on all those issues.

Cheers,

Simeon.

[Deleted user]

Yeah, I've looked at those links. This smelled like the sort of thing you would have a JQL snippet prepared for as a pretty obvious use case, so I was hoping not to churn on it. I'll keep jabbing at it. The working with lists link seems particularly unhelpful as it pertains to something other than querying.