JIRA 6: What's the differences between "Commits" and "Source" tabs

[Shijun Kong]

Recently upgraded to JIRA 6, now for each issue, there is a new "Commits" tab ahead of the "Source" tab.

for the "Source" tab, it still works as it is, connects to fisheye 3.x instance properly with commit information associated by commit message.

for the "Commits" tab, however, it shows three connection options (bitbucket, github and fisheye).

my questions:

1. what's the differences between "Commits" and "Source"
2. why "Commits" does not pick up the application link used by "Source"?

[Gurleen Anand _Atlassian_ · Accepted solution]

Hi Shijun,

Yes, you can disable the JIRA DVCS Connector plugin: https://confluence.atlassian.com/display/BITBUCKET/Use+the+JIRA+DVCS+Connector+Plugin in JIRA to remove the "commits" tab.

Thanks,

Gurleen

[DanielP]

But you're not answering the question! Why was the commit tab introduced if nothing seems to showing up under it?

[Felipevsw]

The commits tab is for the Bitbucket integration (with Git or Mercurial), while the Source tab is for the integration with SVN.

[Shijun Kong]

hi @Felipe, the answer sounds straight forward. However, why other options (stash and fisheye) display there, really confusing.

is there a way to get rid of it? switch off the corresponding plugin?

what display on "Commits" tab:

Connect your code to JIRA

Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.

Git & Mercurial in the cloud

Collaborate across unlimited private code repositories.

ConnectFind out more

Git behind the firewall

Manage and collaborate on Git repositories behind a firewall.

ConnectFind out more

Browse and search code

Browse, search, and track source code repositories.

ConnectFind out more

Find more source code tools on the Atlassian Marketplace

[Jay Barra]

We're using Mercurial and my commits are showing up under the source tab and the commits tab still doesn't show anything even though I'm connected to Fisheye.

[EddieW]

The teaser for Fisheye (what we use for SVN) mentions nothing about DVCS, and has been really confiusing to users.

Browse and search code

Browse, search, and track source code repositories.

ConnectFind out more

But we already have app links fully configured. This message is just misleasing, and clicking COnnect does nothing but show our existing links.

Huge failure.

[Danilo Conrad]

Hi there,

FishEye integration is displayed in the Source tab, as explained in the documents below:

• Integrating JIRA with FishEye
• Viewing an Issue's FishEye Changesets

There is a ticket open to remove the FishEye and Stash integration message from the Commits tab:

• https://jira.atlassian.com/browse/JRA-35749

You may vote on the above ticket and add yourselves as watchers to be notified of any relevant updates.

I hope this information helps.

Cheers,

Danilo

[James Green]

Given under the Source tab I am looking at commits provded by Fisheye, having a Commits tab appears to be utterly redundant. Moving this to the issue however.

[spydersoft]

Using JIRA 6.1, I don't see any instructions on disabling the DVCS Connector in the link provided. We are using a Fisheye application link, so the Source tab populates correctly. If the Commits tab is only for BitBucket/GitHub, I should be able to disable it and remove that tab. As mentioned by others, it's confusing to have both when one works and one does not.

[Yannick R.]

To be honest I think it is confusing too. I'm trying to setup Stash with our Jira installation and I just found that Stash's commits are shown in the source tab and not in the commits one.

Also, like @Andreas said, it's a little bit painful to work with the source tab while Jira Agile shows only the Commits one.

[Joakim Eriksson]

Still curious over here, cause our stash commits appear under "source" and not under "Commits" - even though it's indicated by the plugin it's supposed to appear under commiits..?

[Rodrigo Moreno]

same... Is there some instructions to do that?

[Massimo Corà]

same here. Please provide any instructions on how to proceed, thanks.

[Hubert Brzostowski]

To hide this tab(Commits) you need to disable plugin JIRA DVCS Connector Plugin in administrative options (Manage add-ons).

[Erick van Rijk]

Same issue here, Its confusing. We are using JIRA 6.1 and STASH 2.9 and our commits show up under source. However in the Commits TAB it shows STASH next to bitbucket????

[Erick van Rijk]

Same issue here, Its confusing. We are using JIRA 6.1 and STASH 2.9 and our commits show up under source. However in the Commits TAB it shows STASH next to bitbucket????

[julianrupp]

Same thing, I was close to going mad because I simply couldn't think of a reason why it'd still show that screen even though I already had a 2-way trusted application link set up.

Well, disabling the system plugin as described by @Gurleen of course kills off the symptoms, but this still is highly confusing. Why not just kill off the Source tab and add that functionality to the already-existing dedicated DVCS plugin? (The stuff shown in the Source tab is grouped in commits anyway) Having two tabs for essentially the same function, just connecting to different services, looks rather wonky to me.

[Christophe Leite]

Is there a way to hide Commits tab ? I don't need this tab on my issue screen...

Thanks

[Jobin Kuruvilla [Adaptavist]]

See the answer by @Gurleen.

[Deleted user]

same problem here :(

[Andreas Kjær]

Yeah, I'm having the same problem. I need it to work with the commits tab as this is the only tab showing in Greenhopper/Agile details view! Very annoying!

[Laurent Bourgault-Roy]

Wondering the same thing myself. My Stash commit appear in source tabs, but I am a bit confused with the "commits" tabs that don't seem to do anything.

[Shijun Kong]

hi @Felipe, the answer sounds straight forward. However, why other options (stash and fisheye) display there, really confusing.

is there a way to get rid of it? switch off the corresponding plugin?

what display on "Commits" tab:

Connect your code to JIRA

Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.

Git & Mercurial in the cloud

Collaborate across unlimited private code repositories.

ConnectFind out more

Git behind the firewall

Manage and collaborate on Git repositories behind a firewall.

ConnectFind out more

Browse and search code

Browse, search, and track source code repositories.

ConnectFind out more

Find more source code tools on the Atlassian Marketplace