Setting Category/Version as a required field causes error in projects without categories/versions
|Assignee:||Jean-Philippe Lang||% Done:|
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.
#2 Updated by Go MAEDA over 3 years ago
The same can be said about the "Target version".
I think that the cause of annoyance is that the user cannot know the field is required before submitting the form because "Category" and "Target version" are hidden when they don't have any value.
I think the solution for this issue is to implement #18004. It makes those fields visible at all time, so the user can understand the field is required at a glance whether or not those fields have values.
#4 Updated by Jean-Philippe Lang over 3 years ago
- Subject changed from Setting Category as a required field causes error in projects without categories to Setting Category/Version as a required field causes error in projects without categories/versions
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 3.2.0
- Resolution set to Fixed
Fixed in r14733.