-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
14
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Use case is that, a customer sends an email with an agent CC'd on the message.
What happens now
- Agent gets added as a Request Participant, meaning they take on the customer role for ticket
What should happen
- Agent remains in agent role
How can this be done
- Automation is a good way to do this, but will require conditions to detect WHEN a Request Participant is added, and THEN allow participant to be removed from issue
The final result, might be something like:
- WHEN request participant added
- IF User is an agent
- THEN remove user from participants
- derived from
-
JSDSERVER-2376 When agent comment at issue created by himself , SLA didn't stop as per configured in "Time to Resolution"
-
- Closed
-
- is related to
-
JSDSERVER-5123 As a Service Desk Admin I would like to be able to restrict Customers from adding Agents to Requests as Participants
- Gathering Interest
-
JSDSERVER-6004 Add option to DISABLE adding CC users to request participants
- Gathering Interest
- relates to
-
JSDSERVER-5697 Allow JIRA Service Desk Admins to Decide When Agents should be Treated as Customers
- Gathering Interest
-
JSDCLOUD-12371 Provide automation conditions to allow removal of Request Participants
- Reviewing
- links to
- was cloned as
-
JSDS-353 Loading...
Form Name |
---|
[JSDSERVER-3506] Provide automation conditions to allow removal of Request Participants
Support reference count | Original: 8 | New: 14 |
UIS | Original: 11 | New: 6 |
Labels | Original: affects-cloud | New: affects-cloud ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 976647 ] |
UIS | Original: 6 | New: 11 |
UIS | Original: 12 | New: 6 |
UIS | Original: 6 | New: 12 |
UIS | Original: 5 | New: 6 |
UIS | Original: 4 | New: 5 |
UIS | Original: 8 | New: 4 |