Legacy JO Migration #202

Closed
opened 2019-04-05 06:09:58 +00:00 by jankstudio · 7 comments
jankstudio commented 2019-04-05 06:09:58 +00:00 (Migrated from gitlab.com)

Make sure the legacy jo migration scripts work properly.

Make sure the legacy jo migration scripts work properly.
jankstudio commented 2019-04-05 06:10:05 +00:00 (Migrated from gitlab.com)

assigned to @korina.cordero

assigned to @korina.cordero
korina.cordero commented 2019-04-05 09:23:25 +00:00 (Migrated from gitlab.com)

created merge request !236 to address this issue

created merge request !236 to address this issue
korina.cordero commented 2019-04-05 09:23:25 +00:00 (Migrated from gitlab.com)

mentioned in merge request !236

mentioned in merge request !236
korina.cordero commented 2019-04-09 09:24:01 +00:00 (Migrated from gitlab.com)

mentioned in commit e39289bb54

mentioned in commit e39289bb544412a99bfb2639d24386281d3d3ce6
korina.cordero commented 2019-04-09 09:42:03 +00:00 (Migrated from gitlab.com)

mentioned in commit a08e7b39eb

mentioned in commit a08e7b39eb2934a443eec0803ba8f1ecd028a92f
jankstudio commented 2019-04-09 14:52:04 +00:00 (Migrated from gitlab.com)

closed via merge request !236

closed via merge request !236
jankstudio commented 2019-04-09 14:52:04 +00:00 (Migrated from gitlab.com)

mentioned in commit 2a469dd469

mentioned in commit 2a469dd4692f2450b6ca6f5d24d498b8688922e5
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rgutierrez/resq#202
No description provided.