Similar to @Terry Meissner , I'd love to see the databases have an option to run a scheduled sync with JIRA based on the JQL or Basic filters used to initially set up the database.
I was looking into using databases and confluence pages to create a dashboard tracking rollout JIRA issues. Its an awesome tool, but is effectively something that I can't use right now with the non syncing nature of the tables to pull in the newly created tickets automatically. I'd have to either re-run the import again and lose the custom column data I added post import, or add in the new tickets one by one. Neither of which are scalable across a large amount of projects.
This would be the perfect tool to get around the Filter widget macro in confluence otherwise to add in extra data to the core JIRA information. Hopefully this is on the roadmap and we'll see it soon.
In the meantime, I've gone with a spreedsheet and the JIRA Cloud for Sheets plug in to pull in the data with synchronizing capability.
Ok, I don't get it. I see all of the above comments regarding how wonderful this feature is and so far it isn't living up to my expectations. I tried creating a database using a JQL search, added a field to it hot OK and I have a blank database telling me to add issues. This is probably the third or fourth time I've tried to use this feature and it hasn't ever worked or provided something of value.
If anybody can point me to some good information on how to use it I would appreciate it. I will look through what is presented above but I'm not going to hold my breath.
28 comments