Distinction between Leave requester and Leaving Employee Name

Registered by Grzegorz Grzelak (OpenGLOBE.pl)

IMHO requester of leave should be visible to leave validator.

When you create leave request you can choose employee other than you. I think validator should know if he is validating leave of requester or someone else when requester issued request on behalf of other person.

I suggest to add readonly field Requester User which will be displayed from create_uid. More advanced improvement would be to display additionally readonly field of Requester Employee assigned to create_uid. Field Requester Employee can be empty if it is no assignment to Requester User. And if Employee Name is different than Requester Name the Employee Name could be displayed in Blue (otherwise Black).

I think leave acceptance procedure is quite formal so date of applying should also be visible for validator (from create_date).

The problem is that someone else can change request and this user is not in create_uid field but in write_uid. So to cover this case the solution should be more sophisticated. I think we should change convention that after creating the record write_uid and write_date should also be filled as copy of creation data. I will write blueprint in OpenObject for that.

Created as:
https://blueprints.launchpad.net/openobject-server/+spec/write-uid-equal-create-uid-on-creation

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Grzegorz Grzelak (OpenGLOBE.pl)
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
Proposed for trunk
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.