# Trac migration informational DEP - Feedback required

**URL:** <https://forum.djangoproject.com/t/trac-migration-informational-dep-feedback-required/36649>\
**Category:** Django Internals\
**Created:** [November 21, 2024, 7:10pm UTC](https://forum.djangoproject.com/t/trac-migration-informational-dep-feedback-required/36649 "2024-11-21T19:10:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![carltongibson](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/carltongibson/32/267_2.png) [@carltongibson](https://forum.djangoproject.com/u/carltongibson)\
**Post date:** [November 22, 2024, 6:07am UTC](https://forum.djangoproject.com/t/trac-migration-informational-dep-feedback-required/36649/3 "2024-11-22T06:07:22Z")

</div>

All I can really do is quote my comment from the other thread:

> [@Discuss migrating off of Trac onto 'something' else](https://forum.djangoproject.com/t/discuss-migrating-off-of-trac-onto-something-else/36253/11):
>
> The history. It’s absolutely impossible to work on Django without it. A hard criterion on any option is that we can’t loose that. And it can’t become impossible to filter/search. (This last is a problem with GitHub issues. DRF, for example, a large project that I’ve worked on at length, is much harder to find related issues on, despite probably having only a tenth or less of the history.)

It’s the **precise filtering** that the extra fields enable. GitHub’s labelling is grossly underpowered by comparison. It’s the day to day use of Trac which shows its power.

The timeline and reports are all features I use regularly, and more so when Fellow.

---

_[View the full topic](https://forum.djangoproject.com/t/trac-migration-informational-dep-feedback-required/36649)._
