Hi Dmitri, > To be on the safe side the tool should not assume that person who is > configuring it has access to the machine the instance is running in. > Assumption that someone can restart the instance manully is wrong. > This is it.
I am sorry if I have upset you - I just wanted to suggest a workaround. A different workaround I just tested successfully is to go to the Agilo General preference pane and click save there (no change in settings required). This forces the configuration to be reloaded and should work around this bug. > No. Please report if that solves your problem. The steps you took to configure this where quite correct, so I really guess that this should fix the behavior you are seeing. In the meantime I have entered this bug report to track fixing of this issue: <https://dev.agile42.com/ticket/930> Best Regards, Martin -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum ----- You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en
