Is there a version of application which is supporting Jira with extension structure

[muthu3758]

We have in our Jira hierarchy additional of 2 levels.

Portfolio Epic Capability

Epic Stories Task

If there is such version or how to mention it in the config file, please do share that information.

[Alexander-Hjelm]

Custom issue types can be migrated by including them in the type-map in your config.

See the documentation of the config file here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/config.md

[muthu3758]

We have done that type mapping for the custom work item type, but we are missing the child links.

1. I don't see the child link when I check in the API
2. I don't see the history related with this Child link in the parent work item of Jira

Are these reasons that tool is not able to get the child links

[Alexander-Hjelm]

Not to my knowledge. Are the children in the same project as the parents?

Maybe the links are in fact not standard Jira IssuesLinks but something custom managed by an extension of yours? In that case we cannot guarantee that your data will be supported.

[muthu3758]

How do we check whether links are managed by Extension or standard links.

[Alexander-Hjelm]

You should be able to see them in the list of links on the Jira Issue:

Also, they must be present on the issue Rest API reponse. Here is an example query: https://xxxxxxxxxx.atlassian.net/rest/api/3/issue/PROJECTKEy-123?expand=issuelinks

See the below screenshots.

[muthu3758]

Thanks a lot for your quick response

Below are the screenshots from RestAPI call and Jira

In this case there is a chance that this might have attached via some extension?

[muthu3758]

@Alexander-Hjelm What recommendations do you have for resolving the current issue?

[Alexander-Hjelm]

It sure looks like that is a standard parent-child relation to me.

What if you view the link types in the project settings in Jira? It's a long shot, but could it be that you have multiple Link Types sharing the same Name or something like that?

[muthu3758]

For me it looks like this is not the standard Link, reasons are.

1. I'm not getting this Child links in Rest API call
2. If you see the above screenshot of API IssueLinks[] and SubTasks[] tags are empty.

So in that case Is that true tool is not capable of getting Custom links by default?

This is the below Linking setup I have it in my Instance, not on the Specific project settings.

[Alexander-Hjelm]

Custom link types should be supported!

But judging from your screenshot in your last comment, there does not seem to be any custom link type named "Child" or "Parent" or similar, so I actually doubt that the default parent-child relationship is being overshadowed by some custom link type.

[muthu3758]

@Alexander-Hjelm Can you please tell us how to map if the links are available in rest api with some customfields, As you have seen the below image out of 4 links I could get 3 of them as a child, but i'm missing one link.(DITVM-764). Below is my config of link mapping.

"epic-link-field": "Parent Link", "sprint-field": "Sprint", "download-options": 7, "batch-size": 20, "log-level": "Info", "attachment-folder": "Attachments", "user-mapping-file": "users_ALL 3.txt", "base-area-path": "LinkMigrated", "base-iteration-path": "LinkMigrated", "ignore-failed-links": true, "process-template": "Agile", "link-map": { "link": [{ "source": "Epic", "target": "System.LinkTypes.Hierarchy-Reverse" }, { "source": "Parent", "target": "System.LinkTypes.Hierarchy-Reverse" }, { "source": "Child", "target": "System.LinkTypes.Hierarchy-Forward" }, { "source": "Blocks", "target": "System.LinkTypes.Dependency-Forward" }, { "source": "Cause", "target": "System.LinkTypes.Related" }, { "source": "Cloners", "target": "System.LinkTypes.Related" }, { "source": "Defect", "target": "System.LinkTypes.Dependency-Reverse" }, { "source": "Dependent", "target": "System.LinkTypes.Dependency-Forward" }, { "source": "Duplicate", "target": "System.LinkTypes.Duplicate-Forward" }, { "source": "Dependency", "target": "System.LinkTypes.Dependency-Forward" }, { "source": "Fix", "target": "System.LinkTypes.Related" }, { "source": "Hierarchy", "target": "System.LinkTypes.Hierarchy-Forward" }, { "source": "Implement", "target": "System.LinkTypes.Hierarchy-Forward" }, { "source": "Issue split", "target": "System.LinkTypes.Related" }, { "source": "Jira External", "target": "System.LinkTypes.Related" }, { "source": "Lead/Included", "target": "System.LinkTypes.Related" }, { "source": "Related", "target": "System.LinkTypes.Related" }, { "source": "Relates", "target": "System.LinkTypes.Related" }, { "source": "Sync", "target": "System.LinkTypes.Related" }, { "source": "Verify", "target": "System.LinkTypes.Related" }, { "source": "Tests", "target": "System.LinkTypes.Related" } ] },

Can you please tell us my config file is correct or need to do some modifications to get all the 4 links

[muthu3758]

Hi @Alexander-Hjelm,

Thanks for your response.

We have 2 projects which we need to migrate together, as you have seen in the screenshot.

Project 1 has top hierarchy configured as Parent Link and Project 1 has top hierarchy configured as Feature Link, because of which when we are migrating together we are not able to get all the links.

Questions:

1. Is there any way to have to more than one value for "epic-link-field"
2. Is there any way to have more than one epic-link field configuration.

[Alexander-Hjelm]

Ok! what is strange from your latest messages is that the linked issues seem to be stored as a custom field (customfield_13150) rather than an issuelink. Maybe that could have something to do with why you are not seeing them come across?

You can maybe try the Issue Field Data discovery endpoint and see if you can get any more information on customfield_13150. It would be interesting to see if you can find any clues to whether this field has been brought in by an extension or not. The endpoint looks something like this:

http://kelpie9:8081/rest/api/2/issue/createmeta?projectKeys=QA&issuetypeNames=Bug&expand=projects.issuetypes.fields

If this is the case, then I doubt that this tool will be able to support your requirement of migrating those links. This tool does not have the capability of migrating IssueField as Links. The best thing you could do is probably to map the field "customfield_13150" to a new Custom Field in ADO to ensure full traceability, then after the migration you can run some powershell automation or similar to set up the work item links based on the contents of that field.

Is there any way to have to more than one value for "epic-link-field", Is there any way to have more than one epic-link field configuration.

I don't believe so. The standard Epic Link field (which has now been superseded by the new Parent field in later versions of Jira Cloud) is the only field which tracks epic links.

[github-actions[bot]]

This issue is stale because it has been open for 25 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 5 days since being marked as stale.