Klaas van Schelven f69befd20a Harmonize displayed timestamps ...

I picked server-time as the thing which has the most likeliness of being correct

2024-04-01 23:00:19 +02:00

..

migrations

blank=True; as implied by the default=''

2024-03-30 20:50:02 +01:00

templates/issues

Harmonize displayed timestamps

2024-04-01 23:00:19 +02:00

__init__.py

The ugliest thing that could get a stacktrace on screen

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

admin.py

filter-fields, readonly fields for FKs

2024-03-24 22:02:15 +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

Harmonize displayed timestamps

2024-04-01 23:00:19 +02:00

regressions.py

Implement unmute-after-time

2024-03-08 20:53:31 +01:00

tests.py

issue-views: test for project membership

2024-03-25 23:38:17 +01:00

urls.py

Breadcrumbs, at least implement _something_

2024-03-31 23:04:15 +02:00

utils.py

Mutiple resolve/mute/... from UI: use querysets

2024-03-20 19:32:41 +01:00

views.py

All issue-views need the mute_options in their context

2024-04-01 22:09:59 +02:00