Add improved maintenance column with a dropdown showing tasks

[Simrayz]

Scope and purpose

Resolves #1745

This PR improves the planned maintenance column by adding a dropdown with linkable connected tasks.

Contributor Checklist

Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to Argus can be found in the
Development docs.

• Added a changelog fragment for towncrier
• Added/amended tests for new/changed code
• Added/changed documentation, including updates to the user manual if feature flow or UI is considerably changed
• Linted/formatted the code with ruff and djLint, easiest by using pre-commit
• The first line of the commit message continues the sentence "If applied, this commit will ...", starts with a capital letter, does not end with punctuation and is 50 characters or less long. See our how-to
• If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done
• If this results in changes in the UI: Added screenshots of the before and after
• If this results in changes to the database model: Updated the ER diagram

[github-actions]

Test results

    6 files    888 suites   1m 56s ⏱️
  697 tests   696 ✅ 1 💤 0 ❌
4 182 runs  4 176 ✅ 6 💤 0 ❌

Results for commit 1851bcf.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.57%. Comparing base (7f6da04) to head (1851bcf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1761   +/-   ##
=======================================
  Coverage   82.57%   82.57%           
=======================================
  Files         137      137           
  Lines        6552     6552           
=======================================
  Hits         5410     5410           
  Misses       1142     1142           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[aleksfl]

Mostly works as intended when testing. Documentation should probably be updated accordingly.

[hmpf]

What happens if there are hundreds of incidents covered by the pm?

[hmpf]

Let's be consistent with the date formats please. Always use the formats chosen in preferences.

• |date:preferences.argus_htmx.datetime_format
• |date:preferences.argus_htmx.date_format
• |date:preferences.argus_htmx.time_format

If another is needed, for "datetime without year", let's add another to the above list.

[Simrayz]

Fixed, it is now using the date_format from user preferences. The idea behind using a custom date format was to present the information in the same way to all users, and keep the UI compact. E.g. an EPOCH timestamp is not very user friendly when used in ranges. However, I agree that it makes sense to be consistent, and leave it up to the user to use a proper date format.

[Simrayz]

Updated the UI and date format to match requested changes:

[Simrayz]

What happens if there are hundreds of incidents covered by the pm?

The dropdown shows the tasks connected to an incident, and not the other way around (incidents for task). Only open incidents are checked against a new PM task. As such, unless we expect a lot of maintenance tasks covering the same incidents, the dropdown shouldn't have a lot of entries

[johannaengland]

What happens if there are hundreds of incidents covered by the pm?

The dropdown shows the tasks connected to an incident, and not the other way around (incidents for task). Only open incidents are checked against a new PM task. As such, unless we expect a lot of maintenance tasks covering the same incidents, the dropdown shouldn't have a lot of entries

Yeah, I would also not expect hundreds of tasks that all cover one incident - then the user has done something wrong 😁

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[johannaengland]

We can have the bug that when I click on one maintenance task icon that the dropdown stays visible until I click somewhere else as polish, not that important now

[Simrayz]

We can have the bug that when I click on one maintenance task icon that the dropdown stays visible until I click somewhere else as polish, not that important now

Yeah it seems to be related to the button remaining in focus after clicking it, and happens both in Brave and Firefox. An alternative would be to not use a button element as the trigger