A user can configure the view of object tables and define the following settings:
number of rows to show (default: 10)
object fields to show (default: summary fields)
These settings are currently not persisted. Even if a user navigates in the UI, the latest settings were not restored, if the user comes back to a site.
To improve the usability of object tables, we should persist these settings in the following ways:
automatically store the current settings per user and restore these settings when the user comes back to the page
add a reset functionality to restore the default settings
allow the persisting of multiple settings and let the user switch between these settings
Also changes in object type definitions needs to be handled.
The menu looks different than other navigation elements in DATAGERRY.
current version looks like:
The following improvements wood be nice:
adding new filters:
put the input field at the top of the menu and the save button as a small black/grey icon beside the input box
use the trash icon for the removing filter action an put it at the end of the filter
use the same font size /style/colors like in the top navigation bar
for me the clear button is very dangerous, as all filters can be deleted with on click. I simply would remove that button
“Reset” simply means “show the default summary buttons”? I would show that as a simple filter element with name “Default“ that cannot be deleted.
Tested successfully, pefect!
Needs to be integrated
when opening the settings an endless dropdown of empty configs show up. Can you please take a look at it?
Changed the Jira Workflow from DATAGERRY -> DATAGERRY 2.0