Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AreaPath migration #66

Closed
XVII opened this issue Aug 2, 2019 · 3 comments
Closed

AreaPath migration #66

XVII opened this issue Aug 2, 2019 · 3 comments

Comments

@XVII
Copy link
Contributor

XVII commented Aug 2, 2019

Is there any support/sample configuration for migrating Jira Components => DevOps Area Path?

@quadmig
Copy link

quadmig commented Aug 21, 2019

I don't know if this helps, but I coded mine in the config to use another field.
{
"source": "components",
"target": "Custom.MigratedComponent"
},

That said, you should be able to something like
{
"source": "components",
"target": "System.AreaPath"
},

That should work although I can't test it now because it will mess up my migration in progress.

@XVII
Copy link
Contributor Author

XVII commented Aug 21, 2019

Ah, I tried

      {
        "source": "component",
        "target": "System.AreaPath"
      },

will try components :)

@XVII
Copy link
Contributor Author

XVII commented Aug 22, 2019

The following does work and includes the new area path. I was able to include some mapping logic to take into account the area path.

      {
        "source": "components",
        "target": "System.AreaPath",
        "mapping": {
          "values": [
            {
              "source": "Jira Component Name",
              "target": "Project\\Area Path\\Component Name"
            }
          ]
        }
      },

@XVII XVII closed this as completed Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants