Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-9089

Release status is not synced via rest status call in JIRA Bamboo plugin

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 3.2 RC1, 3.2
    • None
    • None
    • None

      Whats happening:

      • The OAuth token has expired during a release
      • Once the user has done the 3LO dance they are returned to the tab panel
      • Tab Panel queries Bamboo, detects that the build has finished (success or failure), releases the jira version
      • The frontend code does not update the fact that the version has been released even though the status (released or not) has been sent back via the JSON response

            [BAM-9089] Release status is not synced via rest status call in JIRA Bamboo plugin

            bmccoy added a comment -

            Changed tactic. Instead we will send a force refresh flag back in the json response if the entire page needs an update for some reason.

            jira.forceRefresh=true

            bmccoy added a comment - Changed tactic. Instead we will send a force refresh flag back in the json response if the entire page needs an update for some reason. jira.forceRefresh=true

            MarkC added a comment -
            • The backend action should poll Bamboo based on a parametere that will only be set when redirecting back from OAuth

            MarkC added a comment - The backend action should poll Bamboo based on a parametere that will only be set when redirecting back from OAuth

            After talking, have decided instead that once user has done 3LO dance they are redirected to an action which polls Bamboo for the latest status then they're shown the tab panel.

            Jason B (Inactive) added a comment - After talking, have decided instead that once user has done 3LO dance they are redirected to an action which polls Bamboo for the latest status then they're shown the tab panel.

              bmccoy bmccoy
              jdumay James Dumay
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: