> For the complete documentation index, see [llms.txt](https://docs.morpht.com/convivial-for-govcms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morpht.com/convivial-for-govcms/support/morpht-issue-queue.md).

# Morpht issue queue

Morpht builds and maintains Convivial for GovCMS. Bugs, questions about how something works, and requests for changes are tracked in Morpht's issue queue, which gives every request a number, an owner and a visible status.

If your agency is a Morpht client, you will be invited to the issue queue and given a project as part of onboarding; ask your Morpht contact if you do not have a login.

## Raising an issue

Create a new issue in your project with:

* **Tracker** — *Bug* for something broken, *Feature* for something new, *Support* for a question.
* **Subject** — one line saying what and where, e.g. *Accordion does not open on the Permits page*.
* **Description** — the page address, the steps to reproduce, what you expected and what happened, and a screenshot if it is visual. Say which environment, and whether it affects visitors or only editors.
* **Priority** — reserve *Urgent* for the live site being wrong for visitors.

You will get email updates as the issue moves through *New → In progress → Resolved → Closed*, and you can reply on the issue at any point — that is better than a separate email, because the whole history stays in one place.

## Before raising one

Check this guide for the component or setting in question, and check whether the same thing happens on the test environment — a difference between the two usually points at content or configuration rather than code.