PostgreSQL connectivity loss in Jira DC plugin

[Mohan Raj]

Hi all,
There is an issue with a plugin in Jira Data Center, specifically designed for deleting issues. This plugin is intended to conduct a validation check on the database prior to initiating deletion. However, despite the inclusion of a validation query in the dbconfig.xml file, the plugin seems to be losing its connectivity to the database.

"org.ofbiz.core.entity.GenericDataSourceException: SQL Exception occurred on commit (Connection is null.)
at org.ofbiz.core.entity.jdbc.SQLProcessor.commit(SQLProcessor.java:197)
at org.ofbiz.core.entity.jdbc.SQLProcessor.smartCommit(SQLProcessor.java:312)
at org.ofbiz.core.entity.jdbc.SQLProcessor.close(SQLProcessor.java:237) "

please help us to resolve this issue.

Thanks,
Mohan Raj

[Neel]

I realise this question was asked a while ago, but I wanted to provide an answer for anyone who comes across this with a similar query.

Unfortunately, there is also no native "smart check" or built-in conflict detection in JSM DC that would prevent a change owner from scheduling a change at the same date/time as an existing one.

However, here are some workarounds you can consider:

1. Workflow Validator with ScriptRunner (recommended)

If you have ScriptRunner for Jira | Atlassian Marketplace installed, you can add a custom validator on the workflow transition (e.g., when moving a change request to "Scheduled" or "Awaiting Implementation") that runs a JQL query like:

project = <YOUR_PROJECT> AND issuetype = "Change Request" AND "Planned Start Date" <= <current_issue_planned_end> AND "Planned End Date" >= <current_issue_planned_start> AND issue != <current_issue>

If this returns results, the validator blocks the transition and shows a message like "Another change is already scheduled during this window."

2. Automation for Jira (DC)

You can create an automation rule triggered on field change (when "Planned Start Date" or "Planned End Date" is updated) that:

• Runs a JQL lookup for overlapping changes

• Adds a comment or flag to the issue warning about the conflict

• Optionally transitions it back or notifies the change manager

This won't prevent the assignment but will alert the team immediately.

Hope that helps!