I have been tasked to try and use the API to migrate the open items in two projects on an instance of JIRA 6.2.5 to projects on a JIRA running 7.6.1. I was told that we can't do a data dump because that does not retains the links between parent and child items which we want to keep.
I am looking at the API's, the first step in the script process would be to look at what tickets are currently open and which have links, so:
http://jirahostrest/api/2/search?jql=project=xxxxx&fields=issuelinks
Great, if there are no links I get:
"issuelinks": []
However if there are links I get ALL of the information within the square brackets and I will have to parse it all looking for the bit I want.
What I want to do is only return information with the square brackets when it is not a clone link and I only want it to return the key of the linked item.
So my questions:
None of these work
http://jirahostrest/api/2/search?jql=project=xxxxx&fields=issuelinks:key
http://jirahostrest/api/2/search?jql=project=xxxxx&fields=issuelinks[key]
http://jirahostrest/api/2/search?jql=project=xxxxx&fields=issuelinks.key
1. Yes, see this article on how to structure your CSV. You will need to do a little bit of data transformation to get it into the structure after you export (or ideally, write a script to export it directly into the expected format)
https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-740262715.html
2. Yes though you could look into k15t's backbone add on which does issue replication across instances also. Not sure if it'll fit your use case though.
3. No but there are a plethora of json parsing and querying libraries that will do most of the heavy lifting for you if you are manipulating the responses from the API
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.