Can we edit EPIC Link as a customfield_13386 using jira rest api 2 or do we have to use greenhopper

[Shrinish]

I am not able to insert field for customfield_13386 it gives an error as so:

{
"errorMessages": [
"gh.epic.error.not.found"
],
"errors": {}
}

I think it has to do something to do with greenhopper api .

[Derek Fields (RightStar) · Accepted solution]

You do need to use the Greenhopper API for this. See this KB

[Shrinish]

Thanks Derek ! Great help

[Shrinish]

Why is it that only Epic link field requires greenhopper API whereas others dont?

[Nic Brough -Adaptavist-]

Atlassian have not got around to refactoring the "greenhopper" name out of everything yet - Jira Software used to be called Agile, which was itself a rename of Greenhopper.  It's all one API with three names in parts of it.

[Shrinish]

thanks nic'

[Shrinish]

If you have the issue Key you could also do it using the Epic Key:

PUT https://localhost:8080/rest/api/2/issue-key

Body: 

{
"fields": {
"customfield_13386": "Epic Key"
}
}