Skip to content

Service Desk Issue Url Placeholder

Release notes

For service desk requesters, it may be helpful to access the service desk issue directly rather than interact with the service desk request only via email. We are introducing a new placeholder %{ISSUE_URL}, that you can use in places such as the Thank you email to link requesters directly to the service desk issue.

Proposal

Currently, when an issue is created via Service Desk, the notification email sent to the recipient does not include a direct link to the newly created issue. This can be inconvenient for users who need to quickly access the issue to respond or take action.

It would be helpful to include a direct link to the newly created issue in the notification email. This would allow users to easily access the issue without having to navigate through the Service Desk interface.

By providing a direct link to the issue in the notification email, users can more easily and quickly respond to new Service Desk issues, which can improve overall productivity and customer satisfaction.

Current available options:

This is %{ISSUE_ID}: issue IID

This is %{ISSUE_PATH}: project path appended with the issue IID

%{UNSUBSCRIBE_URL}: unsubscribe URL

THis is %{ISSUE_ID}: issue IID

This is %{ISSUE_PATH}: project path appended with the issue IID

THis is %{UNSUBSCRIBE_URL}: unsubscribe URL

Response

This is #5 issue IID 

This is PATH/service-desk-testing#5: project path appended with the issue IID 

https://gitlab.com/-/sent_notifications/HASH/unsubscribe: unsubscribe URL 

This is #5: issue IID This is gitlab-gold/arihant-testing/service-desk-testing#5: project path appended with the issue IID 

This is https://gitlab.com/-/sent_notifications/REDACTED/unsubscribe: unsubscribe URL

<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->

<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->

<!-- Label reminders
Use the following resources to find the appropriate labels:
- Use only one tier label choosing the lowest tier this is intended for
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
Edited by Kevin Chu