Resq - dispatch issue #387

Closed
opened 2020-04-23 03:18:04 +00:00 by korina.cordero · 4 comments
korina.cordero commented 2020-04-23 03:18:04 +00:00 (Migrated from gitlab.com)
No description provided.
korina.cordero commented 2020-04-23 03:18:11 +00:00 (Migrated from gitlab.com)

mentioned in merge request !430

mentioned in merge request !430
korina.cordero commented 2020-04-23 03:18:11 +00:00 (Migrated from gitlab.com)

created merge request !430 to address this issue

created merge request !430 to address this issue
korina.cordero commented 2020-04-30 09:29:53 +00:00 (Migrated from gitlab.com)

closed

closed
korina.cordero commented 2020-04-30 09:31:04 +00:00 (Migrated from gitlab.com)

Upon investigation, the only way the JO could have been locked by Administrator was an Administrator opened it for editing but did not save any changes.

This was caused by an earlier bug but was fixed.

Upon investigation, the only way the JO could have been locked by Administrator was an Administrator opened it for editing but did not save any changes. This was caused by an earlier bug but was fixed.
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#387
No description provided.