Content
View differences
Updated by Jens Ulferts over 10 years ago
**Acceptance criteria**
- Changes in the work package table need to be reflected in the work packages table (which is the result of a query). e.g. when changing the status to closed, while filtering the WP table by status “open”, the work package is no longer a valid filter result. Editing can happen:
- When editing within the table
- When editing in split screen
- When creating in the table
- When creating in split screen
**Open**
- \#\#18404 states to update the table right away (Quote: “Example: After changing the work package status to ”closed" the work package is removed when filtering for open work packages"). This will make it very hard to correct errors one might have made. This will also make it hard to change additional fields when one has forgotten to edit one field. Additionally, this will result in poor user feedback. I have edited a field, and now the row is gone. I have the success message but I would be wondering if I have done anything wrong. This will also be the case when I create a work package not matching the filter criteria. One technical problem adding to this is that we would have to know on which page the work package is now after creation/editing. So while the work package might fit the filter criteria, it might just not be on the current page.
- 1\. Proposal: Have a dedicated section of the table where all the work packages, that no longer match or are created and do not match are placed.
- 2\. Proposal: Keep the work packages in the table, update the values and mark the non matching values or rows.
- Changes in the work package table need to be reflected in the work packages table (which is the result of a query). e.g. when changing the status to closed, while filtering the WP table by status “open”, the work package is no longer a valid filter result. Editing can happen:
- When editing within the table
- When editing in split screen
- When creating in the table
- When creating in split screen
**Open**
- \#\#18404 states to update the table right away (Quote: “Example: After changing the work package status to ”closed" the work package is removed when filtering for open work packages"). This will make it very hard to correct errors one might have made. This will also make it hard to change additional fields when one has forgotten to edit one field. Additionally, this will result in poor user feedback. I have edited a field, and now the row is gone. I have the success message but I would be wondering if I have done anything wrong. This will also be the case when I create a work package not matching the filter criteria. One technical problem adding to this is that we would have to know on which page the work package is now after creation/editing. So while the work package might fit the filter criteria, it might just not be on the current page.
- 1\. Proposal: Have a dedicated section of the table where all the work packages, that no longer match or are created and do not match are placed.
- 2\. Proposal: Keep the work packages in the table, update the values and mark the non matching values or rows.