• 1
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We use Git (+Gerrit +Jenkins) and would love to adopt this plug-in, but we don't want to use GitHub nor do we plan to migrate to GitHub enterprise.

            [JSWSERVER-14416] Support git in addition to GitHub/GitHub Enterprise

            Adam Wride added a comment - - edited

            For posterity - just want to point out that the Git Integration for JIRA add-on does support Smart Commits + GitLab Integration (see video).

            Adam Wride added a comment - - edited For posterity - just want to point out that the Git Integration for JIRA add-on does support Smart Commits  + GitLab Integration ( see video ).

            +1 As a company, we would love to be able to use git integration (and smart commits) from our repository server instead of Github/Bitbucket. All the reasons for this have been covered by previous comments.

            Stoyan Ivanov added a comment - +1 As a company, we would love to be able to use git integration (and smart commits) from our repository server instead of Github/Bitbucket. All the reasons for this have been covered by previous comments.

            +1 for TFS-Git integration to JIRA Cloud. Existing solutions all either require Bitbucket/Github or JIRA Server.

            Kimberly Tran added a comment - +1 for TFS-Git integration to JIRA Cloud. Existing solutions all either require Bitbucket/Github or JIRA Server.

            carlos added a comment -

            carlos added a comment - Maybe it's too late, but https://marketplace.atlassian.com/plugins/com.allenta.jira.plugins.gitlab.gitlab-listener could be useful for your case

            I opened a campaign for adding support for GitLab here https://42picky.tilt.com/jira-dvcs-connector-for-gitlab

            Sorin Sbarnea added a comment - I opened a campaign for adding support for GitLab here https://42picky.tilt.com/jira-dvcs-connector-for-gitlab

            intersol_old added a comment -

            How about GitLab support? Or to to make it easy, just allow people to connect to filesystem GIT repos and remote (HTTP) ones and you solve all use cases for other systems.

            By adding later REST API, you can improve the experience of adding or removing the repositories, but fist make it work with any GIT or Mercurial repo, otherwise you should rename the plugin to "Bitbucket and GitHub Integration".

            intersol_old added a comment - How about GitLab support? Or to to make it easy, just allow people to connect to filesystem GIT repos and remote (HTTP) ones and you solve all use cases for other systems. By adding later REST API, you can improve the experience of adding or removing the repositories, but fist make it work with any GIT or Mercurial repo, otherwise you should rename the plugin to "Bitbucket and GitHub Integration".

            mcook Isn't Bamboo required in order to use that plugin properly? And if so, that is very cost prohibitive when taking into account the cost of licensing Bamboo plus the plugin plus moving away from current tools in order to use the open source and free git software.

            We use Gerrit and have found success with the free JIRA/Gerrit plugin at https://marketplace.atlassian.com/plugins/com.meetme.plugins.jira.gerrit-plugin however, we were really hoping to leverage the additional features which the DVCS connector has. Unfortunately it sounds like Atlassian simply will not back a free product without customers having to purchase even more heavily into Atlasssian products. It's this business model which makes it very difficult to continue to evangelize their products.

            Cheyenne Bryant added a comment - mcook Isn't Bamboo required in order to use that plugin properly? And if so, that is very cost prohibitive when taking into account the cost of licensing Bamboo plus the plugin plus moving away from current tools in order to use the open source and free git software. We use Gerrit and have found success with the free JIRA/Gerrit plugin at https://marketplace.atlassian.com/plugins/com.meetme.plugins.jira.gerrit-plugin however, we were really hoping to leverage the additional features which the DVCS connector has. Unfortunately it sounds like Atlassian simply will not back a free product without customers having to purchase even more heavily into Atlasssian products. It's this business model which makes it very difficult to continue to evangelize their products.

            Hi Megan,

            We are using the GIT plugin already but that does not allow for Smart Commits into JIRA from Gitlab. Moving to Bitbucket or Stash is not an option for us. Looks like we may need to develop our own plugin for smart commits into JIRA if time allows.

            Regards,
            Adam

            Adam Wignall added a comment - Hi Megan, We are using the GIT plugin already but that does not allow for Smart Commits into JIRA from Gitlab. Moving to Bitbucket or Stash is not an option for us. Looks like we may need to develop our own plugin for smart commits into JIRA if time allows. Regards, Adam

            M (Inactive) added a comment - - edited

            Thanks for raising this issue with us. We currently do not have any plans to add this support to the DVCS connector, however it sounds like the Git Integration Plugin will do what you're after. Please let me know if there is additional functionality you were hoping for that this plugin doesn't cover.

            You could also try Bitbucket or Stash of course

            Cheers,

            Megan Cook
            Atlassian Product Manager

            M (Inactive) added a comment - - edited Thanks for raising this issue with us. We currently do not have any plans to add this support to the DVCS connector, however it sounds like the Git Integration Plugin will do what you're after. Please let me know if there is additional functionality you were hoping for that this plugin doesn't cover. You could also try Bitbucket or Stash of course Cheers, Megan Cook Atlassian Product Manager

            It seems nobody is working on this issue since May 2013, we are using JIRA commercially and we don't want to push our codes to third party repositories

            Ozer Erturk added a comment - It seems nobody is working on this issue since May 2013, we are using JIRA commercially and we don't want to push our codes to third party repositories

            +1 for this with Gitlab hosted by us to integrate smart commits with our hosted JIRA.

            Adam Wignall added a comment - +1 for this with Gitlab hosted by us to integrate smart commits with our hosted JIRA.

            We'd love to be able to link JIRA to our VisualStudio.com Git account.

            Peter Drill added a comment - We'd love to be able to link JIRA to our VisualStudio.com Git account.

            My company is an MSDN partner and we get Team Foundation (Git instance) inlcuded in our membership, and my company would be prepared to pay for a JIRA instance, but I wouldn't get the sign off for the Enterprise Git Stash product as well as we already have a Git supplier included in our MSDN subscription.

            If this can connect to any Git instance I'm sure it will increase the amount of sales for Jira!

            James Abbott added a comment - My company is an MSDN partner and we get Team Foundation (Git instance) inlcuded in our membership, and my company would be prepared to pay for a JIRA instance, but I wouldn't get the sign off for the Enterprise Git Stash product as well as we already have a Git supplier included in our MSDN subscription. If this can connect to any Git instance I'm sure it will increase the amount of sales for Jira!

            We are also evaluating to purchase a new JIra + JIra Agile license.. but we need a free tool to connect our git local repository. This would be a problem.

            Aitor Morant Inchausti added a comment - We are also evaluating to purchase a new JIra + JIra Agile license.. but we need a free tool to connect our git local repository. This would be a problem.

            +1

            Riku Raisanen added a comment - +1

            jbtorres added a comment -

            is there any way that it can be integrated gitlab, gitlab.com with issues?, when submit a issue this show on gitlab issues tracking, something like github issues tracker and reverse from gitlab issues to jira...

            jbtorres added a comment - is there any way that it can be integrated gitlab, gitlab.com with issues?, when submit a issue this show on gitlab issues tracking, something like github issues tracker and reverse from gitlab issues to jira...

            +1

            benjamin_d added a comment -

            +1

            benjamin_d added a comment - +1

            Henk Kraal added a comment -

            +1

            I'm currently evaluating Jira Agile and GitlabHQ (locally) to replace our current Trac+SVN setup, as far as I can see now the lack of this plugin to intergrate with a local gitlab instance could be very well a dealbreaker for us starting to work with Jira Agile.

            Henk Kraal added a comment - +1 I'm currently evaluating Jira Agile and GitlabHQ (locally) to replace our current Trac+SVN setup, as far as I can see now the lack of this plugin to intergrate with a local gitlab instance could be very well a dealbreaker for us starting to work with Jira Agile.

            John Dyer added a comment -

            +1

            John Dyer added a comment - +1

            I logged this ticket 4 months ago, can someone from Atlassian please provide some kind of response?

            Cheyenne Bryant added a comment - I logged this ticket 4 months ago, can someone from Atlassian please provide some kind of response?

            We would also really appreciate having this feature natively.

            Viacheslav Kravchuk added a comment - We would also really appreciate having this feature natively.

            So, as far as I can tell, someone can fork the add-on, add this functionality, and send a pull request to Atlassian for approval and inclusion in an upcoming release (or provide their own build). Any volunteers?

            Nicholas Muldoon added a comment - So, as far as I can tell, someone can fork the add-on , add this functionality, and send a pull request to Atlassian for approval and inclusion in an upcoming release (or provide their own build). Any volunteers?

            Mario Cupelli added a comment - - edited

            I am using Jira and git and I think all Git users would love to see the integration independently from Github or Bitbucket. I hope that this feature will be implemented soon.

            Mario Cupelli added a comment - - edited I am using Jira and git and I think all Git users would love to see the integration independently from Github or Bitbucket. I hope that this feature will be implemented soon.

            stijn added a comment -

            Well I just setup this the workaround myself because we really want to have the ability to use smart commits, and we don't care that Jira links to BitBucket issues (after all, BitBucket is quite nice). Works flawlessly. But I understand the wish/need for native support nonetheless.

            stijn added a comment - Well I just setup this the workaround myself because we really want to have the ability to use smart commits, and we don't care that Jira links to BitBucket issues (after all, BitBucket is quite nice). Works flawlessly. But I understand the wish/need for native support nonetheless.

            While that may be a "solution", it seems quite hacky to me.

            So i'd add a post-commit hook in my gitlab instance to push that repo to it's BitBucket clone, only to have BitBucket then communicate back to my server's JIRA instance to let it know about the commits? What about linking - I wouldn't want commit links inside of JIRA issues to link to BitBucket.

            While I appreciate the workaround, i'd rather have native support.

            Steve Kanter added a comment - While that may be a "solution", it seems quite hacky to me. So i'd add a post-commit hook in my gitlab instance to push that repo to it's BitBucket clone, only to have BitBucket then communicate back to my server's JIRA instance to let it know about the commits? What about linking - I wouldn't want commit links inside of JIRA issues to link to BitBucket. While I appreciate the workaround, i'd rather have native support.

            stijn added a comment -

            A possible workaround (not tested, but should work if I'm correct): get a BitBucket account with single user just for the company, create private repositories with the same names you already haves, add the BitBucket repositories as extra remote to the current repositories and either always push to all remotes, or add a post-commit hook on the server to do that push automatically for you.

            stijn added a comment - A possible workaround (not tested, but should work if I'm correct): get a BitBucket account with single user just for the company, create private repositories with the same names you already haves, add the BitBucket repositories as extra remote to the current repositories and either always push to all remotes, or add a post-commit hook on the server to do that push automatically for you.

            My company uses a local gitlab instance to manage our git repositories. It's running on the same host as our JIRA installation. I'd love to be able to use JIRA DVCS to view my commits from those local repositories inside of JIRA.

            Steve Kanter added a comment - My company uses a local gitlab instance to manage our git repositories. It's running on the same host as our JIRA installation. I'd love to be able to use JIRA DVCS to view my commits from those local repositories inside of JIRA.

              Unassigned Unassigned
              d51a434cbf0c Cheyenne Bryant
              Votes:
              69 Vote for this issue
              Watchers:
              49 Start watching this issue

                Created:
                Updated: