Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10915

Do not include fixversions that aren't relevant to the filter

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • 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.

      As a product owner that manages a team that works on a variety of projects at one time,
      I want only the fixversions that are associated with the issues that I have included in my filter to display in the versions column of the scrum board
      To reduce the amount of noise and scrolling required to work with the board and our team's backlog.

      Right now, we have teams that work on issues that may cross 3-5 different projects, even more. We create a scrum board based on labels that identify the team.

      However, the board displays every unarchived version associated with every project that the filter's query is associated with. And, it's not clear, without expanding each version, which have issues associated it.

      The versions functionality should be consistent with the epics in that only those epics that meet the filter criteria appear on the board - not every epic associated with the project that the filter is associated with.

          Form Name

            [JSWSERVER-10915] Do not include fixversions that aren't relevant to the filter

            Atlassian Update – 20 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 20 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              4f4250feead3 Karie Kelly
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: