Both models are only supposed to be visible
to users that have some basic permissions in at least
one project. While the desired scoping is not very fine grained
(you either see all or nothing), it still makes sense for all
models to have such a scope for consistency purposes.
Role name being limited to 30 characters does not work anymore with some
translations of default seeded roles. Raising the limit to 256
characters like a lot of other models.
Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded.
Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013
Uses FactoryBot to keep and maintain specific records in a special transaction that does not get removed after each spec.
They automatically are created whenever first hitting them.
This makes an excellent time saver for items that are commonly used, such as an admin user account
This reverts commit b05a8f7b54.
The release/10 branch received a revert that was applied after changes
from dev unwillingly where merged into it. But when merging release/10.0
back into dev, that revert was also applied to dev where the changes are
indeed wanted. So we revert the revert for dev.
In case the fixed version and the status of a work package are both closed, the status of a work package cannot be altered any more. Attempting it will result in an error.
Before the fix, the possible status calculation would not factor in that situation and the status would be marked as writable regardless as well. Therefore, the frontend would display a list of statuses even though selecting one would do nothing at all.
Now, the status property is marked as non writable in such a situation and the status list will only contain the current status. As we only fetch the form after a click on the edit field, we can only disable the field after that which is a bit weird.
* replace alias_method_chain
* remove deprecation silencing
* bump controller-testing
* introduce permitted params for settings
* replace various deprecations in controllers
* remove deprecation silencing for legacy_specs
* remove `puts` from spec
* replace deprecated access to errors
* remove unnecessary AR::Parameters usage in spec
* specify error to expect
* replace deprecations
* replace deprecated action calls in legacy function specs
* replace deprecations in functional controller tests
* replace deprecations in controllers/controller_specs
* remove params parser which does not seem to be in effect
It is registered for the content type :exclude which makes no sense as it should deal with :json. The desired behaviour of the api dealing with parsing errors is working with or without the code.
* replace deprecations in unit specs
* replace alias_method_chain
[ci skip]
Jan Sandbrink