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

If the status is unmapped in the board configuration, any issue in this status will show as removed from sprint in the sprint report

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 7.13.0
    • Reports
    • None

      Issue Summary

      When a status is unmapped in the board config, it will not show in the sprint report.
      i.e. Issues transitioned to this status will:

      1. show under the Issues Removed From Sprint category
      2. show as if they were in the last status before transitioning to the current one that's unmapped.

      Steps to Reproduce

      1. Start sprint with issue A
      2. Resolve issue A
      3. Complete the sprint
      4. Go to sprint report. Issue A is listed under completed issue
      5. Go to column management page > un-map the Done status (to unmapped column)
      6. Go to the report again

      Expected Results

      The report shall not change

      Actual Results

      Issue A is listed under issue removed from sprint and show the previous status it transitioned to "Done" from.

      Workaround

      Make all workflow statuses in the "Complete" category mapped to columns so they're considered as complete in the reports.

            [JSWSERVER-20184] If the status is unmapped in the board configuration, any issue in this status will show as removed from sprint in the sprint report

            Kalin U added a comment -

            This bug affects Jira 9.12.22 too.

            Kalin U added a comment - This bug affects Jira 9.12.22 too.

            Wupadrasta Subbarao added a comment -

            This is literally causing a great issue. can an update be provided how to overcome the overwhelming churn rate caused due to bulk change applied on moving the status from un mapped to mapped? ideally speaking this should not be resulting in churn as churn is directly a result of moving out any jiras from the current sprint or adding to the current sprint or any change in the estimated efforts while the current sprint is in progress

            Wupadrasta Subbarao added a comment - This is literally causing a great issue. can an update be provided how to overcome the overwhelming churn rate caused due to bulk change applied on moving the status from un mapped to mapped? ideally speaking this should not be resulting in churn as churn is directly a result of moving out any jiras from the current sprint or adding to the current sprint or any change in the estimated efforts while the current sprint is in progress

              Unassigned Unassigned
              adridi Arbi Dridi
              Affected customers:
              12 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: