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

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      At this moment JIRA does have an APi that allows to trigger a check of all plugins updates that are available and trigger their download and upgrade.
      Providing an API for performing this would be of a great importance as it would allow to automate the upgrade of JIRA instances, and even scheduling these updates at times of low load.
      At this moment this operation can be done only manually so it cannot be automated.
      Also by having an automated upgrade option, this would allow to keep the staging / testing instances with bleeding age versions, allowing to test the effect of the new software versions over instances, preventing problems and downtimes on production instances.

            [CONFSERVER-35178] Provide API for automating upgrade of Confluence plugins

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3569591 ] New: JAC Suggestion Workflow 3 [ 4338512 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3174970 ] New: JAC Suggestion Workflow 4 [ 3569591 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3031919 ] New: JAC Suggestion Workflow 2 [ 3174970 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2532008 ] New: JAC Suggestion Workflow [ 3031919 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2282828 ] New: Confluence Workflow - Public Facing v4 [ 2532008 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2176823 ] New: Confluence Workflow - Public Facing v3 [ 2282828 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1941596 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2176823 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1754748 ] New: Confluence Workflow - Public Facing v3 [ 1941596 ]
            jonah (Inactive) made changes -
            Description Original: At this moment JIRA does have an APi that allows to trigger a check of all plugins updates that are available and trigger their download and upgrade.
            Providing an API for performing this would be of a great importance as it would allow to automate the upgrade of JIRA instances, and even scheduling these updates at times of low load.
            At this moment this operation can be done only manually so it cannot be automated.
            Also by having an automated upgrade option, this would allow to keep the staging / testing instances with bleeding age versions, allowing to test the effect of the new software versions over instances, preventing problems and downtimes on production instances.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-35178].
              {panel}

            At this moment JIRA does have an APi that allows to trigger a check of all plugins updates that are available and trigger their download and upgrade.
            Providing an API for performing this would be of a great importance as it would allow to automate the upgrade of JIRA instances, and even scheduling these updates at times of low load.
            At this moment this operation can be done only manually so it cannot be automated.
            Also by having an automated upgrade option, this would allow to keep the staging / testing instances with bleeding age versions, allowing to test the effect of the new software versions over instances, preventing problems and downtimes on production instances.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-35178 [ CONFCLOUD-35178 ]

              Unassigned Unassigned
              73f0b2e75f82 Sorin Sbarnea (Citrix)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: