Ticket Assistant not showing the Reporter field
What project/issue permission(s) are required for the Reporter field to be displayed in chat channel notifications (Atlassian Assist/Ticket Assistant)?
We have a project used to request and grant access to any business application after the request flows through an approval process, and approvers for applications who don't hold the service desk team or higher role in this project receive notifications that are missing several fields, including Reporter.
This makes the approve/deny buttons meaningless and risky since they encourage approvers to take a convenient route and make a decision before properly reviewing the request.
Example notification that impacted approvers see:
A notification for the same request received by an approver who is also a project admin with the differences called out in red:
We have an automation that adds approvers as request participants on create, and they can view these fields fine in the customer portal, this limitation only occurs in chat channel notifications.
The behavior also occurs regardless of JSM agent licensing, and when the approver has read-only access to this project. We have approvers who are agents in other projects, and have read-only access to this one, but don't receive the requester field in chat notifications unless we temporarily elevate them to support desk team in this one.
Our goal is to allow approvers to see all attributes in the chat notification (though at minimum we need Requester to be visible) without granting them access to edit requests or create arbitrary requests in the agent portal.
So we can't grant them service desk team since it enables request create and edit, but I've tested granting several project permissions, including Service Project Agent, and none of them have enabled these fields in chat notifications.
1 answer
1 accepted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.