Please log the user throughout the process and display this information wherever possible to allow for traceability and transparency on who initiates, comments, rejects, accepts etc... "cash out" actions in the organisation. This would probably flow into any future bookkeeping functionality.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | tmgmt-add_uid_to_messages-1901030-7.patch | 11.6 KB | berdir |
| #7 | tmgmt-add_uid_to_messages-1901030-7-interdiff.txt | 1.84 KB | berdir |
| #3 | tmgmt-add_uid_to_messages-1901030-2.patch | 10.44 KB | blueminds |
| #2 | tmgmt-add_uid_to_messages-1901030-1.patch | 10.44 KB | blueminds |
Comments
Comment #1
miro_dietikerRelated to #1900946: Trace remote job issuer not possible
Comment #2
blueminds commentedPlease see the patch
Comment #3
blueminds commentedfixed typo
Comment #4
miro_dietikerLooks pretty fine. I guess we should push this ASAP.
Comment #5
miro_dietikerI would love to see the current user being tested in the output.
An extra test user switch (job creation, job submission) would be even more exciting... ;-)
Comment #6
berdir#3: tmgmt-add_uid_to_messages-1901030-2.patch queued for re-testing.
Comment #7
berdirBasic level of excitement test coverage.
Comment #8
berdirCommited and pushed.