Klaas van Schelven 9ee623de6b Add Event.grouping field and fill it ...

An event always has a single (automatically calculated) Grouping associated with it.
We add this info to the Event model (we'll soon display it in the UI, and as per the
now-removed comment it's simply the consistent thing to do)

2025-01-31 16:16:07 +01:00

..

migrations

Correctly order Turningpoints (as per comment)

2024-12-16 22:04:03 +01:00

templates/issues

'This might mean' refers to 'No open issues'; make this show in the interface

2025-01-24 11:47:12 +01:00

__init__.py

The ugliest thing that could get a stacktrace on screen

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

admin.py

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

2024-09-12 14:08:46 +02: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

Describe role of Grouping and how it relates to Issue

2025-01-31 15:25:18 +01:00

regressions.py

Rewrite comments on 'reopen' and 'issue_is_regression'

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

tests.py

Add Event.grouping field and fill it

2025-01-31 16:16:07 +01:00

urls.py

Navigation: fix for missing events

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

utils.py

Show 'handled' and 'mechanism' in the event details

2025-01-31 13:02:49 +01:00

views.py

Show transaction in the event details

2025-01-31 13:09:54 +01:00