Getting Error: "An error occurred while trying to delete event jira" While trying to edit/delete event in Team Calendar

Platform Notice: Data Center Only - This article only applies to Atlassian apps 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

Problem

When trying to delete or edit an event in Team Calendar, the following error is thrown in the UI:

(Auto-migrated image: description temporarily unavailable)

Diagnosis

Environment

  • This calendar was recently imported from a Confluence Cloud instance

  • Newly created event or events from newly created Calendar does not exhibit this issue

Cause

It's a variation of this bug, (TEAMCAL-1596 - NPE when saving the modification on the event) where having a / anywhere in the UID section of your calendars causes an issue. In this case, it's likely that there's a string of /jira in the UID section.

In order to confirm this, run the following SQL query to confirm:

SQL Query: MySQL/PostgreSQL

select "VEVENT_UID" from "AO_950DC3_TC_EVENTS" where "VEVENT_UID" like '%/jira';

Should the SQL query above return some results, please follow the workaround below

Solution

Workaround

Perform a "Search and Replace" SQL query to remove the /jira from the UID

UPDATE "AO_950DC3_TC_EVENTS" SET "VEVENT_UID" = REPLACE("VEVENT_UID",'/jira','');

Warning: Backup your database before proceeding.

Before running any SQL in this article, create a full backup of your Jira database. This is a database-level operation with no undo other than restoring from backup. Only proceed if you're comfortable running SQL directly against the Jira database, and test on a staging or cloned environment first, wherever possible.

Updated on September 26, 2025

Still need help?

The Atlassian Community is here for you.