| Reporter |
Áxel Costas Pena (axl.coding@gmail.com)
|
|---|---|
| Created | Sep 3, 2013 12:18:15 AM |
| Updated | Sep 3, 2013 6:04:55 PM |
| Resolved | Sep 3, 2013 1:46:04 PM |
| Priority | Normal |
| Type | Usability Problem |
| State | As designed |
| Assignee | Unassigned |
| Subsystem | No subsystem |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
When you have youtrack installed locally on your computer, the service starts at a semi-working state. Then when you first visit your localhost, the service does some more work (CPU and memory usage grows) and then web sergice is totally active.
If you try to chat with youtrack during this non-fully active state, you get no response.
you must explicitly first open a web browser, then chat.
If you try to chat with youtrack during this non-fully active state, you get no response.
you must explicitly first open a web browser, then chat.