Add status messages to a Requisition

As a storeroom manager, I want to leave status messages on my requisitions so that I can convey the context for why I am asking for this mix of products (what I'm requesting may be more expensive than my budget) so that approvers understand my situation.

As a Program Manager (approver), I want to leave status messages on the requisition so that I can communicate to the storeroom manager why I approved or rejected the requisitions.

Acceptance Criteria

• A user can add a draft status message to a requisition (as long as they have permissions to edit the requisition based on their rights and the current state of the requisition)

• Any user with permissions can edit that draft status message until a requisition state change (example: initiated -> submitted, but this can apply to authorize: submitted -> authorized, or approve: authorized -> approved, or reject: authorized -> initiated)

• A draft status message's text can include special characters and line breaks

• A draft status message is saved as part of a PUT request to a requisition's endpoint

  • 'draftStatusMessage' is the name of the data variable passed to the requisition endpoint, which will create or update the most recent draft status message

  • If there is a PUT request to a requisition, and the request data doesn't include a draftStatusMessage field, remove any draft status messages

  • until a status message is "fully saved," it is stored as 'draftStatusMessage' in the requisition DTO

• A requisition state change will "fully save" the status message, turning it from a draft status message into status message

  • It will also empty the draftStatusMessage field in the requisition, since there is no draft status message; it has been "fully saved" and is no longer a draft

• A "fully saved" status message (when a state change happens) has the following attributes:

  • a unique UUID

  • a requisition UUID

  • the user that changed the requisition state (so future users know which person left the status message)

  • the status that the requisition was changed to (so other users will know the action the person took)

  • the timestamp of when the requisition state change happened

  • a text string for the status message – there is no character limit

• A requisition should return the entire status message history with the other requisition data (ie product grid data)

• Status messages for a requisition are never deleted on state change or save, and only get added to (if a user rejects a requisition, the status messages will stay with it and still be there later when it is revised and comes back for approval again)

• When a requisition is deleted, the status messages are deleted (and will not reappear on another requisition)

–

Current Use in eLMIS
Q: Can you elaborate on how requisition comments are used? Or the main purpose?
@Ashraf Islam response: RnR for ILS products are budget controlled and wanted to see the price for the RnR. They can write on the comment section to say why they are requesting more stocks than what they have available.
Q: Could you tell me if multiple comments are needed per requisition? With timestamps?
A: @Ashraf Islam it should suffice to have comments tied to status change. Meaning that saving the comments upon a save, submit, reject, approve, authorize, etc.
Q: Do you know how much they have been used?
A: @Ashraf Islam Probably not that often.