Is your feature request related to a problem?

When developers create issues, the description field is always blank with no guidance. This leads to inconsistent issue quality — some issues lack critical context such as the reason for the change.

Describe the solution you'd like

Allow project admins to configure a default description template in the project settings. When a developer opens the issue creation form, the description field should be pre-filled with the template text (editable, not enforced).

Example template:

## Reason for Change
<!-- Why is this change needed? e.g. Add index to improve query performance -->

## Review Points
<!-- Any concerns reviewers should be aware of? e.g. This change affects the billing flow -->

## Related Tickets
<!-- e.g. JIRA-1234 -->

Additional context

Similar features exist in other tools:

GitHub Issues: issue templates per repository
GitLab: issue description templates per project
Linear: issue templates

A workaround using a bookmarklet to inject text into the description field is possible, but it's not a first-class feature.