Dashboard Assistant uses Jira to store the data so that
-
there is no need to store the data in external servers
-
the discussion can be easily searched within Jira
-
it is easy to enhance or finetune by making configuration changes within Jira itself
How it works
-
For each comment gadget, the app will create a new Team-managed Jira project automatically.
-
The project name is in the format COMMENT_GADGET_<DASHBOARD ID>
-
The project key is in the format CG_<DASHBOARD_ID>
Example, if the dashboard is available at https://xyz.atlassian.net/jira/dashboards/12345, the project will be at https://xyz.atlassian.net/browse/CG_12345 with the project name COMMENT_GADGET_12345
-
A new Jira issue is created for each new reporting period (set by Schedule Frequency )
-
All the discussions for that period are added as comments for that Jira issue
-
The notifications are handled via the issue watcher list, so Jira will handle the notifications on behalf of the app when new comments are added
-
There is a scheduler which will be responsible for adding new Jira issues in the associated Jira projects to trigger a new round of review
Some user visible data are stored within the Jira issues so that power users can also access/modify with ease.
Users can also modify the access control via Jira in-built project settings.
Those backend data which should not be modified by end users are stored using Forge hosted storage.