# Capture 2.0 - Coming soon!

In our continuous pursuit of enhancing user experience and addressing your needs, we are thrilled to announce that Capture team is diligently working on a new and improved version of Capture. This upcoming release is designed to revolutionize the way you handle bug reports, bringing in a host of new features and capabilities to streamline 🤝 **collaboration, 💬 communication, and  💪efficiency.**

**What to expect:**

**Make it work your way:** Capture will retain the simplicity and ease of use that you're accustomed to: clean UI, videos or screenshots with actions, console and network information. However, users will now have the ability to customize their bug reporting experience, tailoring it to their specific needs and workflows by adding description, custom fields or labels.

<figure><img src="https://3224922151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRq7JtkYswaRrJ1pOtPc7%2Fuploads%2FJeU8LASvNA9RRv1oGmWg%2Fimage.png?alt=media&#x26;token=53ea2303-2340-4f6d-b278-735f5967177c" alt=""><figcaption></figcaption></figure>

**Enhanced collaboration:** One of the most exciting features of the upcoming version is the ability to invite other users to collaborate on the tickets. This means that your team can work together seamlessly, sharing insights, assigning tasks, and collectively resolving issues. Collaboration has never been easier.

<figure><img src="https://3224922151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRq7JtkYswaRrJ1pOtPc7%2Fuploads%2FVWradgICeBLaTeXyoP0l%2Fimage.png?alt=media&#x26;token=4dc2e9c3-d9af-4c46-bfdd-ea8547da91e1" alt=""><figcaption></figcaption></figure>

**Real-time comments:** Communication is key when it comes to issue resolving process. With the new version, users can leave real-time comments. This feature facilitates a dynamic conversation thread, allowing team members to discuss issues, share ideas, and propose solutions directly within Capture.

<figure><img src="https://3224922151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRq7JtkYswaRrJ1pOtPc7%2Fuploads%2F1XxCcX4pELO8e9YHBd1l%2Fimage%2044.png?alt=media&#x26;token=a9d7b237-e0ae-4d96-8ad6-28c8934402dc" alt=""><figcaption></figcaption></figure>

**Version history:** We understand the importance of keeping track of changes. **Capture 2.0** will include a comprehensive version history feature, providing users with a chronological overview of all modifications made to a bug report. This not only enhances transparency but also aids in identifying when and how issues were addressed.

<figure><img src="https://3224922151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRq7JtkYswaRrJ1pOtPc7%2Fuploads%2FVUBvZDPxVWO7qRKEDkHH%2Fimage.png?alt=media&#x26;token=c471c51d-4ef6-4ce5-b435-70266fd4f316" alt=""><figcaption></figcaption></figure>

**Unlimited number of captures:** Reporting bugs has never been more versatile. The upcoming version removes limitations on the number of captures, empowering users to thoroughly document and showcase every aspect of a bug. This is particularly beneficial when the team is  big and your project is complex or at the very early stage whre a lot of testing required and reporting and quickly fixing bugs is crucial.

<mark style="color:blue;">As we embark on this exciting journey toward a more advanced bug reporting solution, we are confident that these upcoming features will significantly elevate your bug tracking experience. We are committed to delivering a tool that not only meets but exceeds your expectations. Stay tuned for the release, and get ready to embrace a new era of collaborative bug resolution!</mark>


---

# Agent Instructions: 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:

```
GET https://docs.usecapture.io/help-articles/capture-2.0-coming-soon.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.