Can jira issues remain synced after confluence database import?

Tamsin Purkis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 13, 2024

 

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? 

1 answer

0 votes
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 29, 2024

@Tamsin Purkis welcome to the Atlassian community 

Can you share some screenshots with steps that you are doing.   I want to try and recreate what you are doing to verify the limitation.

 

Tamsin Purkis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 9, 2024

Hi @Brant Schroeder ,

 

Sure! So essentially, I was trying to create a prioritisation matrix for myself taking advantage of this new confluence database.

I created/connected a database filtering on all Jira issues I am assigned to across various boards. I then manually added two columns to that database "Importance" and "Urgency" which are dropdown/select fields, which I then manually populate/select. Then I created a view, that filters on relevant issues (all those that are not in "complete" statuses) and then the idea was to make several views for the different priority quadrants. See filtering on "Important & Urgent". This all worked beautifully. 

But when I went back to it a week or so later, I determined that the database didn't have new Jira issues, which were created since the database was connected/created. And the only way I could find to "sync" it was to "Connect" the database again. And then it would override my custom structure (new fields and filters). 
Screenshot 2024-09-09 at 13.36.38.pngScreenshot 2024-09-09 at 13.36.57.pngScreenshot 2024-09-09 at 13.37.07.pngScreenshot 2024-09-09 at 13.38.09.png

Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 9, 2024

@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 

Like Tamsin Purkis likes this
Daniel Wilde September 20, 2024

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.

image.png

schettino
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 27, 2024

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.

Like Daniel Wilde likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events