Github can do various checks on a branch prior to merging. It would be very good to get the status of any associated JIRA tickets in that list.
Thank you for the additional insight. We do have some features conceptualized around pushing some status to GitHub.
FWIW - in our Jira Cloud product - if the Pull Request is created using the Git Integration for Jira app - the PR will be created with a link to the Jira issue in the PR description. Doesn't provide the automation you are looking for but does link back to Jira.
I believe this is a crucial feature that would be beneficial to many teams.
Github is the place where developers go.
JIRA is the place where the business, issue creators and issue testers go.
In a clean process, an untested card should never be merged.
With the current JIRA - Github integration, developers can easily indicate that an issue is ready for retest, and also push a comment explaining how to do so (in the context of the CI for instance).
But the info that the test is done will currently live in JIRA : issue status change, or comment by the non technical creator/tester.
A check on the PR preventing the merge before the card has the right JIRA status would streamline the process for the dev or the Github Project manager and allow to cleanly define a good CI architecture.
I am currently working on providing this as an Atlassian addon, after having a private version working for the last two years. Would you be interested in testing this feature as it is being developed? It's still in early beta, but it works well for our use case already.
Please contact me if you're interested in helping me test this feature, or just want more information :)
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events