• 2
    • 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.

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

      We currently use Atlassian's entire suite of products and one of the really nice features in Bamboo are global variables. You can setup name:value pairs to be used in builds, etc.

      In JIRA, we house multiple projects that follow the same release timeline. Currently, we need to manually keep all of the versions in sync across projects. There is already a JIRA ticket in place to address that (JRA-2698).

      This ticket is nearly identical to the "Global Variables" request in Confluence (CONF-3999). In our business, we setup a custom dashboard for each version of our software that keys on various filters (Unresolved, All, Released, Priority, etc.). When we start on a new release, we have to go into each of the dozens of filters and manually change the fixVersion in the query.

      If we had a simple way to declare a global variable (e.g. $currentFixVersion), we would no longer need to update all of the filters each time we had a release.

            Unassigned Unassigned
            f79173ef65b7 Josh Martin
            2 Vote for this issue
            4 Start watching this issue