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

Plan should use Issue Resolution rather than Issue Status Category to determine when to remove issues

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

      Problem definition

      Currently issues are removed from a plan if they are in a Status of Done Category (Green).

      Exception: Issues that have Sub Tasks that are not in the Done category will continue to display in the Plan until all Sub Tasks are in the Done category as well. 

      Suggested solution

      Issue Resolution should be used to determine whether issues are to be removed instead of Status.

      Why this is important

      If issues are in a Green status but not resolved, they won't show up in the plan unexpectedly.

      Workaround

      In version 2.22+, enable this dark feature:

      com.atlassian.portfolio.issueloading.includeUnresolvedCompleted

      by adding it from <JIRA_BaseURL>/secure/SiteDarkFeatures!default.jspa

          Form Name

            [JSWSERVER-25116] Plan should use Issue Resolution rather than Issue Status Category to determine when to remove issues

            Reddeppa added a comment -

            +1

            Reddeppa added a comment - +1

            +1, definitely would be more clear for users (even if it`s a basic good practice to have all statusCategory = Done issues with resolution assigned) - now they have some retention period for Done issues set and they have no clue why the issues are disappearing from the plan.

            Stanisław Białowąs added a comment - +1, definitely would be more clear for users (even if it`s a basic good practice to have all statusCategory = Done issues with resolution assigned) - now they have some retention period for Done issues set and they have no clue why the issues are disappearing from the plan.

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Richard Adams added a comment - - edited

            This issue has been around forever and still not fixed? Why remove any Issue from a plan automatically? There is a filter for Status which, if it worked correctly, would allow us to include or exclude based on status as we wish. Instead, DONE issues are automatically removed, irrespective of this filter. 

            Come on. How about instead of buying back its own stock with its free cash flow Atlassian invest some of its money in making its products actually work (and not ignore an obvious issue like this after almost 5 years). 

            Richard Adams added a comment - - edited This issue has been around forever and still not fixed? Why remove any Issue from a plan automatically? There is a filter for Status which, if it worked correctly, would allow us to include or exclude based on status as we wish. Instead, DONE issues are automatically removed, irrespective of this filter.  Come on. How about instead of buying back its own stock with its free cash flow Atlassian invest some of its money in making its products actually work (and not ignore an obvious issue like this after almost 5 years). 

            Hero Honda engine oil manufacturer distributor bane Amaron company e engine oil and mobile signal booster LED bulb PH 925 022 2202

            Amaron Company added a comment - Hero Honda engine oil manufacturer distributor bane Amaron company e engine oil and mobile signal booster LED bulb PH 925 022 2202

            NAYANA added a comment -

            Irrespective of the status given that an issue is part of the source, I want to see it in the plan so that I can work with it, create reports against and or manage related work.

            NAYANA added a comment - Irrespective of the status given that an issue is part of the source, I want to see it in the plan so that I can work with it, create reports against and or manage related work.

              Unassigned Unassigned
              mriza Mohamed Riza (Inactive)
              Votes:
              41 Vote for this issue
              Watchers:
              43 Start watching this issue

                Created:
                Updated: