SharePoint issue tracking web part
SPHub's issue tracking module is a SharePoint issue tracking web part that logs problems in one SharePoint list, inside your own Microsoft 365 tenant, and each issue can carry a priority, a status, an assignee and attachments. A setup wizard creates that list, its nine fields and six pages; staff then report, find and close issues through a two-step form and a set of views.
This page describes what the module's code does and, where it matters, what it does not do. The product's English interface calls a single issue a ticket, and the view names below are quoted as they appear.
The list and fields the setup wizard creates
The setup wizard creates one SharePoint list for issue tracking, named SPHubIssueTracker, with nine custom fields and attachments switched on.
Fields in the issue list
type and values- Issue descriptionMulti-line text
- PriorityChoice: Critical, High, Normal, Low
- StatusChoice, required, defaulting to New: Blocked, In progress, Completed, Duplicate, By design, Won't fix, New
- Assigned toPerson
- Date reportedDate, required
- Issue sourceA hyperlink, for the page or system where the problem was seen
- Issue logged byPerson
- Approval StatusChoice: Pending, Approved, Rejected; new items start as Pending
- Is ActiveYes or No, defaulting to Yes; the flag behind deletion, covered below
Every item also has SharePoint's own Title field. The column names and choice values are created in English. On an empty list the wizard adds one sample record, so the views are not blank on day one.
The New Ticket and Update Ticket forms
The New Ticket form has two steps, Core Details and Supporting Info, and the Update Ticket form uses the same two.
-
Step 1: Core Details
The first step asks for Title, Priority, Status, Assigned To, Issue Logged By and Description. Title, Description, Priority and Status are required. The Priority and Status dropdowns read their values from the list, so what you see there is what the list holds.
-
Step 2: Supporting Info
The second step takes Date Reported, an Issue Source URL with a description, and file attachments. Date Reported starts as today, and the source link must begin with http:// or https://.
-
Progress and safeguards
A progress indicator rises as fields are filled in. Leaving with unsaved changes asks you to confirm, and after a save the form offers Add another ticket or Return to list.
-
Editing an issue
Update Ticket opens from the edit icon on a row and shows the same two steps for an existing issue. Saving writes the changes back to the same list item.
Views: all tickets, your own, and tickets by status
Setup creates six pages for issue tracking, and four of them appear in the site menu, under a Ticket Management entry in the product's English interface: All Tickets, My Tickets, Tickets by Status and New Ticket.
Issue pages
what each shows- All TicketsEvery active issue, 50 rows to a page, with search, column filters, sorting, a detail panel, delete for selected rows, CSV export and a dropdown to hide chosen statuses
- My TicketsThe issues assigned to you or logged by you, with CSV export and the same hide-statuses dropdown
- Tickets by StatusFour tabs: issues you created that are still New or In progress, issues assigned to you, unassigned issues, and issues reported more than 30 days ago that are still New or In progress
- New TicketThe two-step form above
- Update TicketNot in the menu; opened from the edit icon on a row
- Tickets Recycle BinNot in the menu; opened from the Recycle Bin button on All Tickets
A Choose columns panel lets a person show or hide columns on each view, and the hidden statuses are remembered too. Both choices are saved in the browser, so they follow the browser rather than the account.
Approval, email and deletion
Issue records carry an approval status, can notify a contact person by email, and are deleted softly so that they can be restored.
-
Approval
A new issue starts as Pending. Members of a SharePoint group named
SPHub Approverssee Approve and Reject icons on the rows of All Tickets, My Tickets and Tickets by Status; everyone else sees none. The setup code does not create that group. -
Email
SPHub emails the contact person set for the module on the Settings page whenever an issue is created or updated, using a template from the email templates list. If no contact person is set, nothing is sent. The message goes through Microsoft Graph as the person who saved, and it lands in that person's Sent Items.
-
Soft delete and restore
Deleting an issue sets Is Active to No and leaves the item in the list. The Recycle Bin view lists those items and restores them. This is SPHub's own recycle bin, not SharePoint's, and neither view deletes an item for good.
-
What it does not do
The module has no service-level timers, no automatic escalation and no reminder emails. The 30-day tab is a built-in filter on the report date, not a deadline.
Where the data lives and who can see it
Issue data lives in the SPHubIssueTracker list on your own SharePoint site, an ordinary list you can open, export, back up and audit; where SPHub stores your data covers the whole product.
-
Your permissions apply
SPHub adds no permission model of its own, so SharePoint's permissions on the list decide who can read and change issues. The only SPHub-specific gate is the approver group described above.
-
Graph permissions
Two of the three Graph permissions touch this module.
Mail.Sendsends the notification email, andPeople.Readpowers the pickers for assignee and reporter. Neither reads your employee directory. -
Microsoft Teams
The web part can be added as a Teams tab. In a Teams tab it always opens the All Tickets view, not the other pages.
-
Settings page
The choice values above, such as priorities and statuses, are edited on the SPHub Settings page, which updates the list's choice fields directly. The same page sets the module's contact person.
How you get it
Issue tracking ships inside SPHub, and every SPHub plan includes every web part.
-
Created by the setup wizard
Enable the issue tracking module when you run setup and the wizard creates the list and pages. Lists are created only for the modules you enable; the install page has the steps.
-
One licence, every web part
No plan ships fewer web parts. Pricing is per user and falls with headcount, and the pricing page lists the five bands.
-
The other modules
Issue tracking is one of the 27 web parts; the web parts page names the rest.
Questions about SPHub issue tracking
The issue module's values, notifications and attachments are the three details answered below.
-
Can I change the priority and status values?
You can change the priority and status values on the SPHub Settings page. Two of the Tickets by Status tabs match the values New and In progress by name, so renaming those two values changes what those tabs show.
-
Does the assignee get an email?
The creation and update emails go to the contact person set on the Settings page, not to the person named in Assigned to.
-
Can an issue carry attachments?
An issue can carry attachments: the setup wizard switches attachments on for the list, and the second step of the form uploads files to the issue.
Other SPHub module pages
Issue tracking is not the only SPHub module with a page of its own: annual leave, expenses, travel requests and asset management each have one.
Module pages
what it is- Annual leaveA SharePoint leave request web part: employees submit leave through a two-step form and approvers review the requests in a list.
- ExpensesA SharePoint Online web part for expense requests: an employee submits an expense with its receipt, and an approver accepts or rejects it.
- Travel requestsA SharePoint Online web part for business travel requests: an employee describes a trip with its dates and estimated costs, and an approver accepts or rejects it.
- Asset managementA SharePoint asset management web part that keeps a company’s equipment inventory in one SharePoint list.
See issue tracking in your own tenant
Enable the module on a development site and watch the wizard create the list and its pages.