Changing the context manually breaks the conventions enforced in the iceScrum Server configuration so unfortunately this change will not work.
If you want to keep using iceScrum Server, I recommend that you revert your changes (both config.groovy and server.xml) and restart iceScrum Server. If iceScrum doesn’t start properly then check the content of C:UsersyourUserNameAppDataLocalKagilumiceScrum Servertomcatwebapps and if there are other files than icescrum.war and other folders than icescrum then you can remove them.
The only URL customization that will work in iceScrum Server is changing the application name from icescrum to another, e.g. scrum. To do so, you will only have to change the URL in iceScrum Server, (e.g. http://:8080/scrum) and the application takes care of changing the appropriate settings. Don’t change it manually in the config.groovy file.
The point of iceScrum Server is to allow using iceScrum without needing to install everything manually. This can be useful to evaluate iceScrum if you don’t have the time or the knowledge required to set up a proper Tomcat environment. However for actual enterprise / production needs, custom settings are required rather than enforced ones. In this case, as indicated in the documentation: https://www.icescrum.com/documentation/icescrum-server/#advanced-usage_1, a custom Tomcat installation will do a far better job than iceScrum Server.
Finally, please note that even in a regular Tomcat install, adding the Context like you did is not sufficient. Indeed, if the docBase refers to a .war in the Host appBase then you need to set autoDeploy=”false” deployOnStartup=”false” on the Host to prevent double deployment, as indicated in the Tomcat documentation.