Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mB] redesign – project dashboard: Published projects can bypass mandatory project description validation #6063

Open
sblindow opened this issue Feb 11, 2025 · 2 comments
Labels
Prio: Low fix when there is time Type: Bug incorrect or uexpected behaviour

Comments

@sblindow
Copy link
Contributor

URL

Project Dashboard

User

Initiators, Group Members, Admins

Expected Behavior

Since project descriptions are mandatory, the system should prevent any project from being published or maintained in a published state without a project description.

Behavior

During the initial project creation, the system correctly enforces this requirement by displaying a warning indicator (red exclamation mark) and preventing publication when the project description is empty.

However, if an initiator edits a published project and removes the description entirely, the system fails to validate this field. This allows the changes to be saved, resulting in a published project that lacks the mandatory project description.

@CarolingerSeilchenspringer CarolingerSeilchenspringer added Type: Bug incorrect or uexpected behaviour Prio: Medium fixed and released with next scheduled release labels Feb 12, 2025
@janeklqd
Copy link

This is also the case if I don't enter a project description at all. Upon going to the page, I can just click the save button without entering any information, and the red warning indicator disappears.

@CarolingerSeilchenspringer CarolingerSeilchenspringer added Prio: Low fix when there is time and removed Prio: Medium fixed and released with next scheduled release labels Feb 20, 2025
@CarolingerSeilchenspringer
Copy link
Contributor

@sblindow @janeklqd Initiators will most probably not do so, therefore I changed to low prio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio: Low fix when there is time Type: Bug incorrect or uexpected behaviour
Projects
None yet
Development

No branches or pull requests

3 participants