Summary

If you create your instance using a time zone that is not configured in Jira, the system will take this time zone as default, however, it will return an Internal Server Error when you try to access a project in the instance.

As an example, a customer created his instance using the time zone (GMT+4 Europe/Saratov) and Jira got this time zone as default to the system, however, this time zone is not available in Jira, there is just (GMT+4 Europe/Samara) in the system.

So, when you try to access any project in the instance, the system returns an Internal Server Error.

We believe that the same behavior could happen using another time zones that are not configured in Jira.

Steps to Reproduce

1. Change the time zone of your computer to (GMT+4 Europe/Saratov).
2. Create a new Jira instance.
3. Create a project and try to open it.
   You have the same behavior if you change the time zone to (GMT+4 Europe/Saratov) direct in the database.

Expected Results

The system should inform the user that time zone is not available in Jira and ask him to select a similar one.

The error could have a message informing that it's related to the time zone configuration and asking the user the change it.

Actual Results

Jira just return a Jira - Internal Server Error.

In the logs, you can find a message informing that this error is related to the time zone configuration.

Workaround

As a workaround, we changed the Time Zone to a similar one, in our example we change from (GMT+4 Europe/Saratov) to (GMT+4 Europe/Samara).