|
wojtek opened 2 years ago
|
||||||
|
This should be possible. |
||||||
|
|
Robin Shen changed fields 2 years ago
|
||||||
|
|
Robin Shen batch edited 2 years ago
|
||||||
|
|
Considering it's possible to have issues linking (https://code.onedev.io/projects/160/issues/697) and that YT import already parse that information (though it keeps it as text comment in the first issue imported) would it be possible to keep the issue link during the import as well? (should I create separate issue for it?) |
||||||
|
|
Yes, please file separate issue for that. |
||||||
|
|
|||||||
|
OneDev changed state to 'Closed' 2 years ago
|
||||||
|
|
State changed as code fixing the issue is committed |
||||||
|
|
OneDev changed state to 'Released' 2 years ago
|
||||||
|
|
State changed as build #2600 is successful |
(relates to https://code.onedev.io/projects/160/issues/323)
Is it possible to somehow retain original YT issue-id? We used it in commit messages so it would help backtrack the discussion after importing.