nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to programmatically add Epic links to Jira Tickets?

kavindha ranasinghe

I have developed an add-on which has the capability to connect to our remote application and import security vulnerabilities into Jira server as Jira issues(Story and bug tickets).

However I need to link these stories to epics and bugs to stories (programmatically) respectively. Anyone here who has tried this before or have an idea on how to proceed with this?

Below are two approaches I have tried

Approach 1- Update the epic link of an issue that is already created.

MutableIssue missue = issueManager.getIssueObject(jiraIssue.getKey());
CustomFieldManager cfMgr = ComponentAccessor.getCustomFieldManager();
CustomField epicCustomField = cfMgr.getCustomFieldObjectByName("Epic Link");
MutableIssue epicIssue = issueManager.getIssueObject("B1-976");// This is my epic 

 epicCustomField.updateValue(null, missue,
new ModifiedValue(missue.getCustomFieldValue(epicCustomField), epicIssue),
new DefaultIssueChangeHolder());

Approach 2- Set Epic link when a new issue is being created

MutableIssue newJIRAIssue = ComponentAccessor.getIssueFactory().getIssue();
CustomFieldManager cfMgr = ComponentAccessor.getCustomFieldManager();
CustomField epicCustomField = cfMgr.getCustomFieldObjectByName("Epic Link");

MutableIssue epicIssue = ComponentAccessor.getIssueManager().getIssueObject("B1-976");// This is my epic 

newJIRAIssue.setCustomFieldValue(epicCustomField, epicIssue);

Both approaches are not working. The issues are created/updated successfully with all other custom fields except the Epic Link.

Any help on this will be highly appreciated.

Accepted answers

All comments

brbojorque

Hi @kavindha ranasinghe ,

I'm looking at the code and they seem alright, one problem I can point out is the saving of the custom field / issue.

You have to save it in order for the changes to persist.

Something like this should do it.

issueManager.updateIssue(userObj, issue, Event...)

kavindha ranasinghe_w47q8q

Hi @brbojorque

Thank you for the suggestion. I am doing this later on in the code once I have completed adding the rest of the fields such as assignee and reporter as well. All the default Jira fields and custom fields are created successfully in the ticket except the Epic Link.

Andreas Didion_39u08t

Hi,
I'm trying to link Epics as well. Up to now I wasn't succesfull.

I found some examples during my research. But only with Groovy scripts.
I'm wondering how the relation between the Epic issue and the issues IN the Epic works.
In your example (Approach 2) you set the custom field only at the new created issue. I could imagine that an update of the custom field at the EPIC is needed too.
I'll continue today finding a solution. Each hint is very welcome and for sure I'll post my solution - if I found one ;-)

kavindha ranasinghe_w47q8q

Hi @Andreas Didion

I tried the same thing out on Jira Cloud using the REST API and it is working fine with Jira Cloud looks like the issue is with Jira Server. Here is my approach if you want to try it out as well.

Approach 1 - Create issue and then add the issue/s to the relevant Epic.

This can be achieved using the below end point and JSON body

POST -  /rest/agile/1.0/epic/{epicKey}/issue
Body -   {  {  "issues": [    "issue-1, issue-2, issue-3"  ]}

Approach 2 - Add the epic to the Epic link custom field during or after issue creation

This can be achieved using the below end point and JSON body

PUT - /rest/api/2/issue/{issueKey}
Body - { "fields": {"customfield_10008" : "EpicKey" } } //customfield_10008 represents Epic Link

Andreas Didion_39u08t

Hi @kavindha ranasinghe

Thank you. I need to do it programmatically with Java on Jira Server. (we implemented an own plugin which must be extended by this function)

If the logic in code is the same as via webservice I think

- during creation: add the Key of the EPIC to the customfield at new issue
- after creation: add the issue(s) to the EPIC

But how does the EPIC "knows" during creation of a new Issue that the new Issue is an issue within this EPIC? It sounds unlogical to me that the EPIC needs no update.

kavindha ranasinghe_w47q8q

Hi @Andreas Didion

I don't think there's any problem with the logic there because if we were doing this manually we only have to give the name of the EPIC on the issue creation page nothing to update on the Epic side.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

server

jira

jira-server