Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-2471

Support integration with multiple JIRA servers

XMLWordPrintable

    • We collect Bitbucket 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.

        Form Name

          [BSERV-2471] Support integration with multiple JIRA servers

          Greg Gigon added a comment -

          We have a number of Jira instances in our organization and we consider to widespread Stash to a general population of developers. At the moment we are using SVN with a custom hooks, that check for existence of JIRA ticket before the code is checked in. The fact that the integration with Stash only supports a single JIRA instance is a showstopper for us.

          Greg Gigon added a comment - We have a number of Jira instances in our organization and we consider to widespread Stash to a general population of developers. At the moment we are using SVN with a custom hooks, that check for existence of JIRA ticket before the code is checked in. The fact that the integration with Stash only supports a single JIRA instance is a showstopper for us.

          AntonA added a comment -

          pslade, what has this got to do with CI?

          cc jschumacher@atlassian.com.

          AntonA added a comment - pslade , what has this got to do with CI? cc jschumacher@atlassian.com .

          Andrew Frayling added a comment - - edited

          So at the moment, I have to have an n:n number of JIRA servers and Stash servers? If I had 2 production JIRA servers with projects on each that wanted to use Stash I'd have to have 2 Stash servers?

          Stash lets you configure multiple JIRA servers against a single instance of Stash and creates the link to JIRA when you commit using a JIRA ID from the secondary JIRA server in the commit message, but incorrectly creates the link the JIRA server configured as the primary in Stash. Which means you get a 404 when you click it because it's looking for the ticket on the wrong server. Any plans to stop you creating app links, or at least give you some sort of warning until Stash supports multiple JIRA servers?

          Cheers,

          Andrew.

          Andrew Frayling added a comment - - edited So at the moment, I have to have an n:n number of JIRA servers and Stash servers? If I had 2 production JIRA servers with projects on each that wanted to use Stash I'd have to have 2 Stash servers? Stash lets you configure multiple JIRA servers against a single instance of Stash and creates the link to JIRA when you commit using a JIRA ID from the secondary JIRA server in the commit message, but incorrectly creates the link the JIRA server configured as the primary in Stash. Which means you get a 404 when you click it because it's looking for the ticket on the wrong server. Any plans to stop you creating app links, or at least give you some sort of warning until Stash supports multiple JIRA servers? Cheers, Andrew.

            Unassigned Unassigned
            spittet Sten Pittet (Inactive)
            Votes:
            26 Vote for this issue
            Watchers:
            23 Start watching this issue

              Created:
              Updated:
              Resolved: