Installer should create the windows service and config it for manual start up for JIRA used in "application mode"

Currently, if during the installation process Install JIRA as Service is ticked off, the installer config the JIRA Start menu shortcut to be liked to startup_bundled_jre.bat

The installer doesn't install JIRA as the service by default . Despite that most of JIRA are used in the "server mode".

If for whatever reason "inexperienced" windows JIRA administrator install JIRA in the "application" mode and accidentally closes the Tomcat terminal window, the user get surprised that it is impossible to access JIRA from the browser.
Moreover, he can't see the relationship between closing the terminal window and inaccessible JIRA.

The above automatically result in a new SAC case that follow simple script:

USER: My JIRA is down !!!!! help me now !!!! I see in my browser "page cannot be displayed"
SUPPORT: Have you done any thing to JIRA... How do you start up your JIRA? ... and etc.
USER: From the Start menu;
SUPPORT: By any chance, have you closed the black window?
USER: Yes! Because I don't like black windows and I don't need it !!!
SUPPORT: Well ... If you don't like the black window, perhaps you should install JIRA as a service.
....

so, all together we have a few bounces before this "simple issue" is addressed.

Additionally, when the issue is finally resolved, the user faces other issue related to the installer and outlined in JRA-15387.

In summary, I strongly believe that:

1. The installer should install the service by default.
2. The application mode should be optional. Additionally, it would still install the service but set it up to be started up manually and the Start menu item should be linked to start_service.bat. --Startup parameter passed to tomcat5.exe
3. If there are users who might need to start up JIRA in the terminal window they should be able to do it manually by calling startup_bundled_jre.bat. Perhaps some extra info in the doco page.