You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem
Is there a way to define the format of the date? We have the problem that the date format does not cause any problems. The only exception we have is the closed date. The computers that have set e.g. for the region Germany get a wrong format at this point. Which then leads to the errors with Closed Date, which have already been described several times. Unfortunately, changing the language settings only leads to a temporary solution. We observe that longer imports reset after a certain period of time.
Date Format that cannot be processed
Expected format
Tool version
Version of the jira-azuredevops-migrator tool 3.0.115 and newer- we use
The text was updated successfully, but these errors were encountered:
@UweStein At the moment no, you will need to script a solution for yourself. It is doable to write something that hooks onto the migration process by editing the issues between the export and the import.
I'm marking this as a feature request to come back to in the future!
Describe the problem
Is there a way to define the format of the date? We have the problem that the date format does not cause any problems. The only exception we have is the closed date. The computers that have set e.g. for the region Germany get a wrong format at this point. Which then leads to the errors with Closed Date, which have already been described several times. Unfortunately, changing the language settings only leads to a temporary solution. We observe that longer imports reset after a certain period of time.
Date Format that cannot be processed
Expected format
Tool version
The text was updated successfully, but these errors were encountered: