-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
Using the Get epics endpoint and querying for an specific status, the results are not consistent.
Environment
- Next-gen project
Steps to Reproduce
- Create a next-gen project;
- Create two epics, set one with the "Done" status, and the other with another status;
- Run the following endpoint on the browser:
https://<INSTANCE_NAME>.net/rest/agile/1.0/board/<BOARD_ID>/epic?done=falseSee the example on my test instance here.
Expected Results
Only the "Epic 1" should return.
Actual Results
Both Epics return as false.
{
"maxResults": 50,
"startAt": 0,
"isLast": true,
"values": [
{
"id": 12378,
"key": "RT-13",
"self": "https://becktokceb.atlassian.net/rest/agile/1.0/epic/12378",
"name": "",
"summary": "Epic 1",
"color": {
"key": "color_1"
},
"done": false
},
{
"id": 12379,
"key": "RT-14",
"self": "https://becktokceb.atlassian.net/rest/agile/1.0/epic/12379",
"name": "",
"summary": "Epic 2",
"color": {
"key": "color_1"
},
"done": false
}
]
}
Workaround
Use another endpoint to get the proper status for the specific Epics, examples:
- https://<INSTANCE_NAME>.atlassian.net/rest/agile/1.0/issue/<EPIC_KEY>?fields=status
- https://<INSTANCE_NAME>.atlassian.net/rest/api/3/issue/<EPIC_KEY>?fields=status
[JSWCLOUD-17997] Agile rest API for epic is not returning accurate results for the status
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | New: stale-bulk-close202006 |
| Workflow | Original: JSWCLOUD Bug Workflow [ 3269235 ] | New: JAC Bug Workflow v3 [ 3475033 ] |
| Status | Original: Verified [ 10005 ] | New: Gathering Impact [ 12072 ] |
| Status | Original: Open [ 1 ] | New: Verified [ 10005 ] |
I appreciate the input on the workaround - but I would suggest it's not much of a workaround. If you have ~25 Epics, that's 25 API calls instead of 1.
| Support reference count | New: 1 |
| Summary | Original: Agile rest api for epic is not returning accurate results for the status | New: Agile rest API for epic is not returning accurate results for the status |
| Description |
Original:
h3. Issue Summary
Using the [Get epics|https://developer.atlassian.com/cloud/jira/software/rest/#api-rest-agile-1-0-board-boardId-epic-get] endpoint and querying for an specific status, the results are not consistent. h3. Environment * Next-gen project h3. Steps to Reproduce # Create a next-gen project; # Create two epics, set one with the "Done" status, and the other with another status; # Run the following endpoint on the browser: {code:SQL}https://<INSTANCE_NAME>.net/rest/agile/1.0/board/<BOARD_ID>/epic?done=false{code} See the example on my test instance [here|https://cl.ly/003a635d9f23]. h3. Expected Results Only the "Epic 1" should return. h3. Actual Results Both Epics return as false. {code:JSON} { "maxResults": 50, "startAt": 0, "isLast": true, "values": [ { "id": 12378, "key": "RT-13", "self": "https://becktokceb.atlassian.net/rest/agile/1.0/epic/12378", "name": "", "summary": "Epic 1", "color": { "key": "color_1" }, "done": false }, { "id": 12379, "key": "RT-14", "self": "https://becktokceb.atlassian.net/rest/agile/1.0/epic/12379", "name": "", "summary": "Epic 2", "color": { "key": "color_1" }, "done": false } ] } h3. Workaround Use another endpoint to get the proper status for the specific Epics, examples: * https://<INSTANCE_NAME>.atlassian.net/rest/agile/1.0/issue/<EPIC_KEY>?fields=status * https://<INSTANCE_NAME>.atlassian.net/rest/api/3/issue/<EPIC_KEY>?fields=status |
New:
h3. Issue Summary
Using the [Get epics|https://developer.atlassian.com/cloud/jira/software/rest/#api-rest-agile-1-0-board-boardId-epic-get] endpoint and querying for an specific status, the results are not consistent. h3. Environment * Next-gen project h3. Steps to Reproduce # Create a next-gen project; # Create two epics, set one with the "Done" status, and the other with another status; # Run the following endpoint on the browser: {code:SQL}https://<INSTANCE_NAME>.net/rest/agile/1.0/board/<BOARD_ID>/epic?done=false{code} See the example on my test instance [here|https://cl.ly/003a635d9f23]. h3. Expected Results Only the "Epic 1" should return. h3. Actual Results Both Epics return as false. {code:JSON} { "maxResults": 50, "startAt": 0, "isLast": true, "values": [ { "id": 12378, "key": "RT-13", "self": "https://becktokceb.atlassian.net/rest/agile/1.0/epic/12378", "name": "", "summary": "Epic 1", "color": { "key": "color_1" }, "done": false }, { "id": 12379, "key": "RT-14", "self": "https://becktokceb.atlassian.net/rest/agile/1.0/epic/12379", "name": "", "summary": "Epic 2", "color": { "key": "color_1" }, "done": false } ] } {code} h3. Workaround Use another endpoint to get the proper status for the specific Epics, examples: * https://<INSTANCE_NAME>.atlassian.net/rest/agile/1.0/issue/<EPIC_KEY>?fields=status * https://<INSTANCE_NAME>.atlassian.net/rest/api/3/issue/<EPIC_KEY>?fields=status |
Hi all,
Thank you for raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.
To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.