config.sh does not specify schema name when ran in text/headless mode

Summary

When using config.sh in text mode, which is the default on a headless server, it doesn't ask for schema name for PostgreSQL.

Expected Behavior

Ask for schema name when configuring a PostgreSQL database.

Actual Behavior

Schema name isn't specified in dbconfig.xml file.

In some cases, such as in JIRA 7.2.0 / Service Desk 3.2.0, this causes the problems reported in the below bug reports:

• [JSD-4192] Upgrade Task fails in PostgreSQL when installing Service Desk
• [JSD-4193] Creating a Service Desk project fails on PostgreSQL

On previous versions of JIRA, or in installations of JIRA 7.2.0 that do not have Service Desk, this has been found to only trigger ERROR-level log messages - similar to the one below.

2015-12-07 12:40:08,144 localhost-startStop-1 ERROR [c.a.j.appconsistency.db.PostgresSchemaConfigCheck] The schema name 'null' in your dbconfig.xml file contains upper case characters and JIRA only supports lower case schemas in POSTGRES.

Steps to Reproduce

1. Download any version of JIRA;
2. Run the config.sh script - located under <JIRA_INSTALL>/bin - in text mode;
   If you are on a headless server, this mode will be triggered automatically. If not, specify the -c flag in a command line when running the script;
3. Setup a connection to a PostgreSQL database;
4. Notice that the dbconfig.xml file - located under <JIRA_HOME>/ - will be missing the <schema-name> property, a required specification according to Connecting JIRA applications to PostgreSQL;

Workaround

There are three possible ways to prevent or manually correct this problem.

1. Run the config.sh utility in visual mode;
2. Use JIRA's Setup Wizard - shown upon first startup in the browser;
3. Manually specify <schema-name>name_of_schema</schema-name> just above the <jdbc-datasource> section on JIRA's dbconfig.xml file - located under <JIRA_HOME>/;