Unable to publish automation rules in Jira due to Customised DB view
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Unable to publish/enable automation rules in Jira due to Customised DB view.
Environment
Any Jira Data Center version
Diagnosis
The Jira users are getting the below exception while enabling/publishing an automation rule in Jira.
Cause
The issue could be caused due to the custom views defined in the Database. The below SQL exception will be logged in the Jira application's startup logs -
1
2
3
4
5
6
7
8
9
10
11
12
13
2024-03-04 09:26:21,797+0000 active-objects-init-JiraTenantImpl{id='system'}-0 WARN anonymous [c.a.activeobjects.osgi.TenantAwareActiveObjects] bundle [com.atlassian.jira.plugin.automation.for-jira] failed to create ActiveObjects
com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:PostgreSQL
- version:12.14
- minor version:14
- major version:12
Driver:
- name:PostgreSQL JDBC Driver
- version:42.6.0
org.postgresql.util.PSQLException: ERROR: cannot alter type of a column used by a view or rule
Detail: rule _RETURN on view vapp_automation_configs depends on column "ID"Solution
Involve DBA and validate the DB view.
If the view is not being used / is irrelevant, drop the view using the below command. In this case, the view name is "vapp_automation_configs"
1DROP VIEW vapp_automation_configs;⚠️ We strongly recommend taking a backup of the database before dropping the view.
Was this helpful?