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

As a PO, I want the Epic status field to match the StatusCategory of the Epic so that I can work with a Kanban board

XMLWordPrintable

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

      Now that the StatusCategory property exists, it would be much easier to work with Epics if the behavior around the "Epic Status" field could be deprecated in favor of the StatusCategory property.

      A PO would set-up a Kanban board to work with (and eventually plan - see GHS-6175) Epic-level items and this would be reflected in the Scrum boards automatically.

            [JSWSERVER-10836] As a PO, I want the Epic status field to match the StatusCategory of the Epic so that I can work with a Kanban board

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068961 ] New: JAC Suggestion Workflow 3 [ 3659619 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Clement made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 429795 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2623335 ] New: JAC Suggestion Workflow [ 3068961 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Gosia Kowalska added a comment -
            Atlassian Update – 22 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 – 22 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
            SET Analytics Bot made changes -
            Support reference count New: 2
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323826 ] New: Confluence Workflow - Public Facing v4 [ 2623335 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2041904 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323826 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029932 ] New: JIRA PM Feature Request Workflow v2 [ 2041904 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 735840 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029932 ]

              Unassigned Unassigned
              38447ed50c64 Nicolas Bier
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: