Actions
action #94024
openMTUI unable to recover from failure to connect to the refhost
Start date:
2021-06-15
Due date:
% Done:
0%
Estimated time:
Updated by okurz over 3 years ago
I assume a valid workaround is to quit MTUI and start again? Can we keep that as a "known issue" with workaround and then deprioritize the task for now?
Updated by okurz over 3 years ago
- Description updated (diff)
- Assignee deleted (
osukup) - Priority changed from Normal to Low
- Target version changed from Ready to future
Added the workaround to the description and unscheduling from our backlog.
Actions