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

Mandatory fields are not marked #3450

Closed
matthias-ronge opened this issue Apr 15, 2020 · 3 comments · Fixed by #5550
Closed

Mandatory fields are not marked #3450

matthias-ronge opened this issue Apr 15, 2020 · 3 comments · Fixed by #5550
Labels
feature ruleset ruleset functions and configuration

Comments

@matthias-ronge
Copy link
Collaborator

The metadata entry does not show which of the fields are mandatory.

 Screenshot 1

Only after clicking "Save" will they be shown in red.

Screenshot 2

For comparison, in version 2, these were marked with an *.

Goal: An asterisk (*) is displayed behind the mandatory metadata fields.

@andre-hohmann
Copy link
Collaborator

@matthias-ronge : Maybe this related to the following issue?

@matthias-ronge
Copy link
Collaborator Author

You wrote #3403 − you should decide if this is a duplicate of what you meant.

@andre-hohmann
Copy link
Collaborator

It seems, as if it is very similar, but not the same problem:

But it seems to be a good example that we some labels to connect similar issues.
Here, it is a good point to mark mandatory fields with an asterix (*) to express for the users, that the field is a mandatory one.
Still, it needs needs to be checked during the creation of the process, that mandatory fields have to contain a value.
Both demands should be combined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature ruleset ruleset functions and configuration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants