Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-86957

Expand "Parent" field to match functionality with deprecated "Epic Link" field

XMLWordPrintable

    • 1

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

      The "Epic Link" field, which is being removed in 2022, has useful sub-fields such as

      • Epic Link.color
      • Epic Link.id
      • Epic Link.name
      • Epic Link.status

      The successor to "Epic Link" is "Parent." Unfortunately, "Parent" has no such sub-fields. As a result, when we move from using "Epic Link" to "Parent," we will be losing important functionality.

      Please expand "Parent" to include the same valuable sub-fields that "Epic Link" had.

            [JRACLOUD-86957] Expand "Parent" field to match functionality with deprecated "Epic Link" field

            Michael Flores added a comment - - edited

            mhunter , this issue is still VERY important to my team. Please re-open and, if possible, implement it before the Epic Link field is permanently removed. Otherwise, we will have no fallback option. Thank you.

            Michael Flores added a comment - - edited mhunter , this issue is still VERY important to my team. Please re-open and, if possible, implement it before the Epic Link field is permanently removed. Otherwise, we will have no fallback option. Thank you.

            Matthew Hunter added a comment -
            Atlassian Update - April 8, 2025

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - April 8, 2025 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Michael Flores added a comment - - edited

            mhunter 

            To clarify, these Epic Link.<attribute> fields become most valuable when working with API integrations such as Jira to Google or Centercode to Jira.

            Michael Flores added a comment - - edited mhunter   To clarify, these Epic Link.<attribute> fields become most valuable when working with API integrations such as Jira to Google or Centercode to Jira.

              Unassigned Unassigned
              844b774df5ee Michael Flores
              Votes:
              8 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: