---
description: Describes the process of reporting a bug to the cQube Product Team
---

# Reporting a Bug

There is a bug if something for the user isn’t working as intended. The cQube Product Team will be responsible to fix the bug that has been reported in the DPG.

### Communication Tool

All the bugs and need for support should be posted as issues on the cQube Community on GitHub - [Link](https://github.com/Sunbird-cQube/community/issues).

### Reporting a Bug

A new issue should be created in the GitHub Community of cQube **only** if any similar issue doesn't already exist or has been resolved by the cQube Product Team. The reported issues for cQube can be seen [here](https://github.com/Sunbird-cQube/community/issues?q=is%3Aopen+is%3Aissue) and the resolved issues can be seen [here](https://github.com/Sunbird-cQube/community/issues?q=is%3Aissue+is%3Aclosed).

**Process to report a bug:**

1. Go to the issues tab of cQube Community on Github - [https://github.com/Sunbird-cQube/community/issues](https://github.com/Sunbird-cQube/community/issues)

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2FTZVdoxEeHLvJPTIG6T9k%2Fimage.png?alt=media&#x26;token=8a8471d8-8b9d-4659-a163-3481ff1db4fd" alt=""><figcaption></figcaption></figure>

2. Click on 'New Issue'. Then select 'Get Started' in front of 'Bug report'.

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2FffY5lAYFh81lHsIvbMPr%2Fimage.png?alt=media&#x26;token=56a82031-b89c-4aa4-9f8c-7645ebc2e430" alt=""><figcaption></figcaption></figure>

3. Detail out the bug that you are facing with a title, description, steps to reproduce, expected behaviour, relevant screenshots and desktop / mobile configurations.

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2F1ILkIjHGAC4wBKej5yHS%2Fimage.png?alt=media&#x26;token=caff9223-529e-4fe1-acb4-5bc0a34f6f1f" alt=""><figcaption></figcaption></figure>

4. Attach relevant label(s) to the bug being reported.

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2FdMfAKX3tC1dAAQrYO4fq%2Fimage.png?alt=media&#x26;token=a3cd8206-4b45-4570-ae7e-a28b6c90e5b6" alt=""><figcaption></figcaption></figure>

5. Click on 'Submit new issue'.

### Response from the cQube Product Team

The cQube Product Team will respond within 2-3 working days post the issue has been submitted with a timeline by when the bug can be fixed. It will be included in the cQube roadmap. The adopter who has raised the issue will be able to track the bug on a JIRA ticket.

Ideally, P0 bugs will be prioritised and taken up in the ongoing sprint and P1 bugs will be taken up in the next sprint based on when the issue is reported.&#x20;
