-
Notifications
You must be signed in to change notification settings - Fork 159
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
Create tags #7135
Comments
Added appendix links. |
Does not make much sense in my opinion. The idea was to have a hardcoded maximum because we do not know what issues will arise when extended attributes can no longer be written. Allowing an admin to configure it will make him run into exactly these problems sooner or later. Also: How should an admin know which number of tags is feasible for the system? He can't. This is a technical limitation. Only we can know how many tags can be supported. So I don't see the point in making it configurable. Admins can't know which value should be used and if they raise the number too much they will run into unforseeable technical problems sooner or later. |
ok, if this is the reasoning, then lets not make it configurable but hardcoded. updated the AC |
User Story
Value
Acceptance Criteria
<enter>
"stages" the Tag, Button "Save" adds the Tag to the fileVERY Important
->very important
X
or removes the Tag from the form, "Save" removes the tag finally from the file.Automated tests
Unittest:
E2E Tests
Definition of ready
Definition of done
Functional requirements
functionality described in the user story works
acceptance criteria are fulfilled
Quality
codre review happened
CI is green
critical code received unit tests by the developer
automated tests passed (if automated tests are not available, this test needs to be created and passed
Non-functional requirements
no sonar cloud issues
Note on terminology:
"File" is always meant as "file and folder".
The text was updated successfully, but these errors were encountered: