Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-24232

Global Variables

XMLWordPrintable

    • 3
    • 4

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update – August 2024

      Hi everyone,

      Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.

      Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Carol Low
      clow@atlassian.com
      Product Manager, Jira Cloud

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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
              Votes:
              32 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: