---
title: "Mendahulukan tiket"
version: 6.1
locale: id
source: https://docs.djangoproject.com/id/6.1/internals/contributing/triaging-tickets/
canonical: https://djangodocs.dev/id/6.1/internals/contributing/triaging-tickets/
---
# Mendahulukan tiket

Django uses [Trac](https://code.djangoproject.com/) for managing the work on the code base. Trac is a
community-tended garden of the bugs people have found and the features Django
has decided to add. As in any garden, sometimes there are weeds to be pulled
and sometimes there are flowers and vegetables that need picking. We need your
help to sort out one from the other, and in the end, we all benefit together.

Like all gardens, we can aspire to perfection, but in reality there's no such
thing. Even in the most pristine garden there are still snails and insects.
In a community garden there are also helpful people who -- with the best of
intentions -- fertilize the weeds and poison the roses. It's the job of the
community as a whole to self-manage, keep the problems to a minimum, and
educate those coming into the community so that they can become valuable
contributing members.

Demikan pula, selagi kita menyasar untuk Trac menjadi perwakilan sempurna dari keadaan kemajuan Django, kami mengakui bahwa ini tidak akan terjadi. Dengan menyebarkan muatan perawatan Trac ke komunitas, kami menerima bahwa ada kesalahan. Trac "kebanyakan paling akurat", dan kami memberikan kelonggaran untuk fakta bahwa terkadang itu akan salah. Tidak mengapa. Kami ingin sempurna dengan tenggat waktu.

We rely on the community to keep participating, keep tickets as accurate as
possible, and raise issues for discussion on the [Django Forum](https://forum.djangoproject.com/) when there is
confusion or disagreement.

Django adalah proyek komunitas, dan setiap bantuan membantu. Kami tidak dapat melakukan ini tanpa **anda**!

## Alur kerja Triage

Unfortunately, not all reports in the ticket tracker provide all the
[required details](/id/6.1/internals/contributing/bugs-and-features/#reporting-bugs). A number of tickets have proposed
solutions, but those don't necessarily meet all the requirements [adhering
to the guidelines for contributing](/id/6.1/internals/contributing/writing-code/submitting-patches/#patch-style).

Satu cara untuk membantu adalah *memberikan* tiket yang telah dibuat oleh pengguna lain.

Kebanyakan alurkerja berdasarkan seputar konsep dari [triage stages](#triage-stages) tiket. Setiap tahapan menggambarkan dimana didalam siklus hidupnya tiket yang diberikan adalah kapan saja. Bersama dengan bendera-bendera yang sangat membantu, atribut ini dengan mudah memberitahu kami bahwa apa dan siapa setiap tiket sedang menunggu.

Sejak gambar berharga seribu kata, mari kita mulai disana:

![Alur kerja triase tiket Django](internals/_images/contribution_process.svg)

We have four roles in this diagram. Maintainers (also known as Fellows) usually
take part in all of them, but anyone in the Django community can participate in
any role except merger. The [merger role](/id/6.1/internals/organization/#mergers-team) is granted by a
vote of the [Steering Council](/id/6.1/internals/organization/#steering-council).

- Triagers: anyone can take on this role by checking whether a ticket describes
  a real issue and keeping the tracker organized.
- Bug fixers: anyone can contribute by opening a pull request and working on a
  solution for a ticket.
- Reviewers: anyone can [review pull requests](#reviewing-patches) and
  suggest improvements.
- Mergers: people with commit access who make the final decision to merge a
  change.

> **When we say anyone, we mean you!**
>
> Our Trac system and GitHub repositories are intentionally open to the
> public. Anyone can help by working on tickets, triaging tickets and
> reviewing changes. Django is a community project, and we encourage
> [triage and collaboration by the community](#how-can-i-help-with-triaging). We truly want you to help!

For example, here's the typical lifecycle of a ticket:

- Alice creates a ticket and opens an incomplete pull request (missing tests,
  incorrect implementation).
- Bob reviews the pull request, marks the ticket as "Accepted", sets the
  flags "needs tests" and "patch needs improvement", and leaves a comment
  explaining how Alice can improve the patch. This puts the ticket
  automatically into the "waiting on author" queue within the "accepted" stage.
- Alice updates the pull request, adding tests (but not yet fixing the
  implementation), and removes the two flags. The ticket moves into the "needs
  PR review" queue.
- Charlie reviews the pull request, sets the "patch needs improvement" flag
  again, and leaves another comment suggesting changes to the implementation.
  The ticket moves back to the "waiting on author" queue.
- Alice updates the pull request again, this time fixing the implementation,
  and removes the "patch needs improvement" flag. The ticket moves once more
  into the "needs PR review" queue.
- Daisy meninjau pull request, dan menandai tiket sebagai "Siap untuk mendaftar".
- Jacob, a [merger](/id/6.1/internals/organization/#mergers-team), reviews and merges the pull request.

Some tickets move through these steps quickly, while others take more time and
discussion. Each contribution helps Django improve.

## Tahapan-tahapan Triage

Dibawah ini kami menggambarkan dalam lebih rinci beragam tingkatan dimana sebuah tiket mungkin mengalir selama siklus hidupnya.

### Belum ditinjau

The ticket has not been reviewed by anyone who felt qualified to make a
judgment about whether the ticket contained a valid issue or ought to be closed
for any reasons. Unreviewed tickets appear in the "triage" queue.

Unreviewed tickets may receive additional refinement before being accepted.
Unless you are both the author of the ticket and intending to submit a patch,
unreviewed tickets should not be [claimed](/id/6.1/internals/contributing/writing-code/submitting-patches/#claiming-tickets).

### Diterima

The absolute meaning of "accepted" is that the issue described in the ticket is
valid and actionable. It is broken out into three queues:

- **Needs Patch** (Accepted + No Flags)

  The ticket is valid, but no one has submitted a patch for it yet. Often this
  means you could safely start writing a fix for it. This is generally more
  true for the case of accepted bugs than accepted features. A ticket for a bug
  that has been accepted means that the issue has been verified by at least one
  triager as a legitimate bug - and should probably be fixed if possible.

  For new features, accepted tickets should only exist after the idea has gone
  through the appropriate [process for suggesting new features](/id/6.1/internals/contributing/bugs-and-features/#requesting-features) and received community and [Steering Council](/id/6.1/internals/organization/#steering-council) approval, or been accepted in a DEP.
- **Needs PR Review** (Accepted + Has Patch)

  The ticket is waiting for people to review the supplied solution. This means
  downloading the patch and trying it out, verifying that it contains tests
  and docs, running the test suite with the included patch, and leaving
  feedback on the ticket.
- **Waiting On Author** (Accepted + Has Patch + Needs fixes)

  Ini berarti tiket telah ditinjau, dan telah ditemukan untuk pekerjaan lebih lanjut. "Butuh Percobaan" dan "Butuh dokumentasi" adalah penjelasan-sendiri. "Butuh perbaikan tambalan" akan umumnya ditemani oleh komentar pada tiket menjelaskan apa yang dibutuhkan untuk memperbaiki kode.

### Siap Untuk Mendaftar

The ticket was reviewed by any member of the community other than the person
who supplied the patch and found to meet all the requirements for a
commit-ready contribution. A [merger](/id/6.1/internals/organization/#mergers-team) now needs to give
a final review prior to being committed.

There are a lot of pull requests. It can take a while for your patch to get
reviewed. See the [contributing code FAQ](/id/6.1/faq/contributing/#new-contributors-faq) for some
ideas here.

### Suatu hari/Mungkin

This stage isn't shown on the diagram. It's used sparingly to keep track of
long-term changes.

Tiket ini tidak umum dan secara keseluruhan kurang berguna sejak mereka tidak menggambarkan masalah nyata yang dapat ditindaklanjuti.

## Atribut triage lainnya

Sejumlah bendera, muncul sebagai kotak centang di Trac, dapat di setel di tiket:

### Memiliki Tambalan

This means the ticket has an associated solution. These will be reviewed to
ensure they adhere to the [documented guidelines](/id/6.1/internals/contributing/writing-code/submitting-patches/#patch-review-checklist).

Tiga bidang berikut (Butuh dokumentasi, Butuh percobaan, Tambalan butuh perbaikan) berlaku jika sebuah tambalan telah dipasok.

### Butuh dokumentasi

Bendera ini digunakan untuk tiket dengan tambalan yang butuh dokumentasi terkait. Dokumentasi lengkap dari fitur adalah prasyarat sebelum kami dapat memerika mereka ke dalam basiskode.

### Butuh pengujian

This flags the patch as needing associated unit tests. Again, this
is a required part of a valid contribution.

### Tambalan butuh perbaikan

This flag means that although the ticket *has* a solution, it's not quite
ready for checkin. This could mean the patch no longer applies
cleanly, there is a flaw in the implementation, or that the code
doesn't meet our standards.

### Pengambilan mudah

Tiket yang akan membutuhkan kecil, mudah, perubahan.

### Tipe

Tiket harus dikelompokkan berdasarkan *jenis* diantara:

- **Fitur Baru**

    Untuk menambahkan sesuatu baru.
- **Kesalahan**

    Untuk ketika hal yang ada rusak atau tidak berperilaku seperti yang diharapkan.
- **Pembersihan/optimalisasi**

    Untuk ketika tidak ada yang rusak tetapi sesuatu dapat dibuat lebih jelas, lebih baik, lebih cepat, lebih kuat.

### Komponen

Tiket harus dikelompokkan kedalam *komponen* menandakan milik kawasan mana dari basiskode Django. Ini membuat tiket lebih baik tersusun dan lebih mudah ditemukan.

### Kesederhanaan

The *severity* attribute is used to identify blockers, that is, issues that
should get fixed before releasing the next version of Django. Typically those
issues are bugs causing regressions from earlier versions or potentially
causing severe data losses. This attribute is quite rarely used and the vast
majority of tickets have a severity of "Normal".

### Versi

The *version* attribute indicates the earliest version in which the bug was
reproduced. During triage, this field can be updated, but there is no need to
make further updates when that version goes out of support. The field should
not be reset to "dev" to show the issue still exists: instead, the tested
commit hash can be noted in a comment.

### UI/UX

Bendera ini digunakan untuk tiket yang terkait ke Antarmuka Pengguna dan pertanyaan Pengalaman pengguna. Sebagai contoh, bendera ini akan sesuai untuk pengguna-menghadapi fitur dalam formulir atau antarmuka admin.

### Cc

Anda mungkin menambahkan nama pengguna atau alamt surel ke bidang ini untuk diberitahu ketika bantuan baru dibuat ke tiket.

### Kata kunci

With this field you may label a ticket with multiple keywords. This can be
useful, for example, to group several tickets on the same theme. Keywords can
either be comma or space separated. Keyword search finds the keyword string
anywhere in the keywords. For example, clicking on a ticket with the keyword
"form" will yield similar tickets tagged with keywords containing strings such
as "formset", "modelformset", and "ManagementForm".

## Menutup Tiket

When a ticket has completed its useful lifecycle, it's time for it to be
closed. Closing a ticket is a big responsibility, though. You have to be sure
that the issue is really resolved, and you need to keep in mind that the
reporter of the ticket may not be happy to have their ticket closed (unless
it's fixed!). If you're not certain about closing a ticket, leave a comment
with your thoughts instead.

Jika anda menutup sebuah tiket, anda harus selalu memastikan berikut:

- Pastikan bahwa masalah terselesaikan.
- Tinggalkan komentar menjelaskan keputusan untuk menutup tiket.
- JIka ada cara mereka dapat memperbaiki tiket untuk membukanya, biarkan mereka mengetahui.
- Jika tiket ganda, acukan tiket asli. Juga periksa acuan tiket tertutup dengan meninggalkan komentar dalam satu yang asli -- ini mengizinkan untuk mengakses lebih informasi terkait tentang kesalahan dilaporkan atau fitur diminta.
- **Sopanlah** Tidak seorangpun suka tiket milik mereka tutup. Itu dapat mengecewakan atau bahkan mengecilkan. Jalan terbaik untuk menghindari merubah orang dari membantu ke Django adalah menjadi sopan dan ramah dan untuk menawarkan saran untuk bagaimana mereka dapat memperbaiki tiket ini dan tiket lainnya di masa depan.

Sebuah tiket dapat diselesaikan dalam sejumlah jalan:

- **diperbaiki**

    Digunakan ketika sebuah tambalan telah digulirkan kedalam Django dan masalah diperbaiki.
- **tidak sah**

    Digunakan jika tiket ditemukan tidak benar. Ini berarti bahwa masalah dalam tiket sebenarnya hasil dari kesalahan pengguna, atau menggambarkan sebuah masalah dengan sesuatu selain daripada Django, atau bukan laporan kesalahan atau permintaan kesalahan (sebagai contoh, beberapa pengguna baru mengajukan permintaan dukungan sebagai tiket).
- **wontfix**

    Used when someone decides that the request isn't appropriate for
    consideration in Django. Sometimes a ticket is closed as "wontfix" with a
    request for the reporter to start a discussion on the [Django Forum](https://forum.djangoproject.com/) if
    they feel differently from the rationale provided by the person who
    closed the ticket. Other times, a discussion precedes the decision to
    close a ticket. Always use the forum to get a consensus before reopening
    tickets closed as "wontfix".
- **needsnewfeatureprocess**

    Used when the ticket merits a new feature, which will need to get
    community input and support.
    See the [process for suggesting new features](/id/6.1/internals/contributing/bugs-and-features/#requesting-features).
- **rangkap**

    Digunakan ketika tiket lainnya menutuoi masalah sama. Dengan menutup tiket ganda, kami menjaga semua obrolan dalam satu tempat, yang membantu semua orang.
- **worksforme**

    Digunakan ketika tiket tidak mengandung cukup rincian untuk mengulangi kesalahan asli.
- **needsinfo**

    Digunakan ketika tiket tidak mengandung cukup informasi untuk mengulangi masalah dilaporkan tetapi masih berpotensi sah. Tiket harus dibuka kembali ketika informasi lebih dipasok.

If you believe that the ticket was closed in error -- because you're
still having the issue, or it's popped up somewhere else, or the triagers have
made a mistake -- please reopen the ticket and provide further information.
Again, please do not reopen tickets that have been marked as "wontfix" or
"needsnewfeatureprocess". For "wontfix" tickets, bring the issue to the
[Django Forum](https://forum.djangoproject.com/) instead. For "needsnewfeatureprocess" tickets, propose the
feature through the [new features process](/id/6.1/internals/contributing/bugs-and-features/#requesting-features).

## How can I help with development?

The development process is primarily driven by community members. Really,
**ANYONE** can help.

Untuk ikut serta, mulai dengan [membuat sebuah  akun pada Trac](https://www.djangoproject.com/accounts/register/). Jika anda mempunyai sebuah akun tetapi lupa sandi anda, anda dapat menyetel kembali menggunakan [password reset page](https://www.djangoproject.com/accounts/password/reset/).

lalu, anda dapat membantu dengan:

- Closing "Unreviewed" tickets as "invalid", "worksforme", "duplicate",
  "wontfix", or "needsnewfeatureprocess".
- Closing "Unreviewed" tickets as "needsinfo" when the description is too
  sparse to be actionable.
- Memperbaiki bendera "Butuh percobaan", "Butuh dokumentasi", atau "Mempunyai tambalan" untuk tiket dimana mereka disetel tidak benar.
- Mengatur bendera "[Easy pickings](https://code.djangoproject.com/query?status=!closed&easy=1)" untuk tiket yang kecil dan relatif mudah.
- Setel *jenis* dari tiket yang masih belum dikelompokkan.
- Memeriksa tiket lama itu masih sah. Jika sebuah tiket tidak kelihatan aktifitas apapun dalam jangka lama, itu dimungkinkan bahwa masalah telah diperbaiki tetapi tiket belum ditutup.
- Identifying trends and themes in the tickets. If there are a lot of bug
  reports about a particular part of Django, it may indicate we should
  consider refactoring that part of the code. If a trend is emerging,
  you should raise it for discussion (referencing the relevant tickets)
  on the [Django Forum](https://forum.djangoproject.com/).
- Verify if solutions submitted by others are correct. If they are correct
  and also contain appropriate documentation and tests then move them to the
  "Ready for Checkin" stage. If they are not correct then leave a comment to
  explain why and set the corresponding flags ("Patch needs improvement",
  "Needs tests" etc.).

> **Note**
>
> The [Reports page](https://code.djangoproject.com/wiki/Reports) contains links to many useful Trac queries, including
> several that are useful for triaging tickets and reviewing proposals as
> suggested above.
>
> You can also find more [Saran untuk penyumbang baru](/id/6.1/internals/contributing/new-contributors/).

Bagaimanapun, kami meminta berikut semua anggota komunitas umum yang bekerja di basisdata tiket:

- Please **don't** promote your own tickets to "Accepted". Another community
  member should review the report and set this stage after reproducing and
  confirming the issue.
- Please **don't** promote your own tickets to "Ready for checkin". You
  may mark other people's tickets that you've reviewed as "Ready for
  checkin", but you should get at minimum one other community member to
  [review a patch](#reviewing-patches) that you submit.
- Please **don't** reverse a decision without posting a message to the
  [Django Forum](https://forum.djangoproject.com/) to find consensus.
- If you're unsure if you should be making a change, don't make the
  change but instead leave a comment with your concerns on the ticket,
  or post a message to the [Django Forum](https://forum.djangoproject.com/). It's okay to be unsure, but your
  input is still valuable.

## Membagi dua pemulihan

Pemulihan adalah sebuah kesalahan yang hadir dalam beberapa versi terbaru dari Django tetapi tidak di versi lama. Sepotong informasi sangat membantu adalah perbaikan yang memperkenalkan pemulihan. Sepengetahuan penyerahan yang menyebabkan perubahan dalam kebiasaan membantu mencirikan jika perubahan disengaja atau jika itu efek samping tidak sengaja. Disini bagaimana anda dapat menentukan ini.

Begin by writing a regression test for Django's test suite for the issue. For
example, we'll pretend we're debugging a regression in migrations. After you've
written the test and confirmed that it fails on the latest main branch, put it
in a separate file that you can run standalone. For our example, we'll pretend
we created `tests/migrations/test_regression.py`, which can be run with:

```shell
$ ./runtests.py migrations.test_regression
```

Selanjutnya, kami menandari titik saat ini di riwayat menjadi "bad" sejak kegagalan pengujian:

```shell
$ git bisect bad
You need to start by "git bisect start"
Do you want me to do it for you [Y/n]? y
```

Now, we need to find a point in git history before the regression was
introduced (i.e. a point where the test passes). Use something like
`git checkout HEAD~100` to check out an earlier revision (100 commits
earlier, in this case). Check if the test fails. If so, mark that point as
"bad" (`git bisect bad`), then check out an earlier revision and recheck.
Once you find a revision where your test passes, mark it as "good":

```shell
$ git bisect good
Bisecting: X revisions left to test after this (roughly Y steps)
...
```

Sekarang kami siap untuk bagian yang menyenangkan menggunakan `git bisect run` untuk mengotomatiskan sisa proses:

```shell
$ git bisect run tests/runtests.py migrations.test_regression
```

Anda seharusnya melihat `git bisect` menggunakan pencarian biner untuk otomatis periksa perbaikan diantara perbaikan baik dan buruk sampai dia menemukan perbaikan "buruk" dimana percobaan gagal.

Sekarang, laporkan hasil anda di tiket Trac, dan silahkan sertakan percobaan pemulihan sebagai sebuah lampiran. Ketika seseorang menulis perbaikan untuk kesalahan, mereka sudah akan memiliki percobaan anda sebagai sebuah titik permulaan.

## Reviewing patches

A great way to learn the Django codebase is to help review patches. It allows
you to focus on a fixed scope of Django with a particular perspective. Plus,
Django tends to receive more patches than it can review which causes the
[review queue](https://code.djangoproject.com/query?has_patch=1&needs_better_patch=0&needs_docs=0&needs_tests=0&stage=Accepted&status=!closed&order=changetime&desc=1) to build up. Contributors can help Django tremendously by
reviewing patches.

The [review queue](https://code.djangoproject.com/query?has_patch=1&needs_better_patch=0&needs_docs=0&needs_tests=0&stage=Accepted&status=!closed&order=changetime&desc=1) is defined by tickets in [Trac](https://code.djangoproject.com/) that are in the "Accepted"
state with the flag "has patch" set and the flags "patch needs improvement",
"needs tests" and "needs documentation" unset. There is also a set of
[Pull Requests in GitHub with the "no ticket" label](https://github.com/django/django/pulls?q=is%3Aopen+is%3Apr+label%3A%22no+ticket%22) that can be reviewed.

### Code review process

The general process to reviewing a patch for Django is as follows:

1. Pick a patch to review. This can be from the [review queue](https://code.djangoproject.com/query?has_patch=1&needs_better_patch=0&needs_docs=0&needs_tests=0&stage=Accepted&status=!closed&order=changetime&desc=1) or the
   [Pull Requests in GitHub with the "no ticket" label](https://github.com/django/django/pulls?q=is%3Aopen+is%3Apr+label%3A%22no+ticket%22). If you're new, pick
   a specific component to stick with. Django is a big codebase, so it's best
   to contribute consistently with a narrow focus and grow it slowly.
2. Pull the branch. See the [Penanganan pull request](/id/6.1/internals/contributing/committing-code/#handling-pull-requests), including the git
   alias to make checking out other pull requests easier.
3. Check the tests. If the ticket is for a bug, there should be a regression
   test. Confirm that the test fails if the change is reverted. Check that the
   tests are adequately covering the code and logic as well. See
   [Daftar centang bantuan](/id/6.1/internals/contributing/writing-code/submitting-patches/#patch-review-checklist).
4. Test in your own Django project. See [Memasang versi pengembangan](/id/6.1/topics/install/#installing-development-version)
   for how. Explore the user interface and user experience with the change.
   Does it feel right? Can you break it? Another approach is to assume
   everything is wrong. Can you demonstrate to yourself that each piece is
   correct?
5. Check the documentation. Is the documentation understandable? Does it
   provide the information the reader needs at that moment? Does it read well?
   Is it consistent with the documentation before and after it? See
   [Bangun dokumentasi lokal](/id/6.1/internals/contributing/writing-documentation/#build-documentation-locally).
6. Are you happy with the patch? This is fairly subjective, but that's fine.
   You should ask, does the approach make sense to you and is there another
   way to do it that's better? Also ask yourself, is the scope of the change
   appropriate? Are things named appropriately? Renaming things is slow and
   challenging in Django, so we should try to get it right from the start.
   Are there backwards compatibility concerns? Lastly, are there any other
   general concerns such as things that may worry you or that should be looked
   into?
7. Review your feedback. Before you submit your feedback, consider the
   feedback you want to share. It takes courage to open a Pull Request, we
   should be thoughtful and considerate of the leap the author has made. If
   there are nitpicky or small suggestions, use GitHub's suggestion feature.
   If the approach isn't what you expected, consider asking the author why
   before requesting several changes. Seek to understand their reasoning
   first.
8. Submit feedback on GitHub and update flags, "patch needs improvement",
   "needs tests", and "needs documentation", as needed. This will move the
   ticket to the ["waiting for author" queue](https://code.djangoproject.com/query?has_patch=1&needs_better_patch=1&stage=Accepted&status=assigned&status=new&or&has_patch=1&needs_docs=1&stage=Accepted&status=assigned&status=new&or&has_patch=1&needs_tests=1&stage=Accepted&status=assigned&status=new&order=changetime&desc=1). If you have given a
   specific type of code review, please indicate that on the Pull Request.

### Types of code reviews

Not everyone will or should give the same type of code review. Having a diverse
set of opinions and experiences helps Django be better. If you are providing a
specific review, please indicate that on the Pull Request in GitHub. Below
are some of the types of code review you can perform:

- Accessibility review. Does it conform to our [Standar aksesibiltas](/id/6.1/internals/contributing/accessibility/#accessibility-standards)?
- [Patch style](/id/6.1/internals/contributing/writing-code/submitting-patches/#patch-style) and contribution process review.
- Usability and developer experience review.

  - Use the change and provide feedback from that experience.
  - Are the APIs and documentation accessible and well explained?
- Domain expertise review. Do you have a personal expertise that is relevant
  such as databases, HTTP, security, etc?
- Benchmarking and performance review. There are benchmarking tests, but
  sometimes changes require additional testing.

  - Utilize [Tolok ukur django-asv](/id/6.1/internals/contributing/writing-code/submitting-patches/#django-asv-benchmarks) to check performance over time.
  - Run benchmark tests by labeling the pull request with "benchmark".