Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-8938

Allow Limiting by Version for Browser Project Open Issues Dashboard

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • Issue - Fields
    • None
    • 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.

    Description

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

      We would like to exclude Versions from the current dashboard issue counts.

      For example if I have these versions in my project FOO.

      F1-M1
      F1-M2
      F1-M3
      F1-RC
      F2-M1

      I'd like to be able to exclude "F2-M1" since that is a future version that we are not working on yet, and that we are postponing issue to. This skews our dashboard numbers for our current drive to zero issues.

      Attachments

        1. 8938.JPG
          8938.JPG
          119 kB
        2. screenshot-2.jpg
          screenshot-2.jpg
          19 kB

        Issue Links

          is related to

          Suggestion - JRASERVER-8934 Re-opening issue against archived version doesn't prompt user for new version

          • Closed
          relates to

          Suggestion - JRACLOUD-8938 Allow Limiting by Version for Browser Project Open Issues Dashboard

          • Closed

          Suggestion - JRASERVER-8375 Allow Global saved filters to be used as a preset filter on the Browse Project page

          • Closed

          Activity

            People

              Unassigned Unassigned
              f54141d77f13 Randy James
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: