---
title: "Tuairisciú fabhtanna agus gnéithe"
version: 6.1
locale: ga
source: https://docs.djangoproject.com/ga/6.1/internals/contributing/bugs-and-features/
canonical: https://djangodocs.dev/ga/6.1/internals/contributing/bugs-and-features/
---
# Tuairisciú fabhtanna agus gnéithe

> **Important**
>
> Please report security issues **only** to
> `security@djangoproject.com`. This is a private list only open to
> long-time, highly trusted Django developers, and its archives are
> not public. For further details, please see [our security
> policies](/ga/6.1/internals/security/).

## Fhabhtanna a thu

Before reporting a bug on the [ticket tracker](https://code.djangoproject.com/) consider these points:

- Check that someone hasn't already filed the bug report by [searching](https://code.djangoproject.com/search) or
  running [custom queries](https://code.djangoproject.com/query) in the ticket tracker.
- Don't use the ticket system to ask support questions. Use the [Django Forum](https://forum.djangoproject.com/)
  or the [Django Discord server](https://chat.djangoproject.com) for that.
- Don't reopen issues that have been marked "wontfix" without finding consensus
  to do so on the [Django Forum](https://forum.djangoproject.com/).
- Don't reopen issues that have been marked "needsnewfeatureprocess" without
  shepherding an issue through the [new feature ideas](https://github.com/orgs/django/projects/24/) GitHub project.
- Don't use the ticket tracker for lengthy discussions, because they're
  likely to get lost. If a particular ticket is controversial, please move the
  discussion to the [Django Forum](https://forum.djangoproject.com/).

Tá tuairiscí fabht dea-scríofa \* thar a bheith cabhrach. Mar sin féin, tá méid áirithe lasbhairde bainteach le hobair le haon chóras rianaithe fabht ionas go bhfuil meas ag do chabhair lenár rianaitheoir ticéad a choinneáil chomh úsáideach agus is féidir. Go háirithe:

- **Déan** léigh an:doc: FAQ chun a fháil amach an bhféadfadh do cheist a bheith ina cheist aithe\</faq/index\> anta.
- **Do** ask on [Django Forum](https://forum.djangoproject.com/) or the [Django Discord server](https://chat.djangoproject.com) *first* if
  you're not sure if what you're seeing is a bug.
- **Déan** tuarascálacha fabht iomlána, in-atáirgthe, a scríobh. Caithfidh tú cur síos soiléir, gonta ar an bhfadhb a áireamh, agus sraith treoracha chun í a mhacasamhlú. Cuir an oiread faisnéise dífhabhtaithe agus is féidir leat: snippets cód, cásanna tástála, cúltaca eisceachta, scannáin, srl Is é cás tástála deas beag an bealach is fearr chun fabht a thuairisciú, mar tugann sé bealach cabhrach dúinn an fabht a dhearbhú go tapa.
- **Don't** post to [Django Forum](https://forum.djangoproject.com/) only to announce that you have filed a
  bug report. All the tickets are mailed to another list, [django-updates](/ga/6.1/internals/mailing-lists/#django-updates-mailing-list),
  which is tracked by developers and interested community members; we see them
  as they are filed.

To understand the lifecycle of your ticket once you have created it, refer to
[Sreabhadh oibre triage](/ga/6.1/internals/contributing/triaging-tickets/#triage-workflow).

### Reporting user interface bugs

If your bug impacts anything visual in nature, there are a few additional
guidelines to follow:

- Cuir scannáin san áireamh i do thicéad atá comhionann amhairc le cás tástála íosta. Taispeáin an tsaincheist, ní na saincheaptha craiceáilte a rinne tú ar do bhrabhsálaí.
- Má tá sé deacair an cheist a thaispeáint ag baint úsáide as íomhá fhór, smaoinigh ar scáileán gearrthán\* a ghabháil. Má cheadaíonn do bhogearraí é, ní ghabháil ach an limistéar ábhartha den scáileán.
- Má tá paiste á dtairiscint agat a athraíonn cuma nó iompar Chomhéadain Django, ní mór duit\*\* a cheangal roimh\* agus\* tar éis scáileán/scáileáin scáileáin. Tá sé deacair do thríóirí ticéid nach bhfuil siad seo acu a mheas go tapa.
- Ní chuireann scáileáin scáileáin ort ó dhea-chleachtais tuairiscithe eile. Déan cinnte URLanna, snippets cód, agus treoracha céim ar chéim a áireamh maidir le conas an t-iompar atá le feiceáil sna scannáin a atáirgeadh.
- Déan cinnte bratach UI/UX a shocrú ar an ticéad ionas gur féidir le páirtithe leasmhara do thicéad a fháil.
- If the issue relates to accessibility, please link to the relevant
  [accessibility standard](/ga/6.1/internals/contributing/accessibility/#accessibility-standards) if applicable.

## Gnéithe a iarraidh

Táimid i gcónaí ag iarraidh Django a dhéanamh níos fearr, agus is cuid lárnach de sin iad d'iarrataí gné. Seo roinnt leideanna maidir le conas iarratas a dhéanamh is éifeachtaí:

- Evaluate whether the feature idea requires changes in Django's core. If your
  idea can be developed as an independent application or module — for
  instance, you want to support another database engine — we'll probably
  suggest that you develop it independently. Then, if your project gathers
  sufficient community support, we may consider it for inclusion in Django.
- Propose the feature in the [new feature ideas](https://github.com/orgs/django/projects/24/) GitHub project (not in the
  ticket tracker) by creating a new item in the **Idea** column. This is where
  the community and the [Steering Council](/ga/6.1/internals/organization/#steering-council) evaluate new
  ideas for the Django ecosystem. This step is especially important for large
  or complex proposals. We prefer to discuss any significant changes to
  Django's core before any development begins. In some cases, a feature may be
  better suited as a third-party package, where it can evolve independently of
  Django's release cycle.
- Déan cur síos soiléir agus go hachomair cad é an ghné atá in easnamh agus conas ar mhaith leat é a fheiceáil i bhfeidhm. Cuir cód samplaí san áireamh (tá neamhfheidhmiúil ceart go leor) más féidir.
- Mínigh cén fá\* gur mhaith leat an ghné. Cuideoidh míniú cás íosta úsáide le daoine eile tuiscint a fháil ar an áit a luíonn sé isteach, agus má tá bealaí eile ann cheana chun an rud céanna a bhaint amach.

Féach freisin: :ref: documenting-new-features .

## Optamú feidhmíochta a iarraidh

Ba cheart go soláthródh tuairiscí ar aischéimniú feidhmíochta, nó barrfheabhsú feidhmíochta molta, tagarmharcanna agus orduithe don triager ticéad a atáirgeadh.

Féach na:ref: django-asv-tagarmharcans le haghaidh tuilleadh sonraí faoi thagarmharcanna Django atá ann cheana.

## Conas a dhéanaimid cinntí

Whenever possible, we aim for rough consensus. Emoji reactions are used on
issues within the [new feature ideas](https://github.com/orgs/django/projects/24/) GitHub project to track community
feedback. The following meanings are assigned to each reaction:

- 👍: I support this feature and would use it
- 👎: I oppose this feature or believe it would cause issues for me or Django
- 😕: I have no strong opinion on this feature
- 🎉: This feature seems like a straightforward and beneficial addition

The [Steering Council](/ga/6.1/internals/organization/#steering-council) will regularly review the ideas
in the project, moving those with community support through the following
stages:

- Idea
- Approved - Idea refinement - Team creation
- In progress
- Working solution - Review - Feedback
- Needs maintainer (Django only)
- Done

Occasionally, discussions on feature ideas or the direction of Django may take
place on the Django Forum. These discussions may include informal votes, which
follow the voting style invented by Apache and used on Python itself, where
votes are given as +1, +0, -0, or -1.
Roughly translated, these votes mean:

- +1: “Is breá liom an smaoineamh agus táim tiomanta go láidir dó.”
- +0: “Fuaimeanna ceart go leor dom.”
- -0: “Níl áthas orm, ach ní sheasfaidh mé ar an mbealach.”
- -1: “Ní aontaím go láidir agus bheadh mé an-míshásta an smaoineamh a fheiceáil ag titim ina réaltacht.”

Cé go bhfuil na vótaí seo neamhfhoirmiúil, glacfar i ndáiríre iad. Tar éis tréimhse vótála oiriúnach, má thagann comhdhearcadh soiléir chun cinn leanfaimid na vótaí.

## How to test pre-release versions of Django

Testing pre-releases is a great way to contribute to Django. Early testers
help catch bugs before the final release, ensuring a smoother upgrade
experience for everyone.

### Riachtanais

Before testing a pre-release, it is important that your project is running
smoothly on the latest stable release of Django. That way, any regressions can
be attributed to the pre-release. See the [Conas Django a uasghrádú go leagan níos nuaí](/ga/6.1/howto/upgrade-version/) guide
for instructions on getting up to date.

To ensure your project is ready, you should also:

- **Read the release notes:** Review the [Nótaí scaoilte](/ga/6.1/releases/) for the
  upcoming version to learn about upgrade paths for deprecated features or
  about minor backward-incompatible changes.
- **Resolve deprecation warnings:** Run your tests with deprecation warnings
  enabled to become aware of required follow-up actions:

  ```console
  $ python -Wa manage.py test
  ```

### Testing your project

You can install the latest pre-release using `pip`:

```console
$ python -m pip install --pre Django
```

Once installed, run your project's test suite. Rather than just checking
if tests pass, try the following:

- **Check dependency support:** Determine whether major dependencies support
  the new version by checking Django version classifiers on PyPI.
  Since those projects also value early bug reports, don't let a lack
  of support prevent you from testing.
- **Monitor performance:** You can run your tests with the [`test
  --durations`](/ga/6.1/ref/django-admin/#cmdoption-test-durations) flag to identify potential performance regressions.
- **Automate tests in CI:** Consider running your Continuous Integration (CI)
  pipeline with the pre-release version.
- **Test manually:** While automated tests are great, manually testing your
  application's main workflows is an important part of verifying compatibility
  with a new release.

### Reporting issues

If you discover a bug, please report it via the [Django issue tracker](https://code.djangoproject.com/) so it can be fixed before the final
release. When creating the ticket, be sure to set the Django version field to
the exact pre-release version you are testing.

If you suspect a regression, it's helpful to report the specific commit that
caused it. See [Aischéimniú a dhíghilt](/ga/6.1/internals/contributing/triaging-tickets/#bisecting-a-regression) for instructions.

You can also discuss any issues or share feedback in the [Pre-releases](https://forum.djangoproject.com/c/announcements/prereleases/32) category
on the [Django Forum](https://forum.djangoproject.com/).