Ticketing System User Guide » History » Version 1
Kenneth Lim, 12-02-2025 09:14 AM
1 | 1 | Kenneth Lim | h1. Ticketing System User Guide |
---|---|---|---|
2 | |||
3 | --- |
||
4 | |||
5 | h2. Introduction |
||
6 | The Ticketing System is a flexible project management web application. It provides issue tracking, time tracking, and multiple project management capabilities. This guide will help users navigate the Ticketing System and utilize its features effectively. |
||
7 | |||
8 | --- |
||
9 | |||
10 | h2. 1. Logging In |
||
11 | # Open your web browser and go to the Ticketing System URL. |
||
12 | # Enter your *Username* and *Password*. |
||
13 | # Click *Login*. |
||
14 | # If you forget your password, click *Forgot your password?* to reset it. |
||
15 | |||
16 | --- |
||
17 | |||
18 | h2. 2. Dashboard Overview |
||
19 | After logging in, you will see: |
||
20 | * **Top Navigation Bar**: Contains links to Home, My Page, Projects, Administration (if applicable), Help, and Logout. |
||
21 | * **Sidebar**: Quick access to different modules (Issues, Time Entries, Gantt, Calendar, etc.). |
||
22 | * **Main Content Area**: Displays project activities, news, and latest updates. |
||
23 | |||
24 | --- |
||
25 | |||
26 | h2. 3. Creating a New Project |
||
27 | # Click *Projects* from the top navigation. |
||
28 | # Click *New Project*. |
||
29 | # Fill in the required details: |
||
30 | * *Project Name* |
||
31 | * *Identifier* (unique key for URLs) |
||
32 | * *Description* |
||
33 | * *Public/Private* (visibility settings) |
||
34 | # Select relevant modules (Issues, Wiki, Files, etc.). |
||
35 | # Click *Create*. |
||
36 | |||
37 | --- |
||
38 | |||
39 | h2. 4. Managing Issues |
||
40 | |||
41 | h3. Creating an Issue |
||
42 | # Navigate to the relevant project. |
||
43 | # Click *New Issue*. |
||
44 | # Fill in details: |
||
45 | * *Tracker* (Bug, Feature, Task, etc.) |
||
46 | * *Subject* (short summary) |
||
47 | * *Description* |
||
48 | * *Priority* (Low, Normal, High, etc.) |
||
49 | * *Assignee* (optional) |
||
50 | * *Due Date* |
||
51 | # Click *Create*. |
||
52 | |||
53 | h3. Updating an Issue |
||
54 | # Open the issue you want to update. |
||
55 | # Click *Edit*. |
||
56 | # Modify relevant fields. |
||
57 | # Click *Save*. |
||
58 | |||
59 | h3. Closing an Issue |
||
60 | # Open the issue. |
||
61 | # Change the *Status* to *Closed*. |
||
62 | # Click *Save*. |
||
63 | |||
64 | --- |
||
65 | |||
66 | h2. 5. Time Tracking |
||
67 | # Open the issue you worked on. |
||
68 | # Click *Log Time*. |
||
69 | # Enter: |
||
70 | * *Hours spent* |
||
71 | * *Activity* (Development, Testing, etc.) |
||
72 | * *Comment* (optional) |
||
73 | # Click *Save*. |
||
74 | |||
75 | --- |
||
76 | |||
77 | h2. 6. Using the Wiki |
||
78 | # Go to the project’s *Wiki* module. |
||
79 | # Click *Edit* or *New Page*. |
||
80 | # Add content using Markdown or Textile formatting. |
||
81 | # Click *Save*. |
||
82 | |||
83 | --- |
||
84 | |||
85 | h2. 7. Managing Users & Roles |
||
86 | # Go to *Administration > Users*. |
||
87 | # Click *New User* to add a new user. |
||
88 | # Assign roles and permissions. |
||
89 | # Click *Create*. |
||
90 | |||
91 | --- |
||
92 | |||
93 | h2. 8. Generating Reports |
||
94 | # Navigate to *Issues* in a project. |
||
95 | # Use filters to narrow down results. |
||
96 | # Click *Apply*. |
||
97 | # Export as CSV, PDF, or Excel (if enabled). |
||
98 | |||
99 | --- |
||
100 | |||
101 | h2. 9. Configuring Email Notifications |
||
102 | # Click *My Account*. |
||
103 | # Select *Email Notifications*. |
||
104 | # Choose the notifications you want to receive. |
||
105 | # Click *Save*. |
||
106 | |||
107 | --- |
||
108 | |||
109 | h2. 10. Integrations & Plugins |
||
110 | * The Ticketing System supports various plugins for extended functionality. |
||
111 | * Check *Administration > Plugins* to install and configure additional features. |
||
112 | |||
113 | --- |
||
114 | |||
115 | h2. Conclusion |
||
116 | This guide provides a basic overview of the Ticketing System’s features. For more advanced settings, refer to the system’s official documentation or contact your administrator. |