Defect #20583
closed
Setting Category/Version as a required field causes error in projects without categories/versions
Added by Robert Barnebeck over 8 years ago.
Updated over 8 years ago.
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.
I will +1 this as it's annoying to have to create a single category for a project when it's required for another project.
Ideally, however, this should be fixed as part of #1853 by having the workflow per-project.
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.
- Related to Feature #18004: Do NOT hide category and version fields on issue form when no category or version is configured added
- 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
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by