Feature #12915
closed
Display Category field back again if no categories are defined in project and user can create categories
0%
Description
Now that it is possible to define core issue form fields involved in the workflow, there is no more reason to hide the Category field if no categories are defined in the project and the user has the right to create new Categories.
See #2619#note-3 for statement about why it as hidden.
Note: no sure but this issue might be applicable to Version field too.
Related issues
Updated by Jean-Philippe Lang about 11 years ago
there is no more reason to hide the Category field if no categories are defined in the project
If some projects don't use Categories but some other do, the field can not be disabled by the workflow setup.
Updated by Etienne Massip about 11 years ago
- Status changed from New to Closed
- Resolution set to Wont fix
Jean-Philippe Lang wrote:
there is no more reason to hide the Category field if no categories are defined in the project
If some projects don't use Categories but some other do, the field can not be disabled by the workflow setup.
Sure, that's why I didn't propose it as candidate. In some way this issue is related to those tasking the ability to (re?)define WF at project level.
We can close it for now, guess it' meaningless until such functionality is actually implemented.
Updated by Etienne Massip about 11 years ago
Jean-Philippe Lang wrote:
If some projects don't use Categories but some other do, the field can not be disabled by the workflow setup.
The Category field is displayed empty after the issue has been created in a project which has no category defined, this is inconsistent?