Is it possible to get a pull request checks in github based on JIRA ticket status

[Sindri Traustason]

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.

[remi.debette]

Hi,

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.

[Adam Wride]

Hi @remi.debette - 

Are you using Jira Cloud or a self-hosted version of Jira (Server/Data Center)?

[remi.debette]

Hi, JIRA cloud for now.

But this could apply also to server, people in my company have the server form.

[Adam Wride]

Sindri - 

This is a neat feature request.

Would you mind contacting me directly (adam@bigbrassband) or via our support channel (support@bigbrassband.com) so we can contact you about this?

Cheers,

Adam 

[Oleg Kondaurov]

Hi Adam,

Any update for this feature request?

With best regards, Oleg.

[Adam Wride]

Hi Oleg - 

We didn't get any response from the original poster here so this isn't yet in our backlog. 

Could you share what you would want to be able to do here?

Are you on Jira Cloud or Server/Data Center? 

Cheers,

Adam

[Oleg Kondaurov]

I believe, on Jira Cloud.

When PR is creating, some Jira bug ID should be specified. Merge should be not allowed until QA verifies the Jira bug, confirm that it is fixed and set its status to closed (or some another pre-configured value). 

[Adam Wride]

@Oleg Kondaurov - 

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.

[Oleg Kondaurov]

@Adam Wride 

Thank you for info. It may slightly help, but as you said can't create automation. 

[Klitos Giannakopoulos]

Any update on this?
It describes exactly what I am looking for

[Ashwini Yerabati]

Any update on the requested feature?

[Rehan Ahmad]

You can achieve the opposite of this using my chrome extension:
https://chrome.google.com/webstore/detail/pr-status/flfdeojdcmafkipiacfmdgnijodanedb

which I think is more useful. The above extension would show your PR review approval status on the Jira cards. 

[eZet]

@Oleg Kondaurov @remi.debette 

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 :)

[Peter swanstrom]

@eZet how is the progress of your addon? I would be interested in hearing more about your project and possibly help beta based on the use case.

[Lars-Kristian Dahl]

I've had the addon in "production" in our organization for 6 months now, seems to be working well for our use case. The onboarding experience isn't really great, but once it's set up it seems to work fine.