Skip to content

Update reporting popup message

Christian Walgenbach requested to merge update-reporting-message into master

What does this MR do?

There is no final solution or timetable yet for how to proceed with the systems for reporting rule violations.

Therefore the date in the popup message will be removed and the blog entry will be updated.

How confident are you it won't break things if deployed?

(be honest!)

Links to related issues

https://yunity.slack.com/archives/C1T1ZM9A4/p1601624811025700

Screenshots (if applicable)

Any relevant screenshots if this is a design / frontend change

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • use "state:" labels to track this MR's state until it was beta tested
  • added an entry to CHANGELOG.md
  • add a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo:
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...). how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text

(A short text that will appear in the release notes and describes the change for non-technical people. Not always necessary, e.g. not for refactoring.)

Edited by Christian Walgenbach

Merge request reports