How to update an initial JQL in a Database without losing settings and text data?

[Christine Breault]

Hello,

We encountered an issue while managing a database in Atlassian. Here’s our use case:

We created a database and customized it by making several changes and adjusting settings. Later, we realized that our initial JQL was incomplete—it was missing the condition status != Closed, which caused closed Jira issues to appear.

When we tried to re-import the updated JQL, the process overwrote the database, erasing all the columns, settings, and other customizations we had worked on, including notes.

Does anyone know if there is a way to edit the initial JQL directly in the database without losing our previous work? Or is this even possible within the current system?

Thank you in advance for your insights!

[Marc - Devoteam · Accepted solution]

Hi @Christine Breault 

Welcome to the community.

Doing a quick check, no this is not an option.

If I change the import based on Jira via GIU and it tells me all existing content will be deleted

The only work around I see at the moment is to make a copy of the DB, using the copy structure and then import the data in this DB.

Also see, https://jira.atlassian.com/browse/CONFCLOUD-78799 

[Christine Breault]

Hi @Marc - Devoteam 

Thank you for the ticket link and the quick check!

For the moment, I'm using the filter as a workaround to hide closed and done statuses. This helps keep things manageable until a more permanent solution is available.

I appreciate the suggestion regarding the DB copy structure—I'll keep it in mind if needed.