Content
View differences
Updated by Marc Alcobé about 14 hours ago
**As a** user with permission to log time **Original feedback**
_Time entry for others
**I want to** log time for another user without including myself
**so that** I can record time entries work packages on someone else’s behalf accurately
### Acceptance Criteria
* If of other colleagues (within the current user does **not** have the permission to log time for others:
* The Users field scope of permissions) is hidden.
* The time entry is always logged for not possible via the current user (existing behavior).
* If the current user **does** have the permission to log time for others:
* The Users field is visible.
* The Users field allows selecting a **user** for this flow.
* The default selected value in Users is the current user.
* The user picker list includes “(me)” as a selectable option, app, but it is **not forced** and can be unselected by selecting a different user.
* Selecting a different user replaces possible via the current selection, and returning to the Log time form shows the chosen user in the Users field.
web application._
**Acceptance criteria**
* It must be possible to save a time entry where the selected user is **not** the current user.
<br>
**Technical notes**
* All existing required fields <br>
**Permissions and validations for logging time apply unchanged (at minimum: Work package, Date, and either Hours or Start/Finish when “Include exact times” is enabled).
visibility considerations**
* On Save:
* The time entry _To whom is created for the selected user.
this feature visible?_
* The success confirmation does not imply the current user was included unless the selected user _When is “me”.
* If the user attempts to save without selecting a user (only if the field can be empty by default):
* The app prevents saving and shows a clear validation error on the Users field.
* The app only allows to see logged time entries of the current user it not others. visible?_
### Technical Notes **Translation considerations**
<br>
### Permissions and Visibility Considerations
* The Users field is visible only to users with permission to log time for others.
* Users shown _Key terms and phrases in the picker must respect:
* User directory visibility rules.
* Without permission, the feature is effectively unavailable (field hidden; self-only logging). key languages_
### Translation Considerations
<br>
### Out **Out of Scope scope**
* Changing the permission model or introducing new permissions/roles.
* Multi-user batch logging (covered by the separate “log time for multiple users” feature).
* Changes <br>
_Set the_ **To be informed/consulted teams** _field to timer functionality beyond selecting the target user for a logged time entry.
### **Original feedback**
_Time entry for work packages on behalf include all teams necessary to be informed of other colleagues (within the scope of permissions) is not possible via the app, but it is possible via the web application._ changes._
_Time entry
**I want to** log time for another user without including myself
**so that** I can record time entries
### Acceptance Criteria
* If
* The Users field
* The time entry is always logged for
* If the current user **does** have the permission to log time for others:
* The Users field is visible.
* The Users field allows selecting a **user** for this flow.
* The default selected value in Users is the current user.
* The user picker list includes “(me)” as a selectable option,
* Selecting a different user replaces
**Acceptance criteria**
**Technical notes**
**Permissions
* The time entry
* If the user attempts to save without selecting a user (only if the field can be empty by default):
* The app prevents saving and shows a clear validation error on the Users field.
* The app only allows to see logged time entries of the current user
### Technical Notes
<br>
### Permissions and Visibility Considerations
* The Users field is visible only to users with permission to log time for others.
* Users shown
* User directory visibility rules.
* Without permission, the feature is effectively unavailable (field hidden; self-only logging).
### Translation Considerations
<br>
### Out
* Changing the permission model or introducing new permissions/roles.
* Multi-user batch logging (covered by the separate “log time for multiple users” feature).
* Changes
_Set the_ **To be informed/consulted teams** _field
### **Original feedback**
_Time entry for work packages on behalf