Confluence Database Refresh - JQL

[Terry Meissner]

Good morning community,

Please note, the following is in relation to the 'Databases' functionality within Confluence...not the backend DB.

When setting up a Database in Confluence and importing data using a JQL query, the only way I can see to refresh the data is to re-import using the same query which unfortunately blows away the existing Database structure and views.

Is there a way (or is in in the roadmap) where the JQL query can be retained and the database be refreshed based on said query whilst maintaining the table structure (i.e. same as when inserting a Jira Query macro into a Confluence page)?

An example of this as a use case where I want to display a list of Epics with two additional coulmns of RAG and Comments. If more Epics are created within the project, I want the database to automatically add another entry with the additional Epic (i.e. re-run the query) and maintain the RAG and Comments columns.

I can't see this to be done using automation either.

Thanks for your help.

[Giorgos Vasileiou]

I have exactly the same use case as Terry and I'm currently blocked by the fact that there's no refresh of data. 

[Smadar Ben David]

I agree

[Cole Jancsar]

Do you know if that functionality is coming? Without sync-link to Jira it makes databases fairly useless.

[marc -Collabello--Phase Locked-]

As far as I know Atlassian has not committed to building this.

[Kristen]

This is a HUGE miss on Atlassian's part.  Why have a database, if it can't take in new entires based on the JQL?  Completely Useless! 

[Michael Yope]

I'm also unable to really use this tool without the ability for the database to do a refresh/sync based on the original import JQL from JIRA. Love what I see so far, just need this to use it. Hopefully someday!

[marc -Collabello--Phase Locked-]

Unfortunately refreshing data is currently not supported in Confluence databases.

[Kristen]

Then it isn't a database, but merely a grid with information. 

[Tim Dadd]

Not using JQL but using simple CSV import.  There seems to be a number of basic flaws in this whole database design that makes it unusable.

First there is an assumption that the first field is a unique ID to find a record.  OK I can handle that - so based upon that assumption that's been made I have the following questions:

1) Why can't you re-import with an updated CSV file and the unique ID field is used to update the existing record?  As it is merge with more than 10 records never finishes.

2) If the /embed command is used which assumes the first column is a unique ID then why is the ID field selected not shown on the view?  Why just the database name and the word Confluence Database?

2A) Why is there an option to select a field to show but that doesn't actually have a hyperlink to all the fields or show preview option?

3) Instead of selecting a single field to show, wouldn't it be better to select a view to show a set of fields?

4) Has anyone in Atlassian actually tried using the database import feature for anything useful?  Please tell me the use cases of this database that make sense.  If you add some sort of import feature please provide the use cases that you think it can be used for.  For instance one time upload of data.