NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Currently for approvals you are able to select custom user fields as approvers, however you are not able to use the reporter field as a user field for approvals. It will be nice to have the ability to use reporters as approvers for the approval functionality.
- is related to
-
JSDSERVER-3729 Adding the possibility of setting the 'Reporter' as a default value for hidden Approvers
- Gathering Interest
- mentioned in
-
Page Failed to load
[JSDCLOUD-3729] Adding the possibility of setting the 'Reporter' as a default value for hidden Approvers
Tim Duly
added a comment - There is a workaround for this.
Add a post function to the 'Create Issue' transition in your workflow to copy the 'Reporter' field value to the 'Approvers' field.
Tim Duly
added a comment - There is a workaround for this.
Add a post function to the 'Create Issue' transition in your workflow to copy the 'Reporter' field value to the 'Approvers' field. Tim Duly
added a comment - This would be a useful feature as it would automatically mean that a reporter would have to 'approve' their own ticket. In the case of a service desk this is useful as tickets can get raised by the reporter. However, they may not be ready for the service desk to review. Adding this approval step allows the reporter to choose when the service desk should look at it.
A flow similar to below:
1. reporter raises ticket
2. reporter gathers additional information required to support the ticket (eg logs, docs, screenshots etc)
3. reporter than 'Approves' the ticket thereby highlighting to the service desk that it is ready for their review
4. Service desk team review the ticket
You could also use the reporter as the person who approves that the ticket is 'Done' (ie done to their satisfaction)
Tim Duly
added a comment - This would be a useful feature as it would automatically mean that a reporter would have to 'approve' their own ticket. In the case of a service desk this is useful as tickets can get raised by the reporter. However, they may not be ready for the service desk to review. Adding this approval step allows the reporter to choose when the service desk should look at it.
A flow similar to below:
1. reporter raises ticket
2. reporter gathers additional information required to support the ticket (eg logs, docs, screenshots etc)
3. reporter than 'Approves' the ticket thereby highlighting to the service desk that it is ready for their review
4. Service desk team review the ticket
You could also use the reporter as the person who approves that the ticket is 'Done' (ie done to their satisfaction)
Hi,
This can be achieved by using a post function or an automation rule to add the Reporter to the user field being used by the Approvals system.
We do not intend to provide specific functionality for this.
Cheers,
Jason