Automation to calculate Risk Priority is not working

[Shannon Bradley]

I have set up an automation so that when:

Risk Impact value > 0

Risk Probability > 0

Then edit Priority to be equal to: {{#=}}{{issue.Risk_Impact_Value.value}} * {{issue.Risk_Probability_Value.value}}{{/}}

This gets errors

can someone help me figure out what is wrong with my automation?

Thank you!

[Andy Heinzer]

It looks like there is a problem with the database Jira is trying to use on startup.  The logs have errors such as this:

2018-11-10 17:24:51,645 JIRA-Bootstrap ERROR      [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, user_key, lower_user_name FROM jira.app_user (ERROR: schema "jira" does not exist
  Position: 43)

This would tend to indicate that the schema of the database does not match the value set for that schema in the dbconfig.xml file.   

In addition to this problem I also noticed that you're using Jira 7.12.3 with a postgres 9.2.x database:

2018-11-10 17:24:50,209 JIRA-Bootstrap INFO      [o.o.c.entity.jdbc.DatabaseUtil] Database Product Name is PostgreSQL
2018-11-10 17:24:50,209 JIRA-Bootstrap INFO      [o.o.c.entity.jdbc.DatabaseUtil] Database Product Version is 9.2.24

The problem here could also be that this latest version of Jira no longer supports postgres 9.2 or earlier database versions.  You can find this information in Jira 7.12.x supported platforms documentation.

I would recommend that you use a supported database type/version and then create a new database per the steps in Connecting Jira applications to PostgreSQL.  Which assumes you will use a postgres version between 9.3.x - 9.6.x.   By following these steps, you should then be able to correct both problems and get onto a supported platform.

[Tom Lister]

Hi @[deleted]

It's likely the default JIRA install will be using port 8080 so can't start if bitbucket is already using it.

The installer should give you options to choose ports to use.

The <jira-install>/conf/server.xml can be edited to change the ports used.

If that doesn't work can you post the whole log somewheree?

[Deleted user]

I set the Jira port to 8081 and the control port to 8006 when installing.

I tried accessing it directly on the server and I get:

# wget -O- localhost:8081
--2018-11-10 17:25:47-- http://localhost:8081/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8081... connected.
HTTP request sent, awaiting response... 302
Location: /secure/errors.jsp [following]
--2018-11-10 17:25:47-- http://localhost:8081/secure/errors.jsp
Reusing existing connection to [localhost]:8081.
HTTP request sent, awaiting response... 503
2018-11-10 17:25:47 ERROR 503: (no description).

I have uploaded the logs of a fresh Jira installation here.

[Deleted user]

I have installed Jira on port 8081 and conrol port 8006.

All the logs generated after installation and initial start are here.