nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to assign issue to Github Pull Request Reviewer (or assignee)

Jesse Maxwell

Similar issues have been asked in the past but I'm not seeing anything that references the tooling around Development that Atlassian has recently released.

Goal: auto-assign a Jira ticket to the developer who is reviewing the Pull Request in Github.

Background:

The "Development" panel on the sidebar of each ticket has insight into who authored the PR and who reviewed it. However, I'm not seeing a way to access that info via automations.

Is there a way to (easily) auto-assign a ticket to the person who is reviewing the Pull Request?

Accepted answers

All comments

Stefan Salzl

Hi @Jesse Maxwell ,

as the documentation points it out it seems to me that this is not possible out of the box.

One guess:
Haven‘t tried that before so can‘t confirm or provide a solution yet:

Guess that could be done with a webrequest within an automation rule.

see following link to github api:

https://docs.github.com/en/rest/pulls/review-requests

Keep in mind that you will the have to match the issue github user against your jira users to find out the jira user‘s accountID which is needed to set the assignee field.

Hope this was helpful.

Best
Stefan

Dhiren Notani_Exalate_

Hi @Jesse Maxwell

This is Dhiren from Exalate.

Exalate, provides a fully bi-directional synchronization between Jira and GitHub (among other ITSM systems) that is fully customizable. You can synchronize GitHub issues as tickets/issues in Jira and vice-a-versa. It is easy to set up and Exalate uses a scripting engine which is based on Groovy scripts where you can control what data you want to share and even you can independently handle the incoming information. You can achieve complex use-cases with ease.

It's possible to assign the issue to a developer who is working on it (from the development team) via scripting in Exalate.

If you would like to see a customized demo of the product in action, feel free to book a slot with us.

Thanks
Dhiren

Diana_Architect_ZigiWave

@Jesse Maxwell hi there. That's a very interesting use case. You can achieve this, especially if by "developer that reviews the pull request" you mean "assignee". A tool like ZigiOps can help you. It had advanced field mapping capabilities that allow you to customize it to fit your current use case - auto-assign a ticket to someone who is reviewing pull requests. Feel free to explore it and book a demo to see how it can exactly handle your case.

Regards, Diana (ZigiWave)

Stefan Salzl

Hi @Dhiren Notani_Exalate_

first of all: I really love exalate.

But refering to the original post from @Jesse Maxwell :

Is exalate really capable of covering the specified requirement? I know exalate syncs issues/information between different source systems (like github issues to jira issues and vice versa). Can exalate identify a github pull request as an issue itself?