Content
View differences
Updated by Jens Ulferts over 10 years ago
**As an** OpenProject user
**I want to** edit work packages in the list view
**so that** I do not need to leave the page.
**Acceptance criteria**
- Work package attributes to be supported
- Textfield (e.g. Subject)
- Integer (story points)
- Floats (estimated time)
- Single select (e.g. Assignee)
- Bolean (e.g. custom field)
- Dates (e.g. start date)
- Auto refresh after saving a change
- Example: After changing the work package status to “closed” the work package is removed when filtering for open work packages
- The page (e.g. work packages 40 to 60) is kept.
- Mandatory fields
- Changing the type of the work packages (e.g. from bug to feature):
- Additional mandatory field may appear.
- Workflows
- There are workflows defined for each type and role. Example: only a developer may change the status of a bug to “tested”.
- Changing the type:
- Management of invalid status per type and role.
- Error handling and error messages
- Invalid value:
- Example: entering a float in an integer field
- Error handling: change can’t be saved. Fiedl is highlighted. There is an error message that helps the user to understand how to resolve the problem.
- Mandatory fields are not shown:
- Example: The type change requestt has a mandatory field “requester”. The column “requester” is hidden.
- Error handling: Saving the change does not work. There is an error message that helps the user to understand the reason. The column is added so the user can enter the mandatory field.
- Success messages
- Test automation
- Inline editing is triggered by clicking on the field (or pressing enter when having tabbed to the element). There is no icon next to the attribute as there currently is within the full screen/split screen. this is due to not having enough space in the table to show an inline edit trigger icon for every element. Inline editable elements will only receive a border.
- Fields that are linked right now, lose their links (e.g. subject, author, …). On the long run, we might add a tooltip upon hovering over an attribute allowing to present additional actions to the user.
**Visuals**
- http://clients.zzmedia.net/openproject/workpackages/list-view/editing/
**I want to** edit work packages in the list view
**so that** I do not need to leave the page.
**Acceptance criteria**
- Work package attributes to be supported
- Textfield (e.g. Subject)
- Integer (story points)
- Floats (estimated time)
- Single select (e.g. Assignee)
- Bolean (e.g. custom field)
- Dates (e.g. start date)
- Auto refresh after saving a change
- Example: After changing the work package status to “closed” the work package is removed when filtering for open work packages
- Mandatory fields
- Changing the type of the work packages (e.g. from bug to feature):
- Additional mandatory field may appear.
- Workflows
- There are workflows defined for each type and role. Example: only a developer may change the status of a bug to “tested”.
- Changing the type:
- Management of invalid status per type and role.
- Error handling and error messages
- Invalid value:
- Example: entering a float in an integer field
- Error handling: change can’t be saved. Fiedl is highlighted. There is an error message that helps the user to understand how to resolve the problem.
- Mandatory fields are not shown:
- Example: The type change requestt has a mandatory field “requester”. The column “requester” is hidden.
- Error handling: Saving the change does not work. There is an error message that helps the user to understand the reason. The column is added so the user can enter the mandatory field.
- Success messages
- Test automation
- Inline editing is triggered by clicking on the field (or pressing enter when having tabbed to the element). There is no icon next to the attribute as there currently is within the full screen/split screen. this is due to not having enough space in the table to show an inline edit trigger icon for every element. Inline editable elements will only receive a border.
- Fields that are linked right now, lose their links (e.g. subject, author, …). On the long run, we might add a tooltip upon hovering over an attribute allowing to present additional actions to the user.
**Visuals**
- http://clients.zzmedia.net/openproject/workpackages/list-view/editing/