Thanks for your kindness. I will investigate to see if I can prioritize this feature.

YouTrack is a much sophisticated product for issue management. Some rough considerations when importing from it:

Custom Fields

YouTrack custom field can use different value sets for different projects, and can select to show/hide per project. When migrated to OneDev, project specific settings will be lost

Agile Boards

YouTrack board can contain issues from multiple projects. It works by linking issues to boards manually. A single column can have multiple identity values. Migrating this to OneDev will result in many functionality loss, and I'd like to leave it behind.

Issues

YouTrack has issue linking concept, while OneDev does not. When migrated, a note for issue linking will be added in issue description.

Issue Queries

This is very YouTrack specific and will not be migrated.

What do you think?

Thank you very much for looking into this.

What we really need is just historic data from YouTrack. We have a separate project for each customer and long history of tasks/issues for each project/customer. And it is important for us to preserve during migration onto OneDev. The most important is issue subject, description and all the comments.

We do not need migrating agile boards at all. We do not need to migrate issue queries either.

Issues linking is very useful feature and I hope we can have this in OneDev some day. For now, your suggested solution to add a note about issue linking would be sufficient.

I've filed a feature request for issue linking. I can develop the plugin to help importing issue history from YouTrack. Will send you an email for the details.

Importing issues from YouTrack seems to be working very well. I was able to successfully import project with over 1,250 issues. Checked a couple of them and they all have comments as expected.

However, there is one issue with the import.

At the moment the import is only possible to a new project. That is, during the issues import from YouTrack a new project is created in 1dev. It is not possible to import issues into existing project.

However, for us, the case is that we have code repository on GitHub with some public support issues and the actual project tracking for our team work issues is on YouTrack. So, we want to import project from GitHub code+issues and then import issues from YouTrack to the same project.

Could you please make it possible to import YouTrack issues into existing project?

Please add possibility to import issues from YouTrack into existing project in 1dev.

This can be done. However issue numbers might be changing since there will be conflicts for imported issue numbers and existing issue numbers.

Build #1602 now is able to import GitHub/YouTrack issues into existing projects.

Thank you for adding this.

I have just pulled the most recent Docker image from hub.Docker.com, built about 13h ago and it is still version 4.6.0 and it does not have this option.

Could you please post version 4.6.1 on Docker hub?

I mean, I pulled the "latest" which points on Docker.com to 4.6.1 but after running it, it still shows 1dev version number 4.6.0 and the option to import issues is not available.

I just checked and the latest does point to 4.6.1. Please make sure you are using latest tag.

Yes, it does, as I said. but when you install it, the ver number at the bottom still shows Ver. 4.6.0 and functionality is not available.

Please modify tag from "latest" to "4.6.1." to see if it works.

Just installed docker image tagged as 4.6.1 and still the same problem. Ver number at the bottom shows 4.6.0 and functionality not available.

Please change to a new mounting folder to see if it works:

docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd)/new-onedev:/opt/onedev -p 6610:6610 -p 6611:6611 1dev/server:4.6.1

If it works, please switch to your previous mounting folder, start it and then show me the start up log.

Thank you. I did it all and now it works.

For the system in new-onedev folder the version number displayed correctly: 4.6.1.

Then, I stopped this and restarted again, the previous installation. This time, it also showed me the correct version and also the functionality button shows as well. I wonder, if this is some kind of caching problem....

This is odd. If it happens next time, please:

1. Make sure currently running OneDev is stopped completely
2. Start it from console (instead of running as daemon), and show me the start up log

Ok, thank you for your help.