IssueTruck
Get started Start
IssueTruck
Manual

User Manual

From joining through an invitation link to registering issues, setting up test environments, tracking the handling, and completing verification.

01

Getting started

After joining an invited service, you register issues and review what the assignee has recorded. When verification is requested, retest under the same conditions and then close or reopen the issue.

Issue handling flow

Step What you do
1 Log in Open the invitation link; if you do not have an account, sign up and then log in.
2 Join the service Check the service name and the join notice, then join.
3 Register an issue Enter the type and title, the reproduction details, and the attachments and test environment.
4 Track the handling Check comments and status-change notes in the Activity section.
5 Verify Retest in the fixed version, then close or reopen the issue.
Issue status flow Received In progress Verification requested Closed Reopened

You can view and search every issue registered in the current service. Only participants of an issue can add comments or change its status.

Invitation link and login

Open the invitation link provided by the administrator. If you are not logged in, you go through the login page and return to the invitation page.

Login page opened from an invitation link
  1. 1 If you already have an account, enter your email and password, then select [Login].
  2. 2 If you do not have an account, select [Sign up], create an account, and log in.

If you signed up from the regular login page instead of the invitation link, open the invitation link again after logging in.

Join the service

After login, the name of the invited service and the join notice are displayed. Confirm that it is the service you meant to join.

Service join confirmation page
  1. 1 Check the service name and the join notice.
  2. 2 Select [Join service] to join with tester permissions.

The service you join becomes the current service automatically. Opening the same invitation link again does not add you twice.

02

Register an issue

Open the registration page and enter the type and title, the reproduction details, and the attachments and test environment in order.

Open the registration page

Check the service name at the top first. Open the issue list from the left menu, then go to the registration page.

Where to open the registration page from the issue list
  1. 1 Select [Issues] in the left menu to open the list.
  2. 2 Select [+ Create issue] at the upper right of the list.
Before registration
  • Clear [Show participating issues only] and search by title or symptom to see whether the same problem is already registered.
  • If several problems occur together, register each one separately when the cause or reproduction steps differ.
  • Make sure the selected service matches the test target.

Basic information and details

Choose the type and priority, then enter the title and description.

Entering the issue type, title, and reproduction details
  1. 1 Select the type, priority, and category. Use [Normal] when the priority is hard to judge.
  2. 2 Include both the location and the symptom in the title.
  3. 3 In the description, separate the steps to reproduce, actual result, expected result, and reproduction frequency.
Description templates
  • Select [+ Template] to load one of two formats: general issue or bug report.
  • Replace the example text in the loaded format with the actual issue content.

How to write the title and the reproduction steps is covered in 04 Writing it well.

Attachments and test environment

Add the files that help reproduce the problem, together with the environment used for this test.

Selecting evidence files and the test environment
  1. 1 Upload screenshots, videos, logs, and other files that help reproduce the problem.
  2. 2 In [Occurrence situation], record the action performed right before the problem.
  3. 3 In [Test environment], select the environment you used for this test.
  4. 4 Review what you entered, then select [Create issue].

The test environments you can choose from are the ones registered under Personal settings. If the list is empty, create one first in 03 Personal settings.

Attachment limits
  • Up to 5 files in total, including images embedded in the description
  • Up to 10 MB per file
  • File names up to 255 characters

Before attaching, make sure the files contain no passwords, personal information, API keys, or tokens.

03

Personal settings

The test environments you choose on the issue registration page are created in advance under Personal settings. Once registered, you simply pick one from the list every time you report an issue.

Register a test environment

Open Personal settings in the left menu to review the environments you have registered and add a new one.

Test environment list in Personal settings
  1. 1 Select [Personal settings] in the left menu.
  2. 2 Select [Add test environment] in the Test environment section to open the input dialog.
What you do in the list
  • Registered environments appear in the list with their name and device type.
  • Select [Edit] to change the details, or [Delete] to remove an environment you no longer use.
  • Create a separate environment for each device or version, then choose one per issue.

Enter the environment details

Set the name and device type first, then fill in the details that match the device type.

Add test environment dialog
  1. 1 Enter a name you can recognize in the list and select the device type.
  2. 2 Enter the operating system and OS version, the browser and browser version, and the screen resolution, and add anything else in Notes.
  3. 3 Select [Save changes] to add it to the list.

What you enter here is shown as is in the Information section of the issue detail page. The assignee uses it to reproduce the problem, so record the versions accurately.

Notification settings

On the same page, decide which notifications you receive and how. Turn email and push on or off for each notification, then select [Save notification settings].

Notification When you receive it
Issue created A new issue is registered in a service you belong to
New comment A comment is added to an issue you participate in
Status change The status of an issue you participate in changes
Participant added You are added as a participant of an issue

Comment and status-change notifications are sent to the reporter and active participants, excluding the user who performed the action.

04

Writing it well

How to write an issue so that another person can reproduce and confirm the same result.

Writing the title

Write it so the location and the symptom are clear from the title alone.

Good title

Verification code button does not work on the sign-up page

Titles to avoid

An error occurs / Please check

Writing reproduction steps

Separate the following four parts in the description.

Steps to reproduce
  1. Launch the app and log in with the test account.
  2. Select the notification icon at the top.
  3. Open all notifications, then return to the list page.
Actual result

The notification badge continues to display 1 even though there are no new notifications.

Expected result

The notification badge should disappear after all notifications have been opened.

Reproduction frequency

5 out of 5 attempts

Choosing the issue type

Choose the type on the registration page by these criteria.

Type When to use
Bug The feature does not work as expected or an error occurs
Improvement An existing feature or its usability needs improvement
Suggestion A new feature or approach is proposed
Question Clarification about behavior or policy is needed

Before you register

Check these five points before selecting the register button.

  • Can someone understand the location and symptom from the title alone
  • Can another person follow the steps to reproduce exactly
  • Are the actual and expected results clearly separated
  • Did you select the test environment used for this test
  • Are the evidence files free of sensitive information
05

Track the handling

Check the handling history, the participants, and the current status on the detail page of the issue you registered.

Review a registered issue

After registration the detail page opens and the initial status is Received.

Detail page for a received issue
  1. 1 Check the issue type, priority, and current status at the top.
  2. 2 Review the description, attachments, comments, and status history in the Activity section. The reporter can edit the content with the pencil button.
  3. 3 Check the reporter, the dates, the latest activity, and the test environment attached to the issue in the Information section.
  4. 4 Check the participants and the assignee of this issue in the Participants section.

The issue list shows the title, type, priority, status, comment count, and latest activity time.

Participants and assignees

Each issue has its own participants, and comment and status-change notifications go to them.

How participants are decided
  • Registering an issue adds you to its participant list as the reporter.
  • Use [Manage assignees] to designate who handles the issue.
  • Only participants of an issue can add comments or change its status.
  • Even without being a participant, you can view and search the issues registered in the same service.

Comment and status-change notifications are sent to the reporter and active participants, excluding the user who performed the action.

Understand statuses

After reviewing an issue, the assignee updates its status and notes. The reason for each change is shown in the Activity section.

Status Meaning What to check
Received Registration complete Wait for the assignee to review it.
In progress Assignee is handling it Answer in a comment if there are further questions.
Information requested The assignee has asked for clarification Answer the question in a comment.
Completed The assignee has finished the work Review what was changed.
Verification requested Retest required after a fix Retest under the same conditions.
On hold Handling temporarily paused Provide any requested information.
Closed Handled and closed Confirm that the problem has been resolved.
Reopened Problem persists Add the reproduction result and supporting evidence.

Depending on the service settings, the assignee may close an issue directly without the verification stage.

Comment guidelines
  • When answering the assignee, include the reproduction environment and the result.
  • Comments can also include up to 5 files, up to 10 MB each.
  • You cannot add new comments or edit existing ones on a closed issue.
  • If more explanation is needed, reopen the issue first.
06

Verification and closing

When verification is requested, retest under the same conditions and close or reopen the issue based on the result.

Review a verification request

When the status changes to Verification requested, review the assignee's fix and notes. You record the result with the two buttons at the top of the detail page.

Add comment and Change status buttons at the top of the issue detail page
  1. 1 [Add comment] leaves a message and changes the status at the same time, while [Change status] only changes the status.
Retest procedure
  1. Confirm that the fixed app or service version has been deployed.
  2. Repeat the original test environment and reproduction steps exactly.
  3. Check whether the actual result matches the expected result.
  4. Select Close if it is resolved, or Reopen if it still occurs.

Comments and status changes

Leave the retest result in a comment and then change the status.

Add comment dialog and Change status dialog
  1. 1 In [Add comment], enter the text and attachments, choose the new status below, then select [Post comment].
  2. 2 In [Change status], choose the status and leave a note. The note is optional.
Reopen note example

Retested on Android 15 with app version 2.4.1, but the same problem still occurs. A newly captured screen is attached to the comment.

Close or reopen

Choose one of the two based on the retest result. The new status appears in the badge under the title and in the activity history.

Status badge and status change history
  1. 1 The current status appears in the badge under the title.
  2. 2 The Activity section keeps the order and time of every status change.
When to close
  • The problem no longer occurs in the fixed version with the original reproduction steps.
  • The actual result matches the expected result.
  • The same problem does not occur in related key features.
When to reopen
  • The same problem continues to occur.
  • It is resolved only under some conditions, or still reproduces in another environment.
  • The fix caused a new problem in the same feature.

If the symptom, the steps, or the cause clearly differs from the existing issue, register a new issue instead of reopening it.

Final checklist
  • Searched for duplicate issues
  • Wrote a title that identifies the location and the symptom
  • Separated the steps to reproduce, actual result, and expected result
  • Selected the test environment used for this test
  • Attached the necessary screenshots or logs
  • Checked attachments for sensitive information
  • Retested under the same conditions when verification was requested
  • Closed or reopened the issue based on the verification result