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 create the epics that are associated with issuelinks ? through restapi/2

Sashank_ujktqb

i am trying with few subsequent calls in order be EPICS - story - task - bug

/rest/api/2/search?jql=project=XXXX%20and%20issuetype=%22Epic%22&startAt=0&maxResults=400"

/rest/api/2/search?jql=project=XXXX%20and%20issuetype=%22story%22&startAt=0&maxResults=400"

/rest/api/2/search?jql=project=XXXX%20and%20issuetype=%22task%22&startAt=0&maxResults=400"

/rest/api/2/search?jql=project=XXXX%20and%20issuetype=%22bug%22&startAt=0&maxResults=400"

approach1:

here how can i ignore issuelink and create them after the bug calll

approach 2:

how can i create epics first without issuelinks and attach them later?

pr any alternative approach ?

pl advise

Accepted answers

All comments

Florian Bonniec

Hi @Sashank

What are you trying to do ? You call are just jql search ?

You should not use link to manage epics and story as it's how it used in the background, in the foreground you should use Epic Link and Epic Name.

EPic Name is the name of the EPic, it's a field

Epic link is the reference from the task under the EPic, it's a field also.

You can create an Epic then link any issue to it by updating the issue and set the epic issue key as Epic Link value for the field using the API.

Regards

Sashank_ujktqb

Hi @Florian Bonniec

Here i am trying to migrate all the issues from one instance to another instance .
so trying to create epics first where i see the issuetype:story as well coming in through linkedissues. So during a get call as i am grabbing the issue id values into variables from old instance and making a post call for creating issues onto new instance. But for as these issuetypes of story is coming up my post call fails by throwing no epic found error as linked issue is coming ahead of the epic in post call execution.
so i m looking a way to dodge this issue or follow any alternative & better approach ?

Florian Bonniec

I think you should create Epics, get a mapping with the old and new key then create stories without any epic link and keep populate the mapping old/new Key. Then once everything is imported, go over all issues in the source instance that have an Epic Link value and update the associate one in the new instance with the new epic link you should have in your mapping table.

Are you migratin the whole instance or just project by project ? You may have Stories linked to epics from another project if you choose the second option.

Sashank_ujktqb

So here inwas following that approach as you suggested above but during my get call on epics i am recieving the issuelinks(linkedissues) too which inwanted to skip and recieve only epics.
so i am looking for a way to get only epics and not linked issues.
can you suggest ?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

api

jira-server

issue-link

epic

story