Klaas van Schelven f0e93b4d5d 'Resolved in' actually sends the relevant version 'under water' ...

if you have an old screen open which says 'resolved in v1.0' that's what
should happen when you click, even when v2.0 has been seen in the meanwhile

2024-02-21 18:55:52 +01:00

..

migrations

Date/issue_count correct in list_view

2024-02-20 17:49:48 +01:00

templates/issues

'Resolved in' actually sends the relevant version 'under water'

2024-02-21 18:55:52 +01:00

__init__.py

The ugliest thing that could get a stacktrace on screen

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

admin.py

Various fixes after visiting the running server

2024-01-15 23:20:03 +01:00

apps.py

The ugliest thing that could get a stacktrace on screen

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

factories.py

Date/issue_count correct in list_view

2024-02-20 17:49:48 +01:00

models.py

'Resolved in' actually sends the relevant version 'under water'

2024-02-21 18:55:52 +01:00

regressions.py

Tests (and testability) of is_issue_regression

2023-12-14 22:21:43 +01:00

tests.py

Date/issue_count correct in list_view

2024-02-20 17:49:48 +01:00

urls.py

View events only as part of an issue

2023-11-14 19:14:53 +01:00

utils.py

Add separator to issue_grouper for better human readability

2023-11-08 22:25:30 +01:00

views.py

'Resolved in' actually sends the relevant version 'under water'

2024-02-21 18:55:52 +01:00