Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-26916

Treat custom epic issue types like a base level (e.g. task, story) issue types in the backlog

XMLWordPrintable

    • 29
    • 49
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update – 19 Dec 2024

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. To uphold our value for transparency, we wanted to provide an update that we have no immediate plans to put this suggestion on our near term roadmap.

      To recap on this topic, in July 2024 there was a change to treat custom epic issue types to make them behave like the epic issue type that is provided out of the box by Jira. This was the original intended behaviour and we apologise it was done subsequent to the initial rollout of custom epic issue types. We don't expect to change this behaviour in the near term.

      We understand that our decision may be disappointing and we apologise for any inconvenience.

      Regards,
      Eoin
      Product Manager, Jira

      After this https://jira.atlassian.com/browse/JSWCLOUD-25522 was released, the custom epic issue type is being recognized by the epic panel in the backlog, so these custom epics no longer appear in the backlog.

      The customer wants to be able to choose whether or not this issue type will be considered in the Epic panel or not.

              Unassigned Unassigned
              b60c2e526cc5 João Carlos Montanha Zurobski
              Votes:
              34 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated:
                Resolved: