Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2868

Forecast - "Parent" column not showing up on the report

      Issue Summary

      Forecast - "Parent" column not showing up on the report

      Steps to Reproduce

      1. Login 
      2. Select a Program and PI
      3. Browse to Forecast view
      4. Make sure "Parent" column is selected

      Expected Results

      Parent column toggle should be removed as "Theme" is available as a column

      Actual Results

      Parent column is not shown

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JIRAALIGN-2868] Forecast - "Parent" column not showing up on the report

            Don Fuller added a comment -

            Hi everyone, 

            Thank you for sharing your feedback.  

            Over the past several months, Jira Align Product and Engineering teams have reviewed over 1,000 JAC tickets in an effort to better understand the biggest problem areas, and make a concentrated effort to respond to your feedback more efficiently.

            With this renewed focus and organization, we have decided to deprioritize and close this ticket. Here are a few reasons this ticket might be getting closed:
             - The ticket had an impact score of <4 (combination of watchers, participants, votes and linked issues)
             - The bug was older than 18 months (from Oct 1, 2022) with an impact score of <=6
             - The bug was created more than 30 months ago
             - The bug was part of a component (functional area) listed for deprecation

            Moving forward, you will notice the following:
             - all existing tickets with a bug status will be addressed within the next few quarters;
             - all new tickets with a bug status will be addressed according to Atlassian's Cloud Bug Fix Policy;
             - all new and existing tickets with a suggestion status will be considered as part of our product roadmap, which will be communicated during our quarterly roadmap webinar;
             - all tickets with a won't fix status will be deprioritized.

            To elaborate on tickets with a suggestion status, we will either create new projects that address the underlying issue, or incorporate these tickets into existing projects.

            Thanks, Sam Ugulava | Sr. Product Manager

            Don Fuller added a comment - Hi everyone,  Thank you for sharing your feedback.   Over the past several months, Jira Align Product and Engineering teams have reviewed over 1,000 JAC tickets in an effort to better understand the biggest problem areas, and make a concentrated effort to respond to your feedback more efficiently. With this renewed focus and organization, we have decided to deprioritize and close this ticket. Here are a few reasons this ticket might be getting closed:  - The ticket had an impact score of <4 (combination of watchers, participants, votes and linked issues)  - The bug was older than 18 months (from Oct 1, 2022) with an impact score of <=6  - The bug was created more than 30 months ago  - The bug was part of a component (functional area) listed for deprecation Moving forward, you will notice the following:  - all existing tickets with a bug status will be addressed within the next few quarters;  - all new tickets with a bug status will be addressed according to Atlassian's Cloud Bug Fix Policy;  - all new and existing tickets with a suggestion status will be considered as part of our product roadmap, which will be communicated during our quarterly roadmap webinar;  - all tickets with a won't fix status will be deprioritized. To elaborate on tickets with a suggestion status, we will either create new projects that address the underlying issue, or incorporate these tickets into existing projects. Thanks, Sam Ugulava | Sr. Product Manager

              dfuller@atlassian.com Don Fuller
              e992016a60b0 Vishwajit Vinchurkar
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: