Klaas van Schelven 977aae1c25 Show remaining (in db, AKA 'available') number of events in the issue-list ...

prompted by a user being confused about the number of events in their DB;
not 100% sure I'll keep this info here, but I'm introducing it for now
at least

2025-03-06 13:32:32 +01:00

..

migrations

Issue.calculated_* fields: fix lengths

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

templates/issues

Show remaining (in db, AKA 'available') number of events in the issue-list

2025-03-06 13:32:32 +01: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.calculated_* fields: fix lengths

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

regressions.py

Rewrite comments on 'reopen' and 'issue_is_regression'

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

tests.py

Tests: Better error message for failing integration tests

2025-02-20 09:26:04 +01:00

urls.py

Navigation: fix for missing events

2024-07-19 11:03:08 +02:00

utils.py

Truncate input-data that exceeds max_length

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

views.py

Details page: be robust for top-level message-as-string

2025-03-06 13:09:29 +01:00