i am trying with few subsequent calls in order be EPICS - story - task - bug
here how can i ignore issuelink and create them after the bug calll
how can i create epics first without issuelinks and attach them later?
pr any alternative approach ?
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.
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 ?
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.
Can you clean the json you receive and remove the link issue part ?
So you sould get all issues, remove issue link part and epic link field. Once imported you update all issue with the links and epic link this time.
Be aware that Epic <> Stories relation is not a link for JIRA, the association is done using the "Epic Link" field.
You will have issue and have to clean the json you receive if you do project by project because you will always have issue link to an issue in another project or a story under an epic in another project.
Not really, because if you query issue without link, import all of them then all issues with links you will have the same issue because if issue A is linked to B any of your query will return A nor B because A as a link with B and B as a link with A.
There is also some apps on the market place that may help you and can be worse to evaluate such as configuration manager.
Right, it's how I would do it, clean the Json response or build a new Json from the response to create the new issue.
This link may be interested to you too.