Issues in PayStar: how to create and track tasks

How to create, correct, and accept tasks

1) Where to find the Issues section and what it looks like

Issues is a Kanban board with status columns. Each card is a separate task (issue).

2) Issue statuses and how tasks move through the board

In PayStar, the following statuses are typically used:

Draft — a draft (created, but not taken into work yet)

Development — in development

Testing — in testing

Requires acceptance — waiting for acceptance from the requester

Success — completed

What to do in “Requires acceptance”

If an issue has moved to Requires acceptance, it means the team considers the work done and is waiting for:

an “OK” confirmation in the comments; or

your feedback with specifics (what is wrong and what the expected result is).

3) Creating a new issue: step by step

Open Issues

Click Add issue

Select Source* (the “issue location” wizard)

Fill in the required fields (marked with *)

Optionally set Priority and Owner

Click Add

4) Source — a multi-level “issue location” wizard

Source is a multi-level wizard that localizes the “place” of the issue and shows which fields are required for that particular location.

How it works:

you choose where the issue belongs;

the form automatically adds the required fields and constraints.

5) Source options and when to use each one

5.1) Head — admin panels

Choose Source = Head if the issue relates to the admin panel (operations, finance, reports, reconciliations, gateways, limits, etc.).

After selecting Head, the Head* field appears — it’s the admin module/section where the issue belongs.

5.2) MerchHead — merchant cabinet

Choose Source = MerchHead if the issue relates to the merchant cabinet (settings, merchant reports, access, payments, notifications, etc.).

Just like for Head, the system will ask for the relevant module/section and required fields.

5.3) API — documentation

Choose Source = API if the issue relates to API documentation:

endpoint descriptions,

schemas and fields,

request/response examples,

enums,

error texts,

FAQ.

5.4) Integration — creating an integration task

Choose Source = Integration when you need to create a task for a provider/gateway/PSP integration. This option uses an extended form with required fields so the team can start without back-and-forth clarifications.

Common required fields include:

Gateway name + direction* (e.g., Bank name — deposit P2P)

Tech contact* (email / @telegram)

Test API key* and Prod API key*

API Doc* (link/file)

Available balance for test*

Card for test* (or test credentials/data for the method)

6) Important: “Head” is used in two different meanings

To avoid confusion:

Source = Head — the location (admin panel)

Head* field — the module/section within that location

Hint: Source = location, Head = module*.

7) How to write Subject and Description correctly

Subject — issue title

Subject should be short and clear: action + context.

Examples:

“Add an amount filter”

“Transactions: cannot change status”

“Integration: 500 error on payout”

Description — detailed information (template)

Recommended structure:

Context: Source + module (Head*), provider/method/currency (if applicable)

Steps to reproduce: 1) … 2) … 3) …

Expected: what should happen

Actual: what happens now

Data: Order/Payment ID, external_id, gateway_id, time/timezone

Evidence: screenshot/video/log/file

8) Priority and Owner: how to use them

Priority

Recommendations:

Highest — blocker (money, conversion, production incident, operations stopped)

Medium/High — important, but not blocking

Low — non-critical

Owner

Owner is the person responsible for driving the task to completion. This reduces the risk of “unowned” issues and helps manage the queue.

9) Attachments and Comments

Attachments

You can attach files inside the issue card:

drag & drop, or

click Choose a file.

Comments

Use comments for:

clarifications,

test results,

acceptance,

links to logs/artifacts.

10) Search and filters: how to quickly find an issue

The board header provides filters and search such as:

Status

Issue ID

User

Owner

Created

Search

To reset everything — click Clear Filters.

11) Common mistakes and how to avoid them

Typical mistakes:

selecting the wrong Source → the form does not collect required data;

missing Head* for Head/MerchHead;

no reproduction steps and no “expected vs actual”;

no identifiers (Order/Payment ID, external_id) and no evidence (logs/screenshots);

for Integration: missing docs/contact/keys/test data.

Do not paste secrets in plain text into Description or Comments.
Use Protected data (one-time secret) or the built-in “secret” button (if available in the form) to limit lifetime and the number of views.

Issues (Tickets)

How to create, correct, and accept tasks#

1) Where to find the Issues section and what it looks like#

2) Issue statuses and how tasks move through the board#

What to do in “Requires acceptance”#

3) Creating a new issue: step by step#

4) Source — a multi-level “issue location” wizard#

5) Source options and when to use each one#

5.1) Head — admin panels#

5.2) MerchHead — merchant cabinet#

5.3) API — documentation#

5.4) Integration — creating an integration task#

6) Important: “Head” is used in two different meanings#

7) How to write Subject and Description correctly#

Subject — issue title#

Description — detailed information (template)#

8) Priority and Owner: how to use them#

Priority#

Owner#

9) Attachments and Comments#

Attachments#

Comments#

10) Search and filters: how to quickly find an issue#

11) Common mistakes and how to avoid them#

12) How to securely share keys and passwords#