Klaas van Schelven 66b384a87d issue UI pages: optimization ...

no need to calculate event_qs_count (which is potentially expensive) if that's
not used in display.

when counting was moved from the template to the view (in 1eea9268a5) it was
made unconditional; here we restore that behavior.

2025-03-31 13:07:32 +02:00

..

migrations

Issue.calculated_* fields: fix lengths

2025-03-05 11:14:19 +01:00

templates/issues

issue UI pages: optimization

2025-03-31 13:07:32 +02:00

__init__.py

The ugliest thing that could get a stacktrace on screen

2023-11-04 21:02:04 +01:00

admin.py

Chache stored_event_count (on Issue and Projet)

2025-02-06 16:24:25 +01:00

apps.py

The ugliest thing that could get a stacktrace on screen

2023-11-04 21:02:04 +01:00

factories.py

Clarify a docstring

2024-07-18 15:13:08 +02:00

forms.py

Django admin forms: do not mess up my specially crafted fields please

2024-09-12 14:08:46 +02:00

models.py

Issue Tag display: for low event-counts, show more tags

2025-03-31 09:56:31 +02:00

regressions.py

Rewrite comments on 'reopen' and 'issue_is_regression'

2024-09-17 23:01:41 +02:00

tests.py

Tags: as a separate tab

2025-03-03 12:56:20 +01:00

urls.py

Optimization: Search on EvenTag without involving Event if possible

2025-03-12 20:38:07 +01:00

utils.py

Truncate input-data that exceeds max_length

2025-02-08 21:21:55 +01:00

views.py

issue UI pages: optimization

2025-03-31 13:07:32 +02:00