-
Bug
-
Resolution: Fixed
-
Low
-
None
-
4
-
Severity 3 - Minor
-
Summary
Agile rest api for epic is not working for Next-gen projects.
Steps to Reproduce
- Create a next gen scrum project
- Create an epic in the board
- Call the agile board rest api for epics
GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]}
- Call the self URL of the epic
GET https://site.atlassian.net/rest/agile/1.0/epic/11472
Expected Results
The epic details should be returned
Actual Results
The call fails with a 404 and permission error message.
Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472
Request Method: GET
Status Code: 404
{"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}}
[JSWCLOUD-17305] Agile rest api for epic is not working for Next-gen projects.
Thanks Nathan,
I noticed this was now working a couple of days ago.
This has unblocked an important feature for my app.
Great work. Much appreciated.
Best Regards,
Rhys
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
Hi everyone,
Thanks for commenting and voting on this ticket.
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":{"parent":{"id":"11111"}}}
Remove issues from epic - Edit the issue and set the parent field to be empty. Example: {"fields":{"parent":{}}}
{"fields":{"parent":{}}}
Create an issue in the epic by setting the parent field when calling the Create issue endpoint. Example:
{"fields":{"project":{"id":"11111"},"issuetype":{"id":"11111"},"summary":"aaaaa","parent":{"id":"11111"}}}
Regards,
Nathan Sturgess
nsturgess@atlassian.com
Product Manager, JIRA Platform
| Description |
Original:
{panel:title=Atlassian Update – 23 October 2018|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
Hi everyone, Thanks for commenting and voting on this ticket. 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":{"parent":{"id":"11111"}}} 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":{"project":{"id":"11111"},"issuetype":{"id":"11111"},"summary":"aaaaa","parent":{"id":"11111"}}} Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Summary [Agile rest api|https://developer.atlassian.com/cloud/jira/software/rest/] for epic is not working for Next-gen projects. h3. Steps to Reproduce - Create a next gen scrum project - Create an epic in the board - Call the agile board rest api for epics {code} GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]} {code} - Call the self URL of the epic {code} GET https://site.atlassian.net/rest/agile/1.0/epic/11472 {code} h3. Expected Results The epic details should be returned h3. Actual Results The call fails with a 404 and permission error message. {noformat} Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472 Request Method: GET Status Code: 404 {"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}} {noformat} |
New:
h3. Summary
[Agile rest api|https://developer.atlassian.com/cloud/jira/software/rest/] for epic is not working for Next-gen projects. h3. Steps to Reproduce - Create a next gen scrum project - Create an epic in the board - Call the agile board rest api for epics {code} GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]} {code} - Call the self URL of the epic {code} GET https://site.atlassian.net/rest/agile/1.0/epic/11472 {code} h3. Expected Results The epic details should be returned h3. Actual Results The call fails with a 404 and permission error message. {noformat} Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472 Request Method: GET Status Code: 404 {"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}} {noformat} |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-4812]. {panel} {panel:title=Atlassian Update – 3 October 2019|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff} Hi everyone, Thanks for commenting and voting on this ticket. 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":{"parent":{"id":"11111"}}} 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":{"project":{"id":"11111"},"issuetype":{"id":"11111"},"summary":"aaaaa","parent":{"id":"11111"}}} Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Summary [Agile rest api|https://developer.atlassian.com/cloud/jira/software/rest/] for epic is not working for Next-gen projects. h3. Steps to Reproduce - Create a next gen scrum project - Create an epic in the board - Call the agile board rest api for epics {code} GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]} {code} - Call the self URL of the epic {code} GET https://site.atlassian.net/rest/agile/1.0/epic/11472 {code} h3. Expected Results The epic details should be returned h3. Actual Results The call fails with a 404 and permission error message. {noformat} Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472 Request Method: GET Status Code: 404 {"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}} {noformat} |
New:
{panel:title=Atlassian Update – 23 October 2018|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
Hi everyone, Thanks for commenting and voting on this ticket. 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":{"parent":{"id":"11111"}}} 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":{"project":{"id":"11111"},"issuetype":{"id":"11111"},"summary":"aaaaa","parent":{"id":"11111"}}} Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Summary [Agile rest api|https://developer.atlassian.com/cloud/jira/software/rest/] for epic is not working for Next-gen projects. h3. Steps to Reproduce - Create a next gen scrum project - Create an epic in the board - Call the agile board rest api for epics {code} GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]} {code} - Call the self URL of the epic {code} GET https://site.atlassian.net/rest/agile/1.0/epic/11472 {code} h3. Expected Results The epic details should be returned h3. Actual Results The call fails with a 404 and permission error message. {noformat} Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472 Request Method: GET Status Code: 404 {"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}} {noformat} |
| Description |
Original:
h3. Summary
[Agile rest api|https://developer.atlassian.com/cloud/jira/software/rest/] for epic is not working for Next-gen projects. h3. Steps to Reproduce - Create a next gen scrum project - Create an epic in the board - Call the agile board rest api for epics {code} GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]} {code} - Call the self URL of the epic {code} GET https://site.atlassian.net/rest/agile/1.0/epic/11472 {code} h3. Expected Results The epic details should be returned h3. Actual Results The call fails with a 404 and permission error message. {noformat} Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472 Request Method: GET Status Code: 404 {"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}} {noformat} |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-4812]. {panel} {panel:title=Atlassian Update – 3 October 2019|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff} Hi everyone, Thanks for commenting and voting on this ticket. 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":{"parent":{"id":"11111"}}} 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":{"project":{"id":"11111"},"issuetype":{"id":"11111"},"summary":"aaaaa","parent":{"id":"11111"}}} Regards, Nathan Sturgess nsturgess@atlassian.com Product Manager, JIRA Platform {panel} h3. Summary [Agile rest api|https://developer.atlassian.com/cloud/jira/software/rest/] for epic is not working for Next-gen projects. h3. Steps to Reproduce - Create a next gen scrum project - Create an epic in the board - Call the agile board rest api for epics {code} GET https://site.atlassian.net/rest/agile/1.0/board/<BOARD_ID>/epic {"maxResults":50,"startAt":0,"isLast":true,"values":[{"id":11472,"key":"SCRUM-19","self":"https://site.atlassian.net/rest/agile/1.0/epic/11472","name":"","summary":"epic","color":{"key":"color_1"},"done":false}]} {code} - Call the self URL of the epic {code} GET https://site.atlassian.net/rest/agile/1.0/epic/11472 {code} h3. Expected Results The epic details should be returned h3. Actual Results The call fails with a 404 and permission error message. {noformat} Request URL: https://try-ramon-appswitcher.atlassian.net/rest/agile/1.0/epic/11472 Request Method: GET Status Code: 404 {"errorMessages":["The requested epic cannot be viewed because it either does not exist or you do not have permission to view it."],"errors":{}} {noformat} |
Is there an update from Jira eng here? Shipping broken API's is terrible practice.
Thanks goes to the team rhys5690, so i will be sure to pass it on. My apology that you didn't get it sooner, thanks for the kind words.