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.

    • 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.

      Hello Team,

      We need the following feature improvement in Jira cloud.

      1. Ability to create different issue type *names *for epics (in my use case issue name Epic does not make sense and would prefer using different relevant name for Epic issue type)
      2. Ability to define multiple epic types (like we can create multiple Base and
        subtask types for a Jira Software instance)
      3. Remove the current  behaviour  that the system fixates on the word
        "epic" as an issue types name, but to rather use the TYPE value of an issue
        type to determine whether it is an epic, base or subtask.
        Thanks

            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.

              • 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.

                Hello Team,

                We need the following feature improvement in Jira cloud.

                1. Ability to create different issue type *names *for epics (in my use case issue name Epic does not make sense and would prefer using different relevant name for Epic issue type)
                2. Ability to define multiple epic types (like we can create multiple Base and
                  subtask types for a Jira Software instance)
                3. Remove the current  behaviour  that the system fixates on the word
                  "epic" as an issue types name, but to rather use the TYPE value of an issue
                  type to determine whether it is an epic, base or subtask.
                  Thanks

                        rswami@atlassian.com Rohan Swami (Inactive)
                        0ca90e17638a Mohanraj Thangamuthu
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            rswami@atlassian.com Rohan Swami (Inactive)
                            0ca90e17638a Mohanraj Thangamuthu
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: