NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
When updating an issue epic link information using PUT action against /rest/api/2/issue, the status returned is 204 but the changes made is not reflected in the issue.
curl -D- -u admin:admin -X PUT --data @/Users/Vicky/Desktop/test.json -H "Content-Type: application/json" http://localhost:8085/522/rest/api/2/issue/test-1
Sample of test.json:
{
"fields":
{
"customfield_10006": "TEST-3"
}
}
TEST-3 is an issue of the type Epic
Perhaps, the reason why we are not able to update/edit the Epic Link custom field value is because the value itself is not showing in the Edit Screen, although the field itself has been mapped to the screen in the screen configuration. Anyway, it will be great if we are able to update an issue Epic Link information via REST API.
- duplicates
-
JSWSERVER-13156 Cannot set Epic link using Jira REST API
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
JSWCLOUD-7017 As a user, i want to add/update an issue Epic link by using REST API
- Closed
- Testing discovered
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-7017] As a user, i want to add/update an issue Epic link by using REST API
@ialexeyenko Can you please clarify exactly how we should be setting the epic link? If there is a documentation page explaining that which you can point us to that will be great.
Thanks!
Hi Everyone,
This has been fixed as part of JSW-13156 and is available in JIRA Software 7.1.4 Server, JIRA Agile 6.7.14.
Cheers,
Ignat
JIRA Bugmaster.
Brian Witt
added a comment - Hi, I'm trying to have new issues opened via REST api have the Epic link set but it seems I am hitting this bug; any progress on this? If this issue is resolved that would include creating a new issue with the customfield set, correct?
Brian Witt
added a comment - Hi, I'm trying to have new issues opened via REST api have the Epic link set but it seems I am hitting this bug; any progress on this? If this issue is resolved that would include creating a new issue with the customfield set, correct? Has this become possible now that the Epic links are visible in the issue browser?
Regards,
Kim
Hello. I am the originator of this issue. Just to justify why this issue is relevant (and lets ignore the fact that it can be retrieved by REST but not updated the same way):
When starting new projects usually there are a number of project milestones, gates, documentation - whatnot - that every project must pass or complete. Having the ability to pre-fill a new project with these standard stories and corresponding epics is extremely powerful and is something that is already used by everyone managing their projects using a spreadsheet template. It makes sense to me that epic links can be updated from the REST API.
I could even vote for something like this to become a real feature of greenhopper. Kind of a project setup option that could import for example YAML like this:
ISSUES:
- ISSUE:
fields:
summary: Create and approve development order
description: |
bla bla bla
bla blabla bla bla
issuetype: Epic
customfield_10404: Development order
- ISSUE:
fields:
summary: Create development order
description: |
The where what why, aceeptance
issuetype: Story
linkepic: Yes
But REST is fine for me as I already have the other bits in place.
All the best,
Kim
Can we get how this should be done clarified? Very difficult to find documentation on how to do a lot of things with Jira API.