Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14962

Regression: Release Button only works with primary Bamboo server

    XMLWordPrintable

Details

    • 5
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 22 August 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 22 August 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      Summary

      When releasing a version on JIRA it's no longer possible to select plans from different Bamboo Servers if there are more than one connected to JIRA.

      Steps to Reproduce

      1. Have more than one Bamboo linked with JIRA
      2. Go to a JIRA project and try to release a version selecting the option to "Build and release"
      3. Select the "with new build" option

      Expected Results

      You can select plans from all different Bamboo Servers linked to JIRA

      Actual Results

      You can only select from one of them (usually the primary one)

      Workaround

      #1 - Manually release the build directly on Bamboo

      #2 - Set the Bamboo Link for each project individually

      Configure the Bamboo link on a per-Project basis in Jira, this way you get the contents of your defined Bamboo Application link, instead of the globally defined one.

      In Jira,

      • Go to Settings -> Application Links
      • Click on "Bamboo Configuration" (it's right below Application Links and DVCS accounts)
      • You will see the list of linked Bamboo instances, edit the one that is not your default, and write the Jira Project Key to it. If you have more than one project to be included, separate each key with a space character.
      • Click "Update"

      After you have set a custom Bamboo application link for your Project, all release requests will use that Bamboo link. You will not see any projects or plans from other Bamboo servers.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-15971 JIRA fails to retrieve Plan Branches from Non-Primary Bamboo

          • Medium - Medium priority issues
          • Gathering Impact
          relates to

          Suggestion - JRASERVER-71809 When Releasing a Version in JIRA, allow user to choose Plan Branch

          • Closed
          is cloned from

          FUSE-4320 Loading...

          Activity

            People

              Unassigned Unassigned
              fwillig Felipevsw (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: