> For the complete documentation index, see [llms.txt](https://docs.eu-pactum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eu-pactum.com/campaigns/issue-tracker.md).

# Issue Tracker

**What is the Issue Tracker?**

The Issue Tracker is a feature designed to bring a transparent, centralized, and structured approach to managing all negotiation-related tasks, questions, and follow-ups. It aims to provide a single source of truth for all stakeholders, ensuring that nothing falls through the cracks.

By managing these items directly within the Pactum Suite, the Issue Tracker makes sure every issue has a clear owner, a documented resolution, and a complete history, eliminating the need for scattered email threads or spreadsheets.

The Issue Tracker is now being progressively rolled out across Campaigns workspaces, and soon beyond. If you don't see it yet, you should be hearing from your engagement manager shortly.

**What is an issue?**

An issue is an item of work that needs resolution before a negotiation (or other normally automated process) can continue. It may require input or action from your organization, Pactum, or both. The issue contains the relevant details, history and actions required to efficiently achieve a resolution.

***

### Accessing the Issue Tracker

You can access issues three ways:

* **Issues Tab**: In the Suite, on the negotiation list view of a workspace, you will see "Issues" as a tab at the top of the list. Click this to see a list of all issues for your workspace.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FpEeMYxFcw0YKbFkrceLA%2FScreenshot%202025-09-02%20at%2001.06.58.png?alt=media&amp;token=8bfd458c-ea75-45f4-b47e-ab3cedbe22a1" alt=""><figcaption></figcaption></figure>

* **From a Negotiation:** When viewing a negotiation's details, the bottom-left corner of the page lists all issues related to that negotiation. You can click any issue to go directly to its details view.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2F7hh7Kyj4nKl2femldgaq%2FScreenshot%202025-09-04%20at%2015.37.17%20copy.png?alt=media&amp;token=b39e67dc-2b94-43c6-aee5-297ece647c4d" alt=""><figcaption></figcaption></figure>

* **Direct URL**: Every issue has a unique URL that can be bookmarked or shared. The end of the URL is the Issue ID. **Every time an issue is assigned** to a User, that **assignee** user **gets** **an** **email** **notification** with a direct link to the issue.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FkgjJPlR6Tr0RB72GYOCV%2FScreenshot%202025-09-04%20at%2015.17.14%20copy.png?alt=media&amp;token=c1a926fe-411f-41f0-936a-5d382398384d" alt=""><figcaption></figcaption></figure>

#### How to report an Issue

Issues can only be created on negotiations that have already Started.\
Open a Negotiation's Summary view and press the '`Report an issue`' button at the bottom-left corner. This will open a pop-up where you can specify the type of issue and add a first note.\
Creating (Reporting) an Issue will open the issue's Details view where you can add additional information, reassign and save.

Steps:

1. Open a Negotiation's Summary view
2. Press `Report an issue`

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FpIEMx7rpBa52MozDNjsx%2FScreenshot%202025-08-13%20at%2014.33.56.png?alt=media&amp;token=32c46b18-fa06-48a4-b484-ecb182067df3" alt=""><figcaption></figcaption></figure>

3. A panel to input more info about the issue appears
4. Pick an Issue `Category` from the dropdown
5. Add/edit `notes` if needed
6. Initial `assignee` is determined automatically, but you can change it if needed
7. Pressing `Report issue` creates the issue. (Once created, Issues can't be deleted, but they can be Closed if created by mistake. )

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FjZssOcTKASY3Ca6wGMdE%2FScreenshot%202025-09-02%20at%2001.16.10.png?alt=media&amp;token=aef584b9-392a-46c0-a4b2-76e52eac9d8f" alt=""><figcaption></figcaption></figure>

***

### The Issue Lifecycle: From Open to Closed

Every issue follows a 3-step status workflow, ensuring a smooth handoff between your team and Pactum.\
When an issue has been **assigned to you** and is either in the **Open** or **Pending** **Review** status - it means some actions are needed from your end.

**1. Open**

An issue is `Open` when it is active and requires action from the current assignee. This is the initial state for all newly created issues before a Resolution has been submitted. Pactum internal users can change issues back into this state if necessary.

**2. Pending Review**

An issue moves to `Pending Review` after the Client has chosen (and Saved) a Resolution. When a client selects a **Resolution** Type from the dropdown menu and Saves, the issue is **automatically** reassigned to the Pactum team. This status indicates that the client's part is done and the issue is now awaiting a final review and follow-up from Pactum before it can be closed.\
Sometimes Suppliers have additional questions or requests that relate to the same issue. In these scenarios the same issue will be assigned back to Client's team. From Client's view you can identify these bounced-back issues by them being assigned to you (the Client) and the issue being in the `Pending Review` status.

**3. Closed**

An issue is `Closed` when all actions are complete and the task is fully resolved. The issue is then archived for reporting purposes. Issues are typically moved to the `Closed` status by a Pactum team member after the final review is complete. If you know an issue was purely informative or requires no next steps from Pactum team, you can close it yourself.

***

### Key Features

**The Issues List**

The main list view is your command center for tracking all issues for a workspace. From here, you can click on each Issue's row to dive into that issue's details.\
You can sort most columns by ascending/descending by clicking on the column's title.\
The top of the page has filters<img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FrfoGDS5W8Zz7neLMylc6%2Fimage.png?alt=media&amp;token=75d1084e-b9c7-4e79-9535-b635070f8d73" alt="" data-size="line"> - to quickly find what you need. Most often you should pick yourself from the `Assignee` filter and sort the list by `Issue deadline` column to see most urgent issues first. All issues assigned to you that aren't in a Closed status, should be checked.\
Columns can be toggled on or off if you're low on screen space via <img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FN8Kia7DWvu8tfVrfuEv9%2Fimage.png?alt=media&amp;token=d70fd479-ff57-4167-bc1b-50b64d040e92" alt="" data-size="line">.\
The `Actions` column allows to do some direct actions (Reassign, pick Resolution, Close) for each issue without opening the issue details view .\
All issue data can be downloaded from the Issues List view as a .csv file for a more detailed analysis via <img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2F7NJcjfyDZee2vQfal5Vj%2Fimage.png?alt=media&amp;token=6a97aa08-ec65-441e-ac4b-d7050a3d27d3" alt="" data-size="line">.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2Fiz1gxxL1AjzTzhmarlTs%2FScreenshot%202025-09-02%20at%2015.28.50.png?alt=media&amp;token=b50a2ba6-d2f7-4979-96fe-70b9f8838dcd" alt=""><figcaption></figcaption></figure>

**The Issue Details Page**

This page provides a three-column view of a single issue.

* Left Panel (Issue Details & Tags): Contains all the core data about the issue, including the `Supplier contact`, `Issue creator`, `Issue Category`, and a direct link back to the `Negotiation Summary`. Here you can pick a `Resolution`, choose to reassign the issue via changing the `Assignee` , add `Tags` , or change `Issue category` if the original one has changed. Only 'User' role users show up in the Assignee list (Viewers don't).
* Center Panel (Notes & Files): This is the main collaboration space. Users can add notes and upload files. As a best practice, a note should be added every time a meaningful action is taken (e.g., choosing a resolution, reassigning the issue) to maintain a clear record and help the future assignee determine the next steps.
* Right Panel (History): A complete, time-stamped audit trail of actions taken on the issue, including status changes, new notes, and reassignments.

These are the **main actions to take on this page**:

1. **Read** through previous notes to understand the issue.
2. Determine if you know the answer and can **Resolve** the issue **or** need to **reassign** it to someone else in the company (with a corresponding note).
   1. If you need more information from Pactum's team to determine the Resolution, please:
      1. Write a Note with your questions. Click `Save Note` to enter the note and associated files.
      2. Pick 'Pactum Support Agent' from the `Assignee` dropdown menu in the left panel.
      3. Click `Save changes` . Pactum team will then review the notes and assign the issue back with additional information.
3. Once the Issue is with the person that can determine a Resolution for it:
   1. Pick a `Resolution` from the dropdown menu on the left. This will automatically reassign the issue back to Pactum Support Agent.
   2. **Add a Note** to explain the Resolution and/or upload files in `Notes` section
   3. Enter your notes and files via `Save note` (you can add multiple notes and files and delete past notes and files).
   4. Press `Save changes` at the top of the page to save the Issue Details changes.
   5. Once Resolution is picked and saved, the `Assignee` changes **automatically**. Check that the automatically chosen Assignee is correct one for your situation.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2F5dngMUnxsyzD8TYSU1ZR%2FScreenshot%202025-09-02%20at%2001.19.42%20copy.png?alt=media&amp;token=469e68dd-074f-4bf5-bca3-260f28212c7b" alt=""><figcaption></figcaption></figure>

\
Action buttons on the top right:

* '`Save changes`' - every time you're finished with your changes on the Issue Details view, 'Save changes' should be pressed.
* '`Mark issue as Closed`' - further steps from Client or Pactum's side aren't necessary. Issue can be archived. When a Closed issue needs to be reopened, Pactum internal users have the ability to do that. Generally only a `Resolution` needs to be picked, Notes added, and `Save changes` pressed, Pactum team will handle the rest.

\ <br>

**The Issue Dashboard Page**\
\
For general statistics, the Dashboard view now also has an Issues tab for Issue Tracker related information. The Issue Tracker Dashboard displays charts depicted in the picture below.\
Charts can be filtered by an Issue's category, date range, and the time-based group can be changed. These filters affect all charts.

<figure><img src="https://2769938103-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FM7KTpbu7nDWmneLhlf%2Fuploads%2FT3gY0OUCkYPB4N73pCen%2FScreenshot%202025-09-02%20at%2016.46.17.png?alt=media&amp;token=0f498341-84c7-4217-8385-0304c114621b" alt=""><figcaption></figcaption></figure>

###
