Knowledge Base

Issue Tracking is used to capture, organize, and manage bugs, defects, and tasks discovered during the testing lifecycle of a project. It provides a centralized place where teams can log issues, assign them to team members, set priorities and deadlines, and monitor their resolution status.

By linking issues directly to test activities, teams can maintain a clear connection between failed test cases and the underlying defects that need to be resolved. This ensures that nothing falls through the cracks and that all discovered problems are tracked until completion.

Additionally, when a test case result is marked as Failed, an issue automatically created and linked to that test case. This automation helps teams quickly capture defects at the moment they are identified, reduces manual effort, and ensures faster visibility and resolution of critical problems.

Create an Issue ?

The Create Issue form allows users to log a new defect, bug, or task within a project. Each issue is assigned a unique key that makes it easy to reference and track across the project.

Navigate to: Project → Issues → Create New Issue

Fields in the Create Issue Form

1. Title

The Title is the primary identifier for the issue. Use a clear and concise summary that describes the problem or task.

Examples:

• Login button not responding on mobile
• API returns 500 on invalid payload

2. Description

The Description field provides detailed information about the issue. It may include steps to reproduce, expected versus actual behavior, environment details, or any additional context.

This field supports rich text formatting to improve readability and clarity.

3. Assigned To

The Assigned To field designates the project member responsible for investigating or resolving the issue.

Only members of the current project appear in the selection list.

4. Priority

The Priority field indicates the urgency and impact of the issue.

Available options:

• Critical: Must be resolved immediately; blocks progress.
• High: Significant impact; should be addressed as soon as possible.
• Medium: Moderate impact; addressed in the current cycle (default).
• Low: Minor impact; can be deferred.

5. Reported By

The Reported By field identifies the project member who discovered and reported the issue.

This field is required and helps maintain accountability and traceability.

6. Due Date

The Due Date field allows you to set a target resolution date for the issue.

• Helps teams prioritize work
• Ensures critical issues are resolved on time
• Improves planning and coordination

7. Attachments

The Attachments field allows up to 5 files to be uploaded with the issue.

• Screenshots of the problem
• Logs or error messages
• Supporting documents

These files help the team understand and reproduce the issue more easily.

8. Custom Fields

The Custom Fields field allows you to add custom fields to the issue.

Custom fields are used to capture additional information about the issue.

Click Save to create the issue.

Issue List

The Issue List provides a consolidated view of all issues logged within a project. It allows teams to quickly review reported problems, identify high-priority issues, and manage them efficiently.

Navigate to: Project → Issues

Columns Displayed

• Key: Unique auto-generated identifier for the issue.
• Title: The issue name; click to open full details.
• Status: Current workflow state of the issue.
• Priority: Urgency level of the issue.
• Assigned To: Responsible project member.
• Due Date: Target resolution date.

Filtering

The filter bar at the top of the issue list allows users to narrow down issues using different criteria.

• Search: Free-text search across title, description, and issue key.
• Status: Filter by workflow status.
• Priority: Filter by priority level.
• Assigned To: Filter by responsible team member.
• Reported By: Filter by the person who reported the issue.

Click Search to apply filters or Reset to clear them.

Sorting

Issues can be sorted by clicking the column header for:

• Key
• Title
• Priority
• Due Date

Issue Detail

Clicking an issue title in the list opens the Issue Detail view in a side panel. This view displays complete information about the issue and allows users to edit or delete it.

Information Displayed

• Title
• Key
• Status
• Priority
• Due Date
• Description
• Attachments
• Assigned To
• Reported By
• Estimated Time
• Time Spent
• Created At
• Updated At

Resolve an Issue

When an issue is ready to move to its final stage, update its Status and select an appropriate Resolution. Depending on the status you choose, Tuskr displays a resolution form where you can record how the issue was handled.

Available Resolution Statuses

• New: The issue has been created and is awaiting review or assignment.
• In Progress: Work has started on the issue and it is actively being investigated or fixed.
• Resolved: The issue has been fixed and is ready for verification.
• Blocked: Progress cannot continue because of a dependency or external factor.
• Closed: The issue has been verified and no further action is required.

Comments

Add a resolution comment to provide context for the status change. These comments are recorded in the issue history for future reference.

Issue History

Every important activity performed on an issue is automatically recorded in the History tab, giving your team a complete audit trail of the issue's lifecycle.

The history includes:

• Issue creation details, including the creator and timestamp.
• Status changes (for example, New → In Progress → Blocked → Resolved → Closed).
• Resolution updates.
• Comments entered while changing the issue status.
• User who performed each action.
• Date and time of every update.

Actions

Edit Issue

To modify an existing issue, hover over the issue row and click the Edit icon. This opens the issue form in edit mode where fields can be updated.

Click Save to apply the changes.

Delete Issue

To remove an issue, hover over the issue row and click the Delete icon.

A confirmation prompt appears before the issue is moved to the recycle bin.

Bulk Delete

Multiple issues can be deleted at once by selecting checkboxes next to the issues and clicking the Delete button in the bulk action bar.

Linking Issues to Test Run Results

Issues can be created directly from within a Test Run result.

When a test case fails or is blocked during execution, testers can click Add Issue within the result record to log the defect immediately.

This automatically links the new issue to the specific test run result, ensuring clear traceability between the failed test case and the defect.

Once linked, the issue appears inside the test run result record with options to view, edit, or remove the link.

Benefits of Issue Tracking

• Maintain a clear log of all defects and tasks discovered during testing.
• Prioritize work using urgency levels and due dates.
• Assign ownership to ensure accountability.
• Track estimated vs. actual time spent for better planning.
• Link issues directly to test run results for full traceability.
• Quickly filter and search issues that require attention.