Issues
The Administration → Issues page is a global, cross-project table of every issue that has been linked into TestPlanIt from an external tracker — Jira, GitHub, GitLab, Azure DevOps, Gitea, Redmine, MantisBT, or a Simple URL link. Use it to review, re-sync, edit, or delete issue records that appear across your test cases, runs, and sessions.
Only system administrators can open this page. To view or manage issues for a single project, use the project's own Issues page instead.
How to access
- Open the Admin area from the top navigation.
- Select Issues under Test Management in the admin menu.
Viewing issues
Issues are listed in a sortable, filterable table. Use the Filter issues... box to search by name, title, or description (matching is case-insensitive). The Columns control lets you show or hide optional columns; your choice is remembered in this browser for this table.
Three multi-select dropdowns sit beside the search box: Status, Priority, and Issue Type. Each lists the values currently in use. Selecting several values in one dropdown matches issues with any of them; selections in different dropdowns apply together. Leave a dropdown empty to include every value. Matching is case-insensitive, so values that differ only in capitalization are treated as one. The Issue Type dropdown also offers a No Issue Type entry when some issues have no type set — issues only receive a type when they are synced from or created in an external tracker, and not every tracker supplies one. A dropdown is hidden when no issue has a value for that field.
| Column | Description |
|---|---|
| Name | The issue key/name, with status, priority, the provider icon, the issue-type icon, and a link out to the external issue. Always shown. |
| Title | The issue title (plain text). Click to open a popover with the full formatted content. |
| Description | The issue description. Click to open a popover with the full formatted content. |
| Status | The synced status from the external tracker. |
| Priority | The synced priority (defaults to medium). |
| Last Synced | When the issue was last refreshed from the external system, or -. |
| Test Cases | Count of repository cases linked to this issue. |
| Test Runs | Count of linked test runs. |
| Sessions | Count of linked sessions. |
| Milestones | Count of milestones the issue belongs to. Click the count to open a popover listing them, each with its milestone type icon and, for synced milestones, a Jira source badge. |
| Projects | The projects the issue appears in. |
| Integration | The integration the issue was linked through, or -. |
| Actions | Per-row actions (see below). Always shown. |
The Name, Title, Status, Priority, Integration, and Last Synced columns are sortable. The default sort is by name, ascending.
Issues are not created from this page. They appear in TestPlanIt automatically when you link an external issue to a test case, run, or session, when an inbound webhook imports one, or when a project administrator bulk-imports them from a linked external project. This administration page manages issues that already exist.
Actions
Each row exposes up to three actions:
Sync
Pulls the latest data (status, priority, title, description) for the issue directly from its external tracker. A success toast confirms the update; the Last Synced timestamp advances.
The Sync action is hidden when the issue has no linked integration, no external ID, or belongs to a Simple URL integration — a plain link has no upstream API to pull from.
Edit
Opens the Edit Issue dialog with these fields:
- Name
- External Key — for example
JIRA-123or#456 - Title
- Description
Saving recalculates the external URL from the integration's base URL and the provider's link format (for example Jira /browse/KEY, GitHub /issues/NUMBER, Azure DevOps /_workitems/edit/ID, Redmine /issues/ID, MantisBT /view.php?id=ID).
Delete
Opens the Delete Issue confirmation. Deleting is a soft delete — the issue is hidden from lists but retained in the database (and can be restored from Trash by an administrator).
Related pages
- Issue Integrations — connect a tracker so issues can be linked.
- Webhooks — receive issue updates from your tracker in near-real time.
- Audit Logs — every sync, edit, and delete is recorded.