> For the complete documentation index, see [llms.txt](https://docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbase.ai/program-guide/bug-bounty-dashboard/program-reports-section/duplicating-reports.md).

# Duplicating Reports

A duplicate report refers to a report that describes a vulnerability or issue that has already been reported and is being tracked by the program manager. This can occur when multiple hackers discover the same vulnerability and submit a report for it.

There are two ways to mark a report as duplicate in BugBase:

1. **Original Report ID**: When a program manager receives a report that is a duplicate, they can mark it as such by providing the original report ID. This allows program managers to easily link the duplicate report to the original report, making it easier to track and manage the issue.
2. **Issue Ticket Screenshot**: If the company is already aware of the issue, program managers can provide a screenshot of the issue ticket as proof that the issue was already known. This allows program managers to quickly verify that the issue has already been reported and is being tracked by the company.

<figure><img src="/files/B0YRUI6AT2aBkjozyqAv" alt=""><figcaption></figcaption></figure>

It is important to mark a report as duplicate as it helps program managers to avoid duplicate effort and prioritize the most important vulnerabilities.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bugbase.ai/program-guide/bug-bounty-dashboard/program-reports-section/duplicating-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.