Gitlab v3 -> v4 api possible solution

[thomas955]

Hi,

after digging a bit into, i discovered to change v3 api namespace to v4 only is not enough. (#31)
I also had to change the return from get_id former "id". "id" is the global issue ID and not the project related "iid". So this "id" and cannot be used if any issue was created in gitlab before. Otherwise it will raise an exception cause, the issue_url["id"] is pointing to the global id number and not to the corresponding project issue id.

How do i can create a pull request directly? I dont want to fork this project again.

[scambra]

pull requests needs to fork, you can edit file in github to send pull request and it will create fork, or you can fork, clone, push to new branch and then create pull request

[thomas955]

Ok ill do so.
I currently try to fix --keep-id also, maybe will take some more time.

[scambra]

You have access, so you can push without sending pull request now

[sdinot]

I am facing this issue. Is there any news about it?

[thomas955]

#35

Im currently doing my migration too, and still testing if all things work like expected.
This pull request should help you, nearly the same things i fixed in my version.

[sdinot]

Thanks a lot. The code provided by the pull request almost works (issues are created), but the users match fails. I just opened an issue about it #36.

[sdinot]

Finally, the code provided in the pull request works fine. The reason of the fail was a wrong Redmine API key as I explained it in #36.

[flashpixx]

Is there any timeline to integrate the pull request into the current master branch?

[nelo-digitalagentur]

+1

[AdamN1]

Please check master branch it should work with gitlab api v4

[HontoNoRoger]

Can probably be closed as well after #46 is done?
This should fix the problem for people coming here and installing the tool with pip.