You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -305,6 +305,19 @@ And that's all! And with that, you've just completed your first ticket—congrat
305
305
306
306
Happy ticketing!!!
307
307
308
+
### 3.4.2 Example Ticket Workflows
309
+
1. Open a ticket using `/ticket` or `-ticket` without ading a user.
310
+
2. Write a complete opening message. Ensure that all points are covered; use multiple messages if required.
311
+
3. Add a member to the ticket using `/add`.
312
+
4. Mention the member with an @ so they get notified of the ticket.
313
+
314
+
This is ideal for tickets that are neither critical nor time sensitive. Members can get needlessly anxious when they are added to an empty ticket while you are typing, so preparing your message beforehand can prevent unnecessary stress.
315
+
316
+
1. Right click on a member's profile, and click on `Create Ticket` in the apps menu. This will immediately add the member to the new ticket.
317
+
2. The target member should be notified after the ticket is created. At this point you can address the member while they have your attention.
318
+
319
+
This works for immediate concerns that need to be addressed quickly. You can run tickets this way for cases that are easily resolvable or just to promptly pull someone aside.
0 commit comments