> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/helpdesk/cases.md).

# Cases

Learn about cases and how to manage them in the SoftwareOne Marketplace.

A case is a support request or inquiry created when you need more information or help with an issue. Cases allow you to communicate with SoftwareOne and track the progress of your request.

Each case includes important details, such as the case ID, reporter, assignee, status, and the conversation between you and the assignee or individual handling your case. As the issue is reviewed, the case status is updated so you can monitor its progress.

In the SoftwareOne Marketplace, each case includes a conversation thread, also called case chat, that lets you communicate with the assignee handling your case. 

### Cases page

You can view and track your cases through the **Cases** page. From this page, you can also add a case using the **Add** option.

To open the page, choose **Helpdesk** > **Cases** from the main menu.

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FglWSaupWPFL9u6K6f6Bv%2Fimage.png?alt=media&amp;token=c73a7b24-a833-45ee-85b0-75c341f82987" alt=""><figcaption><p>Use the Cases page to add, view, and manage cases.</p></figcaption></figure></div>

On the **Cases** page, you can use the **Actions** column to mark a case as completed. You can also select a case ID to view its full case details and perform case‑management actions.

### Related topics

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/RQbBsq7E39OIZYkcZNvN" %}
[Case states](/modules-and-features/helpdesk/cases/case-states.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/W2kKHl0SQ8yTO4ZSO4b6" %}
[Create case](/modules-and-features/helpdesk/cases/create-case.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/mUna5UXgiYpvRbL4er4j" %}
[View cases](/modules-and-features/helpdesk/cases/view-cases.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/BXREGZxMUdCcJWf5Lty1" %}
[Reopen case](/modules-and-features/helpdesk/cases/reopen-case.md)
{% endcontent-ref %}

{% content-ref url="/spaces/Z5DNbniz33mXCZoO62Rm/pages/XegxwQn6bx4mvXyD6Yiq" %}
[Complete case](/modules-and-features/helpdesk/cases/complete-case.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/modules-and-features/helpdesk/cases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.