@John McKiernan so far it's working great. I added triggers on branch creation, commit, and pull request creation and they all worked as expected. My use case is to move a ticket into in progress when there's obvious work being done on it via git activity and devs forget to update jira from backlog or to do status. One improvement I would make is to allow multiple triggers in the same rule. Right now I created 3 rules and the only difference between the rules is the trigger.
Thank you so much for getting this out. My team will be excited to see this in action.
Atlassian Team members are employees working across the company in a wide variety of roles.
May 13, 2020 edited
Nice! Delighted it is working for you @Will Lu and thanks for sending through how you are using these new triggers. The engineers put a lot of work into bringing it to life so it is always nice to share feedback and show how it helps customers :)
Best of luck and give a shout if you run into any trouble!
Things seem to be working on our side as well. Only two triggers so far, and some errors on transitioning, but the triggers seem to be working thus far.
@John McKiernan We tested it out by automating our happy path work flow for development. So far after testing just a few tickets, the automation has worked like a charm. I am actually pleasantly surprised on how easy it has been to use this, at least for this primary work flow. It's nice! Thanks for keeping us updated and working on this!
The only problem now is that the development panel has never showed up or worked for us. That's a separate issue though.
Automations is exactly what Jira needed. Excellent job here.
I would love to see Bitbucket integration work also the other way, in the actions section. Like when a story transitions, automatically create the related branch.
This looks really awesome and would benefit the different organizations i do consulting work for.
The bitbucket integration is really simple and easy to use, however, i have sometimes run into problems when trying to connect github with jira. I see others have similar issues.
I also notice that you state that you are working on getting this to work with github/gitlab.
Does this mean there will be a new way of integrating jira with github or is the "github for jira" app on market place the solution? Will there be any major changes to that app?
The rules work great and the delivery teams found many useful use cases for the automation. Thanks for this functionality!
I have a small question about a particular case though:
To give a bit of a background, we're dealing with a monolith application and the teams have 2 scenarios for pull requests being raised and transitioned to Code Review:
Only 1 PR in BitBucket is raised against an item and this item should then move to Code Review in JIRA
A team member can raise multiple PR and the transition should only happen when the last PR is raised in BitBucket
Are the automation rules capable of handling our 2nd scenario?
Thanks for the feedback. Can you please share the specific issues that you're facing while connecting with GitHub? Meanwhile, please refer to this GitHub for Jira for more details.
We already support GitHub and GitLab, together with Bitbucket. You need to use the 'GitHub for Jira' or "GitLab for Jira" to get the integration going, and then include a Jira issue key your git activity. Hope this helps.
You might want to follow the guidance here to integrate GitLab with Jira based on the product flavours (self-managed instance or GitLab.com) you're using. You'll need to link your Jira issue with your Git activity by referring to the relevant Jira issue keys.
Please confirm that you're able to see your git activity under the 'Development' section on the Jira issue view. Once that's done, your automation rules should work. Hope this helps. Do let us know how you went with that.
Are there plans to add triggers for things like comments and approvals on a pull request, or being able to assign a Jira issue based on a Pull Request Reviewer or Author?
Hi, there is a comment here that says AWS codecommit is not yet supported and is not in the list. I was wondering if there are any plugins that could help to integrate with AWS codecommit?
84 comments