Lumper youtrack export problem

[piskacek1]

Logged to YT successfully Got error while exporting issues Exported issues: Users found in project

using YT6.5 and HTTPS

[agapoff]

Try to run the script with --debug option.

[agapoff]

I have added some debug information if the YT export fails. Please pull the changes and run the script again. We'll see why the exporting fails. Or you can try to query https://youtrack.test/rest/export/OPER/issues?max=10000 by yourself and see if you are able to get the XML.

[agapoff]

The problem is that your YT returns cookie YTSESSIONID, not JSESSIONID. And Lumper was not ready for that. I'va made some updates. Please pull the changes and try again.

[agapoff]

Lumper does not set the issue key - Jira sets it by itself. Jira takes the largest used number in project and increases it by one while adding a new issue. Lumper just gets this key from Jira and shows it. So try to drop the OPER project in Jira and recreate it. Thus Jira will start creating the issues from OPER-1.

[agapoff]

In order to set appropriate Resolutions for some States you should configure your Jira workflow accordingly. For example if you'd like the Status Done to set the Resolution as Done you should add a Post Function to the transition leading to Done status. The Post Function is called "Update issue field" - just configure it to set the Resolution field. If you'd like to set the Resolution depending on the YT issue status then you need to define the %StatusToResolution in Lumper's config file and add the Resolution field to the Jira project's screens (so Lumper will be able to edit Resolutions).

[agapoff]

Hard to say. You can set $exportTags to "false" in config.pl in order to skip creating the labels. Or you could investigate this issue further. Jira says that it is now aware of the 'labels' field. That's strange.

[agapoff]

You should read the documentation more carefully. The script has such arguments as --skip and --maxissues. For example if you'd like to export issue MYPROJECT-234, then just run the script as follows: ./migrate.pl --skip=233 --maxissues=1

[piskacek1]

I need to create the same number JIRE slip as import opera-34 and not a support-2348th It is possible using API?

export import log Will import issue OPER-34

{"id":"64583","key":"OPER-2348","self":" https://jira.test/rest/api/latest/issue/64583"} OPER-2348 Created issue OPER-2348

2016-05-30 8:46 GMT+02:00 Vitaly Agapov notifications@github.com:

You should read the documentation more carefully. The script has such arguments as --skip and --maxissues. For example if you'd like to export issue MYPROJECT-234, then just run the script as follows: ./migrate.pl --skip=233 --maxissues=1

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/agapoff/Lumper/issues/1#issuecomment-222422994, or mute the thread https://github.com/notifications/unsubscribe/ASqmy2yPHnFpCNjA3BFi8orQ_1vem_onks5qGofggaJpZM4ImidP .

[agapoff]

This is possible if key 34 in Jira is not busy. For example if Jira project has the maximum issue key OPER-15. Then Lumper will create OPER-34. But if Jira project has 2 thousand issues then it is impossible to create issue with already occupied issue key.

[piskacek1]

It is possible to modify it?

2016-05-30 10:12 GMT+02:00 Vitaly Agapov notifications@github.com:

This is possible if key 34 in Jira is not busy. For example if Jira project has the maximum issue key OPER-15. Then Lumper will create OPER-34. But if Jira project has 2 thousand issues then it is impossible to create issue with already occupied issue key.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/agapoff/Lumper/issues/1#issuecomment-222437471, or mute the thread https://github.com/notifications/unsubscribe/ASqmy2r0pPmMr9Q2nT12YbIdTRZyMX8uks5qGpvwgaJpZM4ImidP .

[agapoff]

Modify Jira?

[piskacek1]

Hi, my problem is issue id export and import issue key i need issue id = issue key.

Because I have the tickets issue id 2001 in YT and the next number is issue id 3001. Jira automatically uses the number 2002 on import its bad for me :(

2016-05-30 10:31 GMT+02:00 Vitaly Agapov notifications@github.com:

Modify Jira?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/agapoff/Lumper/issues/1#issuecomment-222441196, or mute the thread https://github.com/notifications/unsubscribe/ASqmy3PYYx9aJQYBWYUyN0ZNrE4rl6o2ks5qGqB0gaJpZM4ImidP .

[agapoff]

Got it. I've added a new parameter to config file named $maximumKeyGap. Just set it to some appropriate value larger than your maximum gap between YT's issue keys (maybe 2000 will be enough).

[piskacek1]

you are master its OK !!!!! thanks

[piskacek1]

Hi Vitaly I have one question ..link issue problem

• Depends on
• my mappink "Depend" => "Depend" but not creating link :( in imports

2016-05-30 13:22 GMT+02:00 Vitaly Agapov notifications@github.com:

Got it. I've added a new parameter to config file named $maximumKeyGap. Just set it to some appropriate value larger than your maximum gap between YT's issue keys (maybe 2000 will be enough).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/agapoff/Lumper/issues/1#issuecomment-222471492, or mute the thread https://github.com/notifications/unsubscribe/ASqmy859FTalmUBkdqJXa8hXjVkqqL3_ks5qGshtgaJpZM4ImidP .

[agapoff]

Maybe your Jira does not have link type "Depend". By default it realy doesn't. You can try to map Depend to Blocks or Relates.

[agapoff]

@patrikszo I have pushed a small fix that would help you to use it in 2020. Enjoy :)

[agapoff]

@patrikszo Are you sure that you have pulled the most recent change? Please run git log and check the latest commit.

[agapoff]

Most likely it redirects to https. Or just an API has changed in some way.