Integration with GitHub for Delievery
Asked by Georg Traar:

Are there any plans to integrate with GitHub Issues / PR for product delivery?


Answers:
author: Syed Majid Hassan -Exalate-
body: Hi [@Georg Traar](/t5/user/viewprofilepage/user-id/5247000) ,

Welcome to the community!

This is Majid @ Exalate.

I would urge you to look at an integration app such as [Exalate](https://marketplace.atlassian.com/search?query=issue%20sync) to do this integration out of the box. The issues and PRs can be synced bi-directionally and the set up is pretty straight forward as well.

Hope it helps.

Thanks

Majid

comments: author: Tanguy Crusson
body: Hi [@Syed Majid Hassan -Exalate-](/t5/user/viewprofilepage/user-id/4626130) thanks, have you validated this works for Jira Product Discovery?


author: Syed Majid Hassan -Exalate-
body: Yes we have already been able to sync succesfully for Product Discovery, but formal certification is under way.

Thanks


author: Tanguy Crusson
body: That's awesome! Would you be able to share a demo here for whoever faces this issue and comes across this post?


author: Syed Majid Hassan -Exalate-
body: Here it is [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) :

[Integrating Jira Product Discovery issues with GitHub issues using Exalate](https://www.youtube.com/watch?v=LlUVRa8Q73w)

Hope it helps!

Thanks

Majid


author: Tanguy Crusson
body: OK I see, thanks, a way to sync issues. You could use that to look for ideas that reach a particular status and then create a corresponding ticket in Github. Then create sub-issues from Github to mimic the integration between Jira Product Discovery and Jira Software. What would be useful is to show a link to the Github issue from the Jira Product Discovery idea.


author: Syed Majid Hassan -Exalate-
body: Indeed, so you can have that populated automatically via Exalate scripts into a custom Field on the Idea.


author: Tanguy Crusson
body: Hi [@Georg Traar](/t5/user/viewprofilepage/user-id/5247000) , Tanguy here from the Jira Product Discovery team. It's not planned yet. Are you using both Github and Jira as issue trackers or just Github?

comments: author: Georg Traar
body: Hi [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)

We are using GitHub heavily in the engineering teams and as main issue tracker.

Otherwise many parts of the Atlassian stack including ITSM, but not Jira directly on its own as issue tracker.

---

Looking at Jira Discovery, if there would be an option to link GitHub issues and/or PRs in the delivery section, this would be kinda nice to keep track. However I guess one could also add it to the description. Custom fields don't seem to be available.


author: Tanguy Crusson
body: Thanks [@Georg Traar](/t5/user/viewprofilepage/user-id/5247000) , that makes sense.

Have you tried creating a field of type "Hyperlink" and pasting a link to Github issues/PR there in a list view? That's another option that could work


author: David.brimley
body: Hi Tanguy, just pinging this again. Has this made it onto the Roadmap for 2024?


author: David.brimley
body: Hi [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)

I wanted to ping this up again onto your radar.

Most folks have been suggesting the use of a sync tool like Exalate. The problem with this approach is.

(A) It requires JIRA, so this doesn't work if your engineers only work in GH.

(B) It requires the sync tool, and our experiences with those are highly variable.

It would be a big bonus for us if JIRA PD could interact directly with a GH Repo for delivery. Of course, the problem then becomes how you standardize delivery labeling, and how you show progress. I'd consider a degraded experience here.

Interested to find out if this is on the roadmap or is under discovery in any way?


author: Diana_Architect_ZigiWave
body: [@Georg Traar](/t5/user/viewprofilepage/user-id/5247000) hello and welcome. I assume it's something we could expect soon. In case you're open to exploring alternative solutions (3rd party ones), you can check [ZigiOps](https://zigiwave.com/zigiops/?utm_source=atls-zigiOps&utm_medium=atls-zigiOps&utm_campaign=atls-zigiOps&utm_id=atls-zigiOps). It's a fully no-code solution that connects the two and syncs their data. It's easy and fast, plus ZigiOps does not store any of the data transferred between the connected system - making it pretty safe for issues and PRs syncing. You can take a look at it, even try it yourself with our [free trial](https://zigiwave.com/trail-template-request/?utm_source=atls-jpdgit&utm_medium=atls-jpdgit&utm_campaign=atls-jpdgit&utm_id=atls-jpdgit) or you can book a meeting with the team to go into details with your use case.

Regards, Diana (ZigiOps team).