Actions
Defect #20583
closedSetting Category/Version as a required field causes error in projects without categories/versions
Defect #20583:
Setting Category/Version as a required field causes error in projects without categories/versions
Resolution:
Fixed
Affected version:
Description
When I go to "Administration" --> "Workflow" --> "Fields permissions", then I can set the "Category" as required. The effect now is, that when I create or edit an issue, the field "Category" is required.
But if the project has no defined categories, this validation accidently tells me, that no category is selected. In my opinion the validation should only check in projects, where one ore more categories are present.
Actions