Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17392 Team-managed software projects
  3. JSWCLOUD-17317

Allow apps to create and retrieve links between epics and stories via API in next-gen projects

XMLWordPrintable

      Summary

      Currently, there's no way to get the reference of epics and sub-issues (e.g stories). It would be great to have this feature as this allow vendors form the relationship between epics and it's sub-issues.

      Use Cases:

      1. When an app is subscribed to a webhook via the descriptor, there's no way to see which epic the story is linked to
      2. When an app's feature is to create diagram for epics and sub-issues, there's no way to form it in next-gen projects

            [JSWCLOUD-17317] Allow apps to create and retrieve links between epics and stories via API in next-gen projects

            Eoin made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            Eoin added a comment - - edited

            As part of the next-gen project, we had the opportunity to re-think how epics worked and aligned the functionality with the Jira platform APIs.

            Please use the Issue type hierarchy API to see which issues are Epics in a next-gen project.

            Instead of the Agile REST APIs, in next-gen please use these alternatives:

            • Get issues without epic - Search for issues that don't belong to an epic by using the Search for issues using JQL operation in the Jira platform REST API. Build your JQL query using the parent is empty clause. For more information on the parent JQL field, see Advanced searching.
            • Get issues for epic - Search for issues that belong to an epic by using the Search for issues using JQL operation in the Jira platform REST API. Build your JQL query using the parent clause. For more information on the parent JQL field, see Advanced searching.
            • Move issues to epic - Edit the issue and set the parent field. Example: {"fields":
              Unknown macro: {"parent"}

              }

            • Remove issues from epic - Edit the issue and set the parent field to be empty. Example: {"fields":{"parent":{}}}
            • Create an issue in the epic by setting the parent field when calling the Create issue endpoint. Example: {"fields":
              Unknown macro: {"project"}

              }

            Eoin added a comment - - edited As part of the next-gen project, we had the opportunity to re-think how epics worked and aligned the functionality with the Jira platform APIs. Please use the Issue type hierarchy API to see which issues are Epics in a next-gen project. Instead of the Agile REST APIs, in next-gen please use these alternatives: Get issues without epic - Search for issues that don't belong to an epic by using the Search for issues using JQL operation in the Jira platform REST API. Build your JQL query using the parent is empty clause. For more information on the parent JQL field, see Advanced searching. Get issues for epic - Search for issues that belong to an epic by using the Search for issues using JQL operation in the Jira platform REST API. Build your JQL query using the parent clause. For more information on the parent JQL field, see Advanced searching. Move issues to epic - Edit the issue and set the parent field. Example: {"fields": Unknown macro: {"parent"} } Remove issues from epic - Edit the issue and set the parent field to be empty. Example: {"fields":{"parent":{}}} Create an issue in the epic by setting the parent field when calling the Create issue endpoint. Example: {"fields": Unknown macro: {"project"} }
            Andre van der Schyff made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 476512 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 3074254 ] New: JAC Sub-task Workflow [ 3475108 ]

            Henrik B Kaersgaard added a comment -

            Please do fix this issue, as this is crippling ProductBoard.coms integration with Jira Next Gen Projects!

            Henrik B Kaersgaard added a comment - Please do fix this issue, as this is crippling ProductBoard.coms integration with Jira Next Gen Projects!

            Nick Muldoon added a comment -

            Linking to https://ecosystem.atlassian.net/browse/ACJIRA-1634 as a duplicate. ACJIRA-1634 has double the votes on here at present.

            Easy Agile User Story Maps for Jira Cloud does not work for Next-Gen projects due to this functionality not being present. 85% of our monthly on-load errors come from people trying to load the story map on a Next-Gen project and being unable to retrieve epic links.

            Nick Muldoon added a comment - Linking to https://ecosystem.atlassian.net/browse/ACJIRA-1634 as a duplicate. ACJIRA-1634 has double the votes on here at present. Easy Agile User Story Maps for Jira Cloud does not work for Next-Gen projects due to this functionality not being present. 85% of our monthly on-load errors come from people trying to load the story map on a Next-Gen project and being unable to retrieve epic links.
            Nick Muldoon made changes -
            Remote Link New: This issue links to "ACJIRA-1634 (Ecosystem JIRA)" [ 416561 ]
            Paula Silveira made changes -
            Parent New: JSWCLOUD-17392 [ 1094115 ]
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 3008116 ] New: GreenHopper Kanban Workflow 20141014 - Restricted [ 3074254 ]
            Issue Type Original: Suggestion [ 10000 ] New: Sub-task [ 6 ]
            Anne Calantog made changes -
            Labels Original: cc-ecosystem cc-integration cc-migrations devhelp ecosystem New: cc-ecosystem cc-integration cc-migrations devhelp ecosystem next-gen
            Anne Calantog made changes -
            Remote Link New: This issue links to "DEVHELP-1897 (Ecosystem JIRA)" [ 398665 ]

              Unassigned Unassigned
              acalantog Anne Calantog
              Votes:
              15 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: