[INFRA-297] Redmine tickets missing during migration Created: 31/Jul/21 Updated: 05/Jul/23 |
|
| Status: | In Progress |
| Project: | Software Development Infrastructure |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | hassan | Assignee: | yuki.moritani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 1 | ||||||||
| Description |
|
It has been reported in the slack commissioning channel that at least one redmine ticket (internal redmine identifier 5905) has not been migrated to JIRA. Please investigate, check whether other tickets have not been migrated, and fix. |
| Comments |
| Comment by hassan [ 08/Oct/21 ] |
|
Missing tickets are due to only those redmine tickets that are either open, or previously migrated, are updated on the Jira side. In other words: closed tickets on the redmine side were ignored during the migration. Code is being updated to manage the other redmine status. During tests of that update, a problem was found with the privileges for the 'Redmine' Jira user. This has been fixed. Currently going through fixing some errors related to migrating newer tickets (connection dropouts, erroneous newlines in descriptions). These are being investigated. |
| Comment by hassan [ 22/Oct/21 ] |
|
All errors apart from connection dropouts have been fixed (mostly due to missing ticket attributes, or newlines in descriptions). Connection dropouts still need to be investigated. |
| Comment by yuki.moritani [ 05/Jul/23 ] |
|
While I were working on |