> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/enterprise/raising-support-tickets.md).

# Raising Support Tickets

## Overview

Raise a support ticket to report a bug or incident, ask a question, or request a feature. AttackForge Enterprise customers raise tickets in [Backlog](https://nulab.com/products/backlog/), where you can follow progress and talk to the support team.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FX7BOVczlqaYxtxYQbwc5%2Fraising-support-tickets-at-a-glance.svg?alt=media&amp;token=db69e0e8-91b3-4d6a-954e-514e62ef62c7" alt=""><figcaption></figcaption></figure>

## Choose how to get help

| You have                   | Get help by                                                                        |
| -------------------------- | ---------------------------------------------------------------------------------- |
| **AttackForge Enterprise** | Raising a ticket in your organisation's Backlog project, as described on this page |
| **AttackForge Core**       | Emailing <support@attackforge.com>                                                 |

## Why it matters

| Benefit                    | What it means                                                                       |
| -------------------------- | ----------------------------------------------------------------------------------- |
| **Faster fixes**           | A clear ticket with steps to reproduce lets support find and fix the problem sooner |
| **The right urgency**      | Choosing the right priority makes sure critical issues get attention first          |
| **One place to follow up** | Track progress, add details and see replies on the ticket                           |
| **Your team sees it too**  | Your organisation's tickets are kept together in its own Backlog project            |

## Who uses it

| Role                                          | Typical use                                                    |
| --------------------------------------------- | -------------------------------------------------------------- |
| **AttackForge administrators**                | Report incidents, and request access to Backlog for their team |
| **Testers, consultants and project managers** | Report bugs and ask questions                                  |
| **Product owners and security leaders**       | Request features                                               |

## Get access to Backlog

If you are an Enterprise customer, you will automatically receive an invitation to our workspace on Backlog.

If you have not yet received an invitation, please contact your AttackForge tenant administrators to request access.

When you log in, your dashboard shows the projects you can access. Each organisation has its own project for its tickets.

## Before you raise a ticket

* **Check it's a new issue.** Search your organisation's project for an existing ticket about the same problem.
* **Try to reproduce it.** Note the exact steps, and whether it happens every time.
* **Gather evidence.** Take screenshots, and note the page, the time and any error message.
* **Choose the priority.** See Choose a priority.

## Raise a ticket

1. Log in to Backlog, and click your organisation's project on the dashboard.
2. Click **Add Issue**.
3. Select the priority. See Choose a priority.
4. Enter the details of your request. For a bug, include the information support needs.
5. Upload screenshots, to help support troubleshoot faster.
6. Click **Add**.

A confirmation message appears. The support team will then work to resolve your incident or bug, or respond to your enquiry or feature request.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FXOorTfqc6IjQQzURMqoR%2Fimage.png?alt=media&amp;token=9de45c73-0e54-4275-b6ca-5a08d2638d42" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FyEWYwLPk2rBFbTnsWNOR%2Fimage.png?alt=media&amp;token=0e7e7cfb-22d6-4650-876c-0fb6965c79e3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FHWozmyijRf7PSdlWqz7v%2Fimage.png?alt=media&amp;token=a44924a3-e1ff-4b09-8ee5-9670c133be22" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F1pCTF0FNJqEN0nj5NycZ%2Fimage.png?alt=media&amp;token=75b21e5a-4f49-43bc-948c-d35f052fa7f7" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FUtOUKFfTyqQ1AHxFH26S%2Fimage.png?alt=media&amp;token=bf598b0e-52f7-4d6c-b788-10fe926b8479" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fx21tP0IMRMGUjDCIJjYL%2Fimage.png?alt=media&amp;token=24fad32f-ff0d-4ad5-a1d8-a6398c6ce9fb" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FhZ1S3km3L6tu96s4tnrA%2Fimage.png?alt=media&amp;token=cd169132-4c42-4c0a-86b2-817a09e3770b" alt=""><figcaption></figcaption></figure>

### Choose a priority

| Priority                             | Definition                                                                                      | Examples                                                                                                                                                              |
| ------------------------------------ | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Priority 1 Incident: CRITICAL**    | Security incident or application not working. Support will work with you 24x7 until resolution. | Application is down · Users cannot log in · Security incident                                                                                                         |
| **Priority 2 Incident: HIGH**        | Defects affecting core functionality resulting in limited use of AttackForge.                   | Cannot create a Project or Project Request · Cannot create a Vulnerability · Cannot download a Report                                                                 |
| **Priority 3 Incident: MEDIUM**      | Defects affecting non-core functionality. No major impact to ability to use AttackForge.        | Cannot clone a Project · Cannot create a Writeup · Cannot update a Test Case                                                                                          |
| **Priority 4 Incident: LOW**         | Minor bugs or defects.                                                                          | Cannot update a single field on a record · User interface limitation, for example table loading incorrectly or filtering not working · Application performance issues |
| **Priority 5 General Request: INFO** | Feature requests and general enquiries.                                                         |                                                                                                                                                                       |

### Information support needs for a bug

For bugs, please ensure to include the following information otherwise your ticket may be delayed or rejected.

| Field                  | What to include                                                                                                                                                                                                   |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Description**        | Include detailed information relating to the incident or bug. This should include the page it is observed on, the activities performed leading to the bug, any specific data you entered triggering the bug, etc. |
| **Steps to Reproduce** | This is Important! We need to be able to reproduce the issue otherwise we may be limited in fixing it for you. Please include detailed steps to reproduce the bug.                                                |
| **Expected Outcome**   | Include information relating to what you were expecting the functionality to do                                                                                                                                   |
| **Observations**       | Include information relating to the actual outcome and what you had observed.                                                                                                                                     |

*Example, for illustration:*

> **Description:** On a project's Vulnerabilities page, the Priority filter shows no results after I select High.
>
> **Steps to Reproduce:** 1. Open any project with High vulnerabilities. 2. Go to Vulnerabilities. 3. Filter by Priority: High.
>
> **Expected Outcome:** The table lists the project's High vulnerabilities.
>
> **Observations:** The table is empty. Clearing the filter shows them again. Happens every time, in Chrome and Edge.

## Tips

* **One issue per ticket.** Separate tickets are easier to track and resolve.
* **Write a clear title.** Say what's wrong and where, such as "Priority filter shows no results on Vulnerabilities page".
* **Include the steps to reproduce.** It's the most important part of a bug report.
* **Add screenshots or a short screen recording.** Hide any sensitive data first.
* **Say what you've already tried,** such as another browser or clearing the cache.
* **Note when it happened,** including the time zone, so support can check the logs.
* **Choose the priority honestly.** Save Priority 1 for outages and security incidents, so they get the fastest response.
* **Don't share passwords or API keys** in a ticket.

## FAQ

**I'm an Enterprise customer, but I don't have a Backlog invitation. What should I do?** Contact your AttackForge tenant administrators to request access.

**I'm a Core customer. How do I get support?** Email <support@attackforge.com>.

**Which priority should I choose?** Use the priority table. Priority 1 is for outages and security incidents; Priority 5 is for feature requests and general enquiries.

**Is support available outside business hours?** For Priority 1 incidents, support will work with you 24x7 until resolution.

**Why was my ticket delayed or rejected?** Bug tickets need a description, steps to reproduce, the expected outcome and your observations. Without them, support may not be able to fix the issue.

**Can my colleagues see my tickets?** Each organisation has its own Backlog project, so other people from your organisation with access can see its tickets.

**How do I request a feature?** Raise a ticket with **Priority 5 General Request: INFO**.

## Related pages

* [Backlog](https://nulab.com/products/backlog/): the ticketing tool AttackForge uses.
* [Backlog help: Add an issue](https://support.nulab.com/hc/en-us/categories/4402869930649-Backlog): Backlog's own guide.
* [Administration](https://support.attackforge.com/app/modules/administration): manage your AttackForge users and settings.


---

# 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://support.attackforge.com/enterprise/raising-support-tickets.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.
