| Usecase | Description | Questions to Clarify | Answers |
|---|
| 1 | Connect to the datasource | Users configure the connection from the app to the external datasource. | What type of datasource is it? (SQL, Posgres, Oracle, MSSQL) Which source will be the primary? Database or App?
| Support all of them Suggest “Database” to be the main source
|
| 2 | Display data from the datasource | Data from the datasource is displayed in tables within the app. | Is there a limit to the number of records displayed? How to handle with big data from database? JQL search will still work as expected?
| No Still run, just take more time to synchonize. Yes
|
| 3 | Update data in the app | Users can update data in the app, and the changes are reflected in the external datasource. | How should conflicts between app and datasource data be resolved? How can we detect the data as conflict? Should users be notified about unsynced data? Should a warning display for stale data? What happen when the connection is lost? Can still user be able to use that grid? How should conflicts be handled if datasource changes during editing? If the data is add from UI but the database is offline, will the data from app be save or throw error?
| If the data is not the same, the grid will still show the data (which is saved from Jira database). But in this case, user will not know if the data is not synchonize. - We need to find a way to let user know if the data is not the same…
When the connection is lost, the user can still use the grid, but the data will no longer sync with the database. The action that is saved last will determine the final data value. Throw error → tested on Data Mirror TGNG
|
| 4 | Update data in the datasource | Updates made in the datasource are synchronized back to the app. | Is real-time synchronization required, or will periodic updates suffice, or when user reload the grid? How will the app handle partial updates or missing fields? What happens if a record is updated in the app and datasource simultaneously? Should updates from the datasource queue when the user is offline and apply later?
| Realtime is needed, and user can synchonize again when click on a button “Re-synchonize”. Follow TGE, with the column is not the same type or missing, it will be ignored. The action that is saved last will determine the final data value. - A background function to run the synchonize is an option, but not sure if we should support this or not…
|
| 5 | Synchronize datasource schema | Automatically detect and adapt to the structure (schema) of the datasource for compatibility. | Should the schema be fetched dynamically or provided manually? How will changes in the datasource schema be handled? Should users be notified if new columns or tables are added to the datasource? How to handle if app and database have different restriction? Like allow null value, different in data type?
| No, refect to TGE User will need to synchonize manually Showing error when user saves data in the app
|
| 6 | Error handling and notifications | Users are informed of connection issues, synchronization errors, or invalid data. | What types of errors should trigger notifications? Should there be retry mechanisms for failed synchonize or connections? What level of detail should be provided in error messages?
| - Errors related to the table structure not the same, synchonize action failed
Yes, we should provide a button for users to proactively synchronize. However, we will notify them that all current data will be overwritten by the data from the database. Since the synchronization process might take some time, we need to warn users not to interact with the grid during this period. Additionally, consider providing a progress indicator to enhance the user experience. - Show them clearly which column type is preventing user from saving the data.
|
| 7 | Security and access control | Ensure that only authorized users can access and update data. | What roles/permissions are needed for accessing and updating data? Is encryption required for data in transit and at rest? Should users' actions (e.g., edits, deletions) be restricted based on their roles?
| User that can edit grid can do this, or admin can use the Grid Behaviour to restrict No, reflect on TGE The same as #1 answer
|
| 8 | Logging and audit trail | Log all actions related to data synchronization for troubleshooting and auditing purposes. | What details should be logged (e.g., timestamp, user, action)? Who should have access to the logs? Should there be a UI for viewing logs within the app?
| - Something the same as Grid History should be logged.
Admin Yes, but in the Grid Configuration → Data Mirror section for only admin
|
| 9 | Data transformation and mapping | Define how the datasource data is mapped to the app's data structure. | What if the column type is being changed from one side, what should be happen? How will unsupported or invalid data be handled?
| With TGE, it does not support changing column types and reflecting those changes in the database and vice versa, if the changes is being processed, the data in table will be broken and does not display the data. TGNG should have the same restriction. Ignore and only work with correct data
|