Content
View differences
Updated by Esther Hassan 4 months ago
A standardised request form is required for submitting **technical support requests** via the JSM portal (e.g. for HR-related services).
The form should support both **individual requests** and **collaborative requests**, where multiple people are involved in the same issue.
<br>
#### Form Proposed form structure
The request form should include the following fields:
* **Title**
* **Description**
* **Attachments**
* **Request Participants** _(important field)_
* **Priority**
* **Due Date**
####
#### Importance of the _Request Participants_ field
The **Request Participants** field is critical for collaboration. It allows multiple people to be involved in a single request, ensuring that:
* All relevant participants are aware of the request
* The request is visible to them in their JSM portal
* Participants receive notifications and updates
* Participants can interact with the request (e.g. comment, add information)
<br>
#### **User impact and behaviour**
From a user perspective:
* The request appears as a **shared request** involving all participants
* In practice, it remains a **single request**, submitted by one person
While one individual creates the request, all added participants:
* Receive notifications
* Can view and interact with the request through the JSM portal
* Can collaborate as if they made the original submission
This enables effective collaboration without duplicating requests.
####
The form should support both **individual requests** and **collaborative requests**, where multiple people are involved in the same issue.
<br>
#### Form
The request form should include the following fields:
* **Title**
* **Description**
* **Attachments**
* **Request Participants** _(important field)_
* **Priority**
* **Due Date**
####
#### Importance of the _Request Participants_ field
The **Request Participants** field is critical for collaboration. It allows multiple people to be involved in a single request, ensuring that:
* All relevant participants are aware of the request
* The request is visible to them in their JSM portal
* Participants receive notifications and updates
* Participants can interact with the request (e.g. comment, add information)
<br>
#### **User impact and behaviour**
From a user perspective:
* The request appears as a **shared request** involving all participants
* In practice, it remains a **single request**, submitted by one person
While one individual creates the request, all added participants:
* Receive notifications
* Can view and interact with the request through the JSM portal
* Can collaborate as if they made the original submission
This enables effective collaboration without duplicating requests.
####