-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
7.0.10
-
7
-
Can not set epic links with Jira REST API. We are using REST API to integrate 2 Jira instances and I can not figure out a way to set epic links.
Here are the problems:
1) When using POST /rest/api/2/issue/12345 to set epic link, it only works when there is no previous epic set. So it only works when setting the epic for the first time. Using this to move issues between epics fails. (Internal Server Error 500 is returned)
2) Agile API POST /rest/agile/1.0/epic/521/issue does not seem to work. I only get 404
3) Also any oldschool greenhopper API-s that can be used to set epic link dont work. Also 404
Please help, this is major annoyance, we have over 50 issues at the moment that are not syncing, because epic link has changed. This would take significant amount of time to fix manually and the problem is growing every day. I would very much prefer if you would just allow us to set epic link using /rest/api/2/issue/12345. Why is this not allowed?
- is duplicated by
-
JSWSERVER-7017 As a user, i want to add/update an issue Epic link by using REST API
- Closed
[JSWSERVER-13156] Cannot set Epic link using Jira REST API
| Minimum Version | New: 7 |
| Workflow | Original: JAC Bug Workflow v2 [ 2852960 ] | New: JAC Bug Workflow v3 [ 2935849 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545657 ] | New: JAC Bug Workflow v2 [ 2852960 ] |
| Fix Version/s | New: 7.1.0 [ 59897 ] | |
| Fix Version/s | Original: 7.1.0 Server [ 61099 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548468 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545657 ] |
| Labels | New: affects-server |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1133253 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548468 ] |
| Fix Version/s | New: 7.1.0 Server [ 61099 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Description |
Original:
Can not set epic links with Jira REST API. We are using REST API to integrate 2 Jira instances and I can not figure out a way to set epic links.
Here are the problems: 1) When using POST /rest/api/2/issue/12345 to set epic link, it only works when there is no previous epic set. So it only works when setting the epic for the first time. Using this to move issues between epics fails. (Internal Server Error 500 is returned) 2) Agile API POST /rest/agile/1.0/epic/521/issue does not seem to work. I only get 404 3) Also any oldschool greenhopper API-s do set epic link dont work. Also 404 Please help, this is major annoyance, we have over 50 issues at the moment that are not syncing, because epic link has changed. This would take significant amount of time to fix manually and the problem is growing every day. I would very much prefer if you would just allow us to set epic link using /rest/api/2/issue/12345. Why is this not allowed? |
New:
Can not set epic links with Jira REST API. We are using REST API to integrate 2 Jira instances and I can not figure out a way to set epic links.
Here are the problems: 1) When using POST /rest/api/2/issue/12345 to set epic link, it only works when there is no previous epic set. So it only works when setting the epic for the first time. Using this to move issues between epics fails. (Internal Server Error 500 is returned) 2) Agile API POST /rest/agile/1.0/epic/521/issue does not seem to work. I only get 404 3) Also any oldschool greenhopper API-s that can be used to set epic link dont work. Also 404 Please help, this is major annoyance, we have over 50 issues at the moment that are not syncing, because epic link has changed. This would take significant amount of time to fix manually and the problem is growing every day. I would very much prefer if you would just allow us to set epic link using /rest/api/2/issue/12345. Why is this not allowed? |