Why doesnt Git Integration for Jira (by GitKraken) look as good as GitHub for Jira (by Atlassian)??

[Jon.Austen]

Why doesnt Git Integration for Jira (by GitKraken) look as good as GitHub for Jira (by Atlassian)??

I come from a company that used the latter, and it was awesome.  The second you open a JIRA ticket, without any additional clicks, you can see the branches and pull-requests.

BUT

Now I am at a company that uses Azure ADO and we are forced to use the GitKraken plugin for integration, and the integration works but it looks terrible and requires scrolling down and a click to get to the info.

Am I the only person that sees that this is a problem?    Is it possible that the GitKraken ADO plugin can be configured to look more like the Atlassian integration to GitHub, without needing the additional scroll-click?

[Dan Tombs]

Hi @Jon.Austen

while there are a few things you can do regarding the data shown, marketplace apps are limited in how data can be shown. This is very common in regards to almost every marketplace app.

[Jon.Austen]

In this case, it is such a massive difference, that I would call the GitKraken plugin pretty much unusable.

[Adam Wride]

Hi @joh - I'm the Product Manager for Git Integration for Jira at GitKraken. Our app does push commit/branch/and pull request data into Jira Cloud so it can be displayed in the Developer Information panel in the Jira issue. This is the same access that the GitHub app by Atlassian uses to display this data.

Are you seeing something different on your side? Feel free to email me directly: adam . wride @ gitkraken.com

 

[Jon.Austen]

Yes, I see something very different.   Instead of showing those links where your screenshot shows, it instead shows them in a popup sidepanel after clicking the "Git Integration" blade, which you have to scroll down to find.    I suspect that the screenshot you sent above is not the GitKraken plugin, but it is instead a screenshot of the Github/Atlassian Jira integration plugin.    You might be getting the 2 confused with each other.

[Adam Wride]

Hi @Jon.Austen - 

Our app definitely publishes to Jira Cloud such that it can show in the developer panel, just like the GitHub app.

The "Git Integration" glance (what Atlassian calls that part of the issue) is in addition to the developer panel (not instead of).

If you aren't seeing anything in the developer panel - it's possible that one setting in Git Integration for Jira is not enabled. Have your Jira admin go to the General Settings page and check for the "Send Development Information to Jira Cloud" checkbox. Is yours checked or unchecked? (it should be checked)

If it is already checked, then we'd love to engage with you (support@gitkraken.com) because you should be seeing your Azure data in the issue development panel - just like you saw with the GitHub app.

Cheers,

Adam

[Jon.Austen]

Thanks Adam.  I'll ask our JIRA admin and get back to you asap in this thread.  Would this solution also work if we have a self-hosted instance rather than JIRA cloud?   If not, are we stuck with the alternate config due to having self-hosted instance?   I don't know if we are self-hosted or not but I will ask.

[Adam Wride]

@Jon.Austen - Git Integration for Jira works with self-hosted / cloud hosted git servers the same way. No differences so you should be good to go if you are self-hosted.

[Jon.Austen]

@Adam Wride  Turns out that we have the checkbox for "Send Dev Info to Jira Cloud" disabled.   We are definitely have a Jira Cloud instance also.   Can you tell me :  what are the risks of checking that box, if we have 800+ repos being indexed by this plugin?  Could it have any side-effects that might hurt existing users in our JIRA?   Our JIRA admin needs some reassurement about checking that box.

[Adam Wride]

@Jon.Austen - good to hear. This is very likely the reason that you are not seeing any information in the Development Panel.

In terms of risks, if you do not have any other plugin publishing to the Development Panel (it sounds like you don't) then the main "risk" would be in automated workflows that might trigger based on commits added/PRs merged/etc.

However - if your team hasn't been using any plugin with this functionality then it's unlikely that you have any workflows using these triggers. If your admin would like to check - they can look at the Automation for Jira administration screen.

If your admin would like to test out this functionality - they can test on a sandbox or on a free Jira Cloud instance to verify the behavior (I don't think this is necessary but I would understand why a seasoned Jira admin would want to do this).

Since the repositories are already getting indexed, you won't see any differences in behavior in terms of performance by turning on the "Send Dev Info" setting. Note - you will only see new activity after enabling this setting (for more information - see this help article). If it is important to see all historical information - your admin will need to remove the repositories and re-connect.

If you have any questions - you can reach out to us at support@gitkraken.com and we'll hop on a call with your admin.

Cheers,

Adam

[Jon.Austen]

Thanks @Adam Wride  ,  the change worked!    Now our huge organization has this feature.   Thank you.

Probably would be worth making sure your clients know how to configure this.   It's possible many of your clients might want this but don't know how to configure it.

[Adam Wride]

@Jon.Austen  - I'm glad you and your team were able to get the full benefit of seeing Git in Jira.

We'll take a look at who has that setting disabled and remind them of the benefits of enabling. We will also look at updating the setting label to make it more clear what that setting does.

Cheers,

Adam

[Dave Labra Gaona]

Hi John,

I'm David and work for GitKraken. We make the Git Integration for Jira. As Dan has shared with you, Marketplace apps do have special requirements/limitations to show data. That is why there are some additional clicks or scrolling needed. In any case, I will share this request with our team to see what can be improved to offer a better look and feel.

Thank you for creating this community question.

Cheers,

David

[Jon.Austen]

Glad that one of you saw this.   Thanks.