Automatic workflow transition on Bitbucket merge

[David Cook]

Hi,

I want to know if it is possible to cause an automatic workflow transition in JIRA when creating or merging branches?

e.g.

We have 3 branches:

• Production
• Release
• Development

Branching an JIRA issue from the development branch should transition the JIRA workflow status from OPEN to IN PROGRESS. Merging a JIRA issue branch into the Development branch should transition the JIRA workflow status from IN PROGRESS to RESOLVED.

Finally, merging a validated release candidate from the release branch into the production branch should transition the JIRA workflow status from RESOLVED to CLOSED.

We do not use code reviews or pull requests.  We're using the tools for embedded software development. The team is small and each engineer runs his own project.  There are no contribution to the code base from other engineers nor is there any collaboration between projects. Solo projects.

Thanks

[Matthias Gaiser _K15t_]

Hi @David Cook,

we're using Bitbucket Pull Requests, therefore I haven't tried out these approaches, but I can think of the following.

• Try Jira Automation
  Atlassian has some template rules for your inspiration, e.g. when a commit is created then transition the Jira issue. Not sure if you get all the flexibility you wanted, but you could give it a try.
• Try Bitbucket Pipelines
  With a Bitbucket Pipeline, you can define some script you run on each branch (and can also control on which branches you run it). In that script, you could call Jira's REST API to transition an issue.

I think, I'd try to go with Automation first. If that's not enough flexibility you could use a Pipelines script.

Hope that helps,
Matthias.