Can jira issues remain synced after confluence database import?

Question

Love this new confluence database feature and already starting to use it to organise my work!

I just wanted to check, I have imported jira issues with particular jql applied, then I added more columns in the database that are outside of the fields I want in jira to be able to apply specific filters/grouping for specific views I want. This works great!

But going back to the table a week later, although the issues that were already there, are synchronised in terms of their status and other jira detail fields, I see no new jira issues (that would be returned with the same jql) that have been added since.

It seems I have to "re-import" from jira to get my most recent relevant issues, and when doing so, I lose the new columns and views I created / populated.

Is there no way to "re-sync"/ "re-import" without losing my current setup each time?

schettino · Answer

The issue has been reported here, but its status is set to Long Term Backlog because not enough users have upvoted the ticket—as I was told by Atlassian Support.

Daniel W_ · Answer

hi,

I'm struggline with the same problem and I'm wondering why nobody was reporting it yet. Some users just complain about losing the structure by importing again from jira.

I wanted to report it but unfortunately I am not able to create a ticket in project CONFCLOUD.

Brant Schroeder · Answer

@Tamsin Purkis After playing with the import functionality I am having the same issue.  The import overwrites everything and I loose the custom columns that I added.  It looks like this is a limitation of the product.  I would suggest submitting a enhancement request here: https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=10440