We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90581

Custom epic issue type is not recognized by the epic panel in the backlog

      Update 12th December 2023

      Custom epic issue type is now supported on Timeline. Epic panel is still pending.

      Issue Summary

      The custom epic issue type is not recognized by the timeline and epic panel in the backlog

      Steps to Reproduce

      1. Create a custom issue type and add it to the epic level in the issue type hierarchy.
      2. Remove the epic issue type from the project and add the custom issue type which is at the epic level in the project.

      Expected Results

      The timeline and epic panel in the backlog should recognize the custom issue type added at the epic level in the issue type hierarchy.

      Actual Results

      The timeline and epic panel in the backlog is not recognizing the custom issue type added at the epic level in the issue type hierarchy.

      Workaround

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

        1. screenshot-1.png
          screenshot-1.png
          197 kB
        2. screenshot-2.png
          screenshot-2.png
          340 kB
        3. screenshot-3.png
          screenshot-3.png
          204 kB

          Form Name

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-90581

            Custom epic issue type is not recognized by the epic panel in the backlog

                Update 12th December 2023

                Custom epic issue type is now supported on Timeline. Epic panel is still pending.

                Issue Summary

                The custom epic issue type is not recognized by the timeline and epic panel in the backlog

                Steps to Reproduce

                1. Create a custom issue type and add it to the epic level in the issue type hierarchy.
                2. Remove the epic issue type from the project and add the custom issue type which is at the epic level in the project.

                Expected Results

                The timeline and epic panel in the backlog should recognize the custom issue type added at the epic level in the issue type hierarchy.

                Actual Results

                The timeline and epic panel in the backlog is not recognizing the custom issue type added at the epic level in the issue type hierarchy.

                Workaround

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

                  1. screenshot-1.png
                    screenshot-1.png
                    197 kB
                  2. screenshot-2.png
                    screenshot-2.png
                    340 kB
                  3. screenshot-3.png
                    screenshot-3.png
                    204 kB

                        vle2@atlassian.com Vu Le
                        2a7f4ad44e0d Ramchandra Kudtarkar
                        Votes:
                        30 Vote for this issue
                        Watchers:
                        55 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            vle2@atlassian.com Vu Le
                            2a7f4ad44e0d Ramchandra Kudtarkar
                            Affected customers:
                            30 This affects my team
                            Watchers:
                            55 Start watching this issue

                              Created:
                              Updated:
                              Resolved: