**As a** project manager,
**I want to** manually set the % complete status of a work Begin of the insertionpackge End of the insertion Begin of the deletion packge End of the deletion
**so that** I have more influence in what I communicate to my stakeholder Begin of the insertion

End of the insertion Begin of the deletion



End of the deletion **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 Begin of the insertion

End of the insertion Begin of the deletion



End of the deletion ### **Context**

This Begin of the insertionfeature is a response to user feedback on breaking changes to the way OpenProject handles progress reporting starting with version 14.0:End of the insertion Begin of the deletion complements (or completes) another feature:

End of the deletion ###40749

Begin of the insertionIn version 14.x, inEnd of the insertion Begin of the deletion With that,End of the deletion the Begin of the insertiondefault Work-based progress calculation mode, theEnd of the insertion _**% complete**_ field Begin of the insertionrequiresEnd of the insertion Begin of the deletion will require and be a function of the value ofEnd of the deletion _Work_ (and consequently, _Remaining work_). This change makes Begin of the insertionmadeEnd of the insertion Begin of the deletion makesEnd of the deletion progress reporting Begin of the insertionpossiblyEnd of the insertion more grounded in reality but also Begin of the insertionintroducedEnd of the insertion Begin of the deletion introducesEnd of the deletion complexity:

* Progress cannot be manually input (like it Begin of the insertionwasEnd of the insertion Begin of the deletion isEnd of the deletion possible Begin of the insertionin the past)End of the insertion Begin of the deletion today)End of the deletion without also inputing a value for work. Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Progress Begin of the insertionisEnd of the insertion Begin of the deletion then logically also becomesEnd of the deletion tied to the notion of _work done_ (or _earned Begin of the insertionvalue_); for users who wantEnd of the insertion Begin of the deletion value_), or, alternatively,End of the deletion to Begin of the insertionupdate progress without also estimatingEnd of the insertion Begin of the deletion _time spent_. In either case, it's more information is needed to be able to calculate progress.

This means that the field represents a form of **calculated progress** expressed as a percentage a total (% complete) relative to (estimated)End of the deletion work and remaining work Begin of the insertionin units of time, the only other option is to use _Status-based mode_, which is also not always ideal asEnd of the insertion Begin of the deletion

ForEnd of the deletion certain Begin of the insertionusers prefer decoupling status from % complete values.


A significant number of users were dissatisfied with the breaking change we introducedEnd of the insertion Begin of the deletion users, organisationsEnd of the deletion and Begin of the insertionthe inabilityEnd of the insertion Begin of the deletion projects, however, there might be value in reporting progress manually, unconnectedEnd of the deletion to Begin of the insertionmanually enter progress. The found the new approach rigid and unadapted to the way they wanted to work.

**ThisEnd of the insertion Begin of the deletion other fields. ThisEnd of the deletion feature Begin of the insertionseeks to make it possible again for users to manually input progress again** _**without**_ **introducing a separate field whilst still preservingEnd of the insertion Begin of the deletion introducesEnd of the deletion the Begin of the insertionabilityEnd of the insertion Begin of the deletion notion of **Reported progress**End of the deletion to Begin of the insertionlink progress to work (but as a choice).**End of the insertion Begin of the deletion afford just that possibility.End of the deletion

### **Acceptance criteria**

Begin of the insertion**In Work-based mode:**

End of the insertion * Begin of the insertionAll three fields are always editable: Work (W), Remaining work (RW) and % Complete (%C)

End of the insertion Begin of the deletion There is a new field called **Reported progress**
End of the deletion * Begin of the insertionFor simpler progress reporting, it is possibleEnd of the insertion Begin of the deletion Migration: Existing _% complete_ values will be migratedEnd of the deletion to Begin of the insertionmanually enterEnd of the insertion Begin of the deletion this field
* Or rather, logically, the current "% complete" will be renamed "Reported progress"End of the deletion and Begin of the insertioneditEnd of the insertion a Begin of the insertion%C valueEnd of the insertion Begin of the deletion new attribute called "Calculated progress" will be introducedEnd of the deletion for Begin of the insertiona work package:

End of the insertion Begin of the deletion <mention class="mention" data-id="40749" data-type="work_package" data-text="#40749">#40749</mention>
End of the deletion * Begin of the insertionIf WEnd of the insertion Begin of the deletion The value is self-reportedEnd of the deletion and Begin of the insertionRW are not entered, %C remains an independent,End of the insertion Begin of the deletion manuallyEnd of the deletion entered Begin of the insertionvalue that is _not_ automatically calculated. It behaves just as it like it did pre-14.0.

End of the insertion Begin of the deletion and unaffected by other values (like _Work_, _Remaining work_ or _Time spent_)
End of the deletion * Begin of the insertionIf W or RW are also entered, the threeEnd of the insertion Begin of the deletion OpenProject can be configured to automatically set fixed reported progressEnd of the deletion values Begin of the insertionmust always be consistent.

End of the insertion Begin of the deletion based on status.
End of the deletion * Begin of the insertionFor any work package, there are three possibilities:

End of the insertion Begin of the deletion Example: in our own case here at OpenProject, these could be:
End of the deletion * Begin of the insertionAll three fields are empty (unset)

End of the insertion Begin of the deletion New = 0%
End of the deletion * Begin of the insertionOnly one value is set (W, RW _or_ %C)

End of the insertion Begin of the deletion In specification = 20%
End of the deletion * Begin of the insertionAll three values are set

End of the insertion Begin of the deletion Specified = 40%
End of the deletion * Begin of the insertionIt is not possible to enter only two values; entering that second value will automatically derive a value for the third

End of the insertion Begin of the deletion In development = 50%
End of the deletion * Begin of the insertionIf W and %C are input, RW is calculated automatically

End of the insertion Begin of the deletion Needs review = 80%
End of the deletion * Begin of the insertionIf %C and RW are input, W is calculated automatically

End of the insertion Begin of the deletion In testing = 90%
End of the deletion * Begin of the insertionIf RW and W are input, %C is calculated automatically

End of the insertion Begin of the deletion Tested = 99%
End of the deletion * Begin of the insertionInEnd of the insertion Begin of the deletion Closed = 100%
* Rejected = current value conserved but ignored in sums
* Status changes can update Reported progress but it&#39;s not a direct connection;End of the deletion the Begin of the insertionpop-overEnd of the insertion Begin of the deletion value remains manually editable.
* Setting a featureEnd of the deletion to Begin of the insertionenter W, RWEnd of the insertion Begin of the deletion &quot;In development&quot; will set it at 50% automatically, but a user can go aheadEnd of the deletion and Begin of the insertion%C values (&quot;EstimatesEnd of the insertion Begin of the deletion change it to 60% or even 100% if she wants, without affecting status
* _... (specification in progress)_

### **User Feedback**

**Task:** Contact around five different OpenProject users of different sizesEnd of the deletion and Begin of the insertionprogress&quot;),

End of the insertion Begin of the deletion ask them:

End of the deletion * Begin of the insertion% Complete is now an integer inputEnd of the insertion Begin of the deletion How they currently use the progressEnd of the deletion field Begin of the insertion(limit: 0–100)

End of the insertion Begin of the deletion (or how they report progress)
End of the deletion * Begin of the insertionThe user can input justEnd of the insertion Begin of the deletion What works for them and what doesn&#39;t
* To share screenshots of views they currently use (if possible).

We should a variety of different _types_ of usages inEnd of the deletion the Begin of the insertionnumber orEnd of the insertion Begin of the deletion same: for example,End of the deletion a Begin of the insertionnumber followed by &quot;%&quot;

End of the insertion Begin of the deletion large public organisations, a small NGO, a mid-sized company, perhaps a scientific team...

### **Open questions**

End of the deletion * Begin of the insertionIf the input value for  % Complete is higher than 100, an inline error message will read, &quot;can&#39;tEnd of the insertion Begin of the deletion **Sum:** Should itEnd of the deletion be Begin of the insertionover 100%&quot;

End of the insertion Begin of the deletion possible to sum Reported progress?
End of the deletion * Begin of the insertionIf the input value for  % Complete is lower than 0%, an inline error message will read, &quot;can&#39;t be over 100%&quot;


**In Status-based mode:**

End of the insertion Begin of the deletion \[PS: Yes. Why not?\]
End of the deletion * Begin of the insertionWe keepEnd of the insertion Begin of the deletion **Reported and/or Calculated:** Should it be possible to use both Reported progress and Calculated progress (% progress) atEnd of the deletion the Begin of the insertioncurrent behaviour.


### User feedback

After this feature is implemented in a pull request, we will seek feedback form some of theEnd of the insertion Begin of the deletion same time? Or should useEnd of the deletion users Begin of the insertionwho previously expressed dissatisfactionEnd of the insertion Begin of the deletion haveEnd of the deletion to Begin of the insertionsee ifEnd of the insertion Begin of the deletion pick one orEnd of the deletion the Begin of the insertionchanges are useful and helpful to them.End of the insertion Begin of the deletion other?End of the deletion

### Figma

Begin of the insertion[https://www.figma.com/file/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?type=design&amp;node-id=1010-7036&amp;mode=design](https://www.figma.com/design/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?node-id=2086-3403)End of the insertion Begin of the deletion https://www.figma.com/file/znrocQvFNLb5jXRXNo7oeD/Progress-estimation?type=design&amp;node-id=1010-7036&amp;mode=designEnd of the deletion