Content
View differences
Updated by Parimal Satyal almost 2 years ago
**As a** project manager,
**I want to** manually set the % complete status of a work packge
**so that** I have more influence in what I communicate to my stakeholder
**As a** project member (eg. a developer),
**I want to** be able to quickly update how much progress I think I've made on a Feature or a User story
**So that** my team (including my manager) has a overall perspective on progress on an Epic or a Project in general
### **Context**
This feature is a response to user feedback on breaking changes to the way OpenProject handles progress reporting starting with version 14.0: ###40749
In version 14.x, in the default Work-based progress calculation mode, the _**% complete**_ field requires _Work_ (and consequently, _Remaining work_). This change makes made progress reporting possibly more grounded in reality but also introduced complexity:
* Progress cannot be manually input (like it was possible in the past) without also inputing a value for work.
* Progress is tied to the notion of _work done_ (or _earned value_); for users who want to update progress without also estimating work and remaining work in units of time, the only other option is to use _Status-based mode_, which is also not always ideal as certain users prefer decoupling status from % complete values.
A significant number of users were dissatisfied with the breaking change we introduced and the inability to manually enter progress. The found the new approach rigid and unadapted to the way they wanted to work.
**This feature seeks to make it possible again for users to manually input progress again** _**without**_ **introducing a separate field whilst still preserving the ability to link progress to work (but as a choice).**
### **Acceptance criteria**
##### **In Work-based mode:**
* All three fields are always editable: Work (W), Remaining work (RW) and % Complete (%C)
* For simpler progress reporting, it is possible to manually enter and edit a %C value for a work package:
* If W and RW are not entered, %C remains an independent, entered value that is _not_ automatically calculated. It behaves just as it like it did pre-14.0.
* If W or RW are also entered, the three values must always be consistent.
* For any work package, there are three possibilities:
* All three fields are empty (unset)
* Only one value is set (W, RW _or_ %C)
* All three values are set
* It is not possible to enter only two values; entering that second value will automatically derive a value for the third
* If W and %C are input, RW is calculated automatically
* If %C and RW are input, W is calculated automatically
* If RW and W are input, %C is calculated automatically
* In the pop-over to enter W, RW and %C values ("Estimates and progress"),
* % Complete is now an integer input field (limit: 0–100)
* The user can input just the number or a number followed by "%"
* If the input value for % Complete is higher than 100, an inline error message will read, "can't be over 100%"
* If the input value for % Complete is lower than 0%, an inline error message will read, "can't be over 100%"
##### **In Status-based mode:**
* We keep the current behaviour.
##### **Updated texts**
* **In** _**Administrator → Work packages → Work package settings**_**, change the guideline text under the field** _**Progress calculation**_ **to the following:**
* _In **work-based** mode, % Complete can be freely be set to any value. If you optionally enter a value for Work, Remaining work will automatically be derived. Changing Remaining work will then update % Complete. In **Status-based** mode, each status has a % Complete value associated with it. Changing status will change % Complete._
* **On the same page, in the yellow warning banner when switching from status- to work-based:**
* Changing progress calculation mode from work-based to status-based will result in all existing _% Complete_ values to be lost and replaced with values associated with each status. Existing values for _Remaining work_ may also be recalculated to reflect this change. This action is not reversible.
* **On the same page, in the yellow warning banner when switching from work- to status-based:**
* Changing progress calculation mode from work-based to status-based will preserve existing values but make the _% Complete_ field non-editable. Changing status will then automatically update _% Complete_. _Work_ and _Remaining work_ might be affected by status updates but will canot change the status-derived value of _% Complete_.
* **Text permenantly displayed in the pop-over to edit W, RW and %C**
* **Note**: % Complete is linked to Work and Remaining work when these values exist.
### User feedback
After this feature is implemented in a pull request, we will seek feedback form some of the users who previously expressed dissatisfaction to see if the changes are useful and helpful to them.
### Figma
[https://www.figma.com/file/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?type=design&node-id=1010-7036&mode=design](https://www.figma.com/design/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?node-id=2086-3403)
**I want to** manually set the % complete status of a work packge
**so that** I have more influence in what I communicate to my stakeholder
**As a** project member (eg. a developer),
**I want to** be able to quickly update how much progress I think I've made on a Feature or a User story
**So that** my team (including my manager) has a overall perspective on progress on an Epic or a Project in general
### **Context**
This feature is a response to user feedback on breaking changes to the way OpenProject handles progress reporting starting with version 14.0: ###40749
In version 14.x, in the default Work-based progress calculation mode, the _**% complete**_ field requires _Work_ (and consequently, _Remaining work_). This change makes made progress reporting possibly more grounded in reality but also introduced complexity:
* Progress cannot be manually input (like it was possible in the past) without also inputing a value for work.
* Progress is tied to the notion of _work done_ (or _earned value_); for users who want to update progress without also estimating work and remaining work in units of time, the only other option is to use _Status-based mode_, which is also not always ideal as certain users prefer decoupling status from % complete values.
A significant number of users were dissatisfied with the breaking change we introduced and the inability to manually enter progress. The found the new approach rigid and unadapted to the way they wanted to work.
**This feature seeks to make it possible again for users to manually input progress again** _**without**_ **introducing a separate field whilst still preserving the ability to link progress to work (but as a choice).**
### **Acceptance criteria**
##### **In Work-based mode:**
* All three fields are always editable: Work (W), Remaining work (RW) and % Complete (%C)
* For simpler progress reporting, it is possible to manually enter and edit a %C value for a work package:
* If W and RW are not entered, %C remains an independent, entered value that is _not_ automatically calculated. It behaves just as it like it did pre-14.0.
* If W or RW are also entered, the three values must always be consistent.
* For any work package, there are three possibilities:
* All three fields are empty (unset)
* Only one value is set (W, RW _or_ %C)
* All three values are set
* It is not possible to enter only two values; entering that second value will automatically derive a value for the third
* If W and %C are input, RW is calculated automatically
* If %C and RW are input, W is calculated automatically
* If RW and W are input, %C is calculated automatically
* In the pop-over to enter W, RW and %C values ("Estimates and progress"),
* % Complete is now an integer input field (limit: 0–100)
* The user can input just the number or a number followed by "%"
* If the input value for % Complete is higher than 100, an inline error message will read, "can't be over 100%"
* If the input value for % Complete is lower than 0%, an inline error message will read, "can't be over 100%"
##### **In Status-based mode:**
* We keep the current behaviour.
##### **Updated texts**
* **In** _**Administrator → Work packages → Work package settings**_**, change the guideline text under the field** _**Progress calculation**_ **to the following:**
* _In **work-based** mode, % Complete can be freely be set to any value. If you optionally enter a value for Work, Remaining work will automatically be derived. Changing Remaining work will then update % Complete. In **Status-based** mode, each status has a % Complete value associated with it. Changing status will change % Complete._
* **On the same page, in the yellow warning banner when switching from status- to work-based:**
* Changing progress calculation mode from work-based to status-based will result in all existing _% Complete_ values to be lost and replaced with values associated with each status. Existing values for _Remaining work_ may also be recalculated to reflect this change. This action is not reversible.
* **On the same page, in the yellow warning banner when switching from work- to status-based:**
* Changing progress calculation mode from work-based to status-based will preserve existing values but make the _% Complete_ field non-editable. Changing status will then automatically update _% Complete_. _Work_ and _Remaining work_ might be affected by status updates but will canot change the status-derived value of _% Complete_.
* **Text permenantly displayed in the pop-over to edit W, RW and %C**
* **Note**: % Complete is linked to Work and Remaining work when these values exist.
### User feedback
After this feature is implemented in a pull request, we will seek feedback form some of the users who previously expressed dissatisfaction to see if the changes are useful and helpful to them.
### Figma
[https://www.figma.com/file/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?type=design&node-id=1010-7036&mode=design](https://www.figma.com/design/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?node-id=2086-3403)