As of today, nobody on our team can see the Commit tab. Yesterday everything worked fine - we are using Bitbucket / Git. I verified I have the appropriate permissions. (Again, we made no changes from yesterday to today.) The permissions helper says I have access. The project > admin > development tools says...
The View Development Tools permission allows users to view development-related information on the view issue screen, like commits, reviews and build information.
The following users currently have this permission:
Project Role (Developers)
We're are all in this group.
Am using JIRA 6.1 and installed GIT-JIRA integration plugin. But am not able to see GIT commit tab for sny issue id I use in GIT commit description
Dhanesh, there is no longer a tab in version 6.2. Maybe, double check your version. It now shows up on the right had side below Dates and Time Tracking under the heading Development. It is now a link e.g. it may say 2 commits. Clicking the link will pop a window w/ the commit details. Hope that helps. Also see my comment above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With version 6.2 of Jira OnDemand, the Development tools integration has changed a little bit as noted in the release notes, https://confluence.atlassian.com/display/JIRA/JIRA+6.2+Release+Notes. Basically, they moved the content from a tab, to the right side of the page under the heading Development. The section only appears if there were commits made for the ticket in question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the response Luther. This is Jira OnDemand.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may have to re setup the application link between fisheye and JIRA. Especially if the server changed between upgrades. Alternatively you could restart Fisheye and JIRA as they may have some old config values cached that could be messing with this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.