Content
View differences
Updated by Christophe Bliard 5 days ago
**Pain points** Pain points:
* In the form configuration page, when there is a related work package table, it's impossible to know what it is without clicking it.
* what relation
* what filters
* what columns
* etc.
* it looks like this: <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/922707/content">
**Ideas** Ideas:
* Display the important configuration under it
* relation
* columns
* filters if any
* sort if not default
* baseline if any
* Something a bit like this:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/922713/content">
**Acceptance criteria**
Summary display
* Under each related work packages table in the form configuration page, a summary shows the table's configuration without opening the query editor.
* The summary appears in both editable and read-only views.
* The summary is a labelled list: label on the left, values on the right, aligned across rows.
* Only non-default configuration adds text, so the summary isn't overloaded.
* Rows that have several values (filters, sort criteria) show one value per line.
* The summary stays readable on narrow layouts (about 320px).
Content of the summary
* Relation type: shows the relation of the table (children, parent, blocks, etc.), using the same labels as the relation types.
* Columns: lists the columns selected.
* Filters: lists each filter on its own line, with a localized operator and localized values. Date ranges show open endpoints.
* Sort by: shown only if not the default. Each sort criterion is on its own line. Manual sort shows "Manual sort order" without "(Ascending)".
* Baseline: shown only if set.
* A relative baseline shows no fixed date (e.g. "Since yesterday at 08:00 AM").
* Two dates read "From <date time> to <date time>".
* A saved time is shown as saved. If its UTC offset differs from the viewer's, the offset is shown (e.g. "yesterday at 23:00 (UTC-04:00)").
* Highlighting: not shown.
Missing or inaccessible configuration
* A filter or value that is missing or that the user can't see appears as "Unavailable filter" or "Unavailable value" instead of being dropped.
* Labels respect visibility. For example, "Shared with" only lists principals the user can see.
Saving and refreshing
* Saving the query in the modal refreshes that table's summary immediately.
* The refresh doesn't discard unsaved section names or other unsaved changes elsewhere on the page.
* Reopening the editor shows the server's saved configuration, not defaults.
* A new table that is saved without a name gets a default name (the server's "Untitled", or a name like "Children relations"), so the configuration isn't lost.
Saved settings are kept when reopening the editor
* Sort: after a manual sort is saved, switching back to "Automatic" offers "ID" as the default, not "Manual sort order".
* Baseline: the saved baseline option is selected, not "-".
* Highlighted attributes: the saved selection is kept (e.g. only "Priority"). Only the selected attributes are highlighted in the table, instead of all of them.
* Baseline time inputs: choosing "-" in the baseline dropdown hides the time inputs.
Table configuration modal
* When opened from form configuration, the modal hides the Gantt chart and Display settings tabs instead of showing them disabled.
* Other table configuration modals still show these tabs, as before.
**Out of scope**
* Showing highlighting choices in the summary, maybe a later development
* Bug seen while validating/reviewing the PR: Row highlighting ("Entire row by", "No highlighting"), baseline and columns changes need a hard refresh to show in the table. This is a regression introduced in ##OP-20430, bug created and tracked in ##OP-20713.
* In the form configuration page, when there is a related work package table, it's impossible to know what it is without clicking it.
* what relation
* what filters
* what columns
* etc.
* it looks like this: <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/922707/content">
**Ideas**
* Display the important configuration under it
* relation
* columns
* filters if any
* sort if not default
* baseline if any
* Something a bit like this:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/922713/content">
**Acceptance criteria**
Summary display
* Under each related work packages table in the form configuration page, a summary shows the table's configuration without opening the query editor.
* The summary appears in both editable and read-only views.
* The summary is a labelled list: label on the left, values on the right, aligned across rows.
* Only non-default configuration adds text, so the summary isn't overloaded.
* Rows that have several values (filters, sort criteria) show one value per line.
* The summary stays readable on narrow layouts (about 320px).
Content of the summary
* Relation type: shows the relation of the table (children, parent, blocks, etc.), using the same labels as the relation types.
* Columns: lists the columns selected.
* Filters: lists each filter on its own line, with a localized operator and localized values. Date ranges show open endpoints.
* Sort by: shown only if not the default. Each sort criterion is on its own line. Manual sort shows "Manual sort order" without "(Ascending)".
* Baseline: shown only if set.
* A relative baseline shows no fixed date (e.g. "Since yesterday at 08:00 AM").
* Two dates read "From <date time> to <date time>".
* A saved time is shown as saved. If its UTC offset differs from the viewer's, the offset is shown (e.g. "yesterday at 23:00 (UTC-04:00)").
* Highlighting: not shown.
Missing or inaccessible configuration
* A filter or value that is missing or that the user can't see appears as "Unavailable filter" or "Unavailable value" instead of being dropped.
* Labels respect visibility. For example, "Shared with" only lists principals the user can see.
Saving and refreshing
* Saving the query in the modal refreshes that table's summary immediately.
* The refresh doesn't discard unsaved section names or other unsaved changes elsewhere on the page.
* Reopening the editor shows the server's saved configuration, not defaults.
* A new table that is saved without a name gets a default name (the server's "Untitled", or a name like "Children relations"), so the configuration isn't lost.
Saved settings are kept when reopening the editor
* Sort: after a manual sort is saved, switching back to "Automatic" offers "ID" as the default, not "Manual sort order".
* Baseline: the saved baseline option is selected, not "-".
* Highlighted attributes: the saved selection is kept (e.g. only "Priority"). Only the selected attributes are highlighted in the table, instead of all of them.
* Baseline time inputs: choosing "-" in the baseline dropdown hides the time inputs.
Table configuration modal
* When opened from form configuration, the modal hides the Gantt chart and Display settings tabs instead of showing them disabled.
* Other table configuration modals still show these tabs, as before.
**Out of scope**
* Showing highlighting choices in the summary, maybe a later development
* Bug seen while validating/reviewing the PR: Row highlighting ("Entire row by", "No highlighting"), baseline and columns changes need a hard refresh to show in the table. This is a regression introduced in ##OP-20430, bug created and tracked in ##OP-20713.