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

Scope changes are inconsistent

XMLWordPrintable

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

      Usecase #1
      If you use Convert to Issue on a sub-task, the issue is removed from the current sprint and completely disappears from all reports (e.g. sprint report, burndown report)

      Usecase #2
      If you change an issue's metadata so that it no longer matches the rapidboard's filter query, it completely disappears from all reports (e.g. sprint report, burndown report)

            [JSWSERVER-8457] Scope changes are inconsistent

            Gosia Kowalska added a comment -
            Atlassian Update – 28 February 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 – 28 February 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

            Michael Tokar added a comment -

            We won't address use case #2 as it is very difficult for us to include issues in our report when they no longer match the board's filter.

            Michael Tokar added a comment - We won't address use case #2 as it is very difficult for us to include issues in our report when they no longer match the board's filter.

              Unassigned Unassigned
              4ef8826114c9 Fabian Meier
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: