Content
View differences
Updated by Jens Ulferts over 10 years ago
**Acceptance criteria**
- inline edit (triggered by click) for a work package’s subject
- errors are displayed via the box at the top (default)
- The input field has a hidden label so that it is accessible
**Open**
- Can we use the exact same UI for editing the field?
- Showing the trigger via a pen icon to the right will take away some precious space all the time. It might be benefical to move the icon to where the save/cancel buttons are when one is inside an inplace edit field. If we change it, we should change it everywhere.
- Subjects can be quite long (255 characters). How is the subject input field to be displayed when the space does not suffice?
- If the user filters for subject, this might lead to the work package the user currently edits to no longer be part of the query result. If we remove it from the results right away (as specified by \#18404) this will make it very hard for the user to fix a typo or other errors as the work package is removed once he presses the save key.
- inline edit (triggered by click) for a work package’s subject
- errors are displayed via the box at the top (default)
- The input field has a hidden label so that it is accessible
**Open**
- Can we use the exact same UI for editing the field?
- Showing the trigger via a pen icon to the right will take away some precious space all the time. It might be benefical to move the icon to where the save/cancel buttons are when one is inside an inplace edit field. If we change it, we should change it everywhere.
- Subjects can be quite long (255 characters). How is the subject input field to be displayed when the space does not suffice?
- If the user filters for subject, this might lead to the work package the user currently edits to no longer be part of the query result. If we remove it from the results right away (as specified by \#18404) this will make it very hard for the user to fix a typo or other errors as the work package is removed once he presses the save key.