Defect #2619
closed
Categories field displays when no categories exist and user can't add new
0%
Description
As a user with no access to create new categories, create a new ticket in a project with no categories. The category drop down displays, although no options exist. It probably shouldn't show, much like target version doesn't display when no options are there.
Related issues
Updated by Jean-Philippe Lang almost 16 years ago
- Status changed from New to Resolved
- Target version set to 0.8.1
- Resolution set to Fixed
This was fixed in r2270.
Updated by Brad Beattie almost 16 years ago
Hrm. This fix hides the ability to add new categories to those that would otherwise have access to do so. :(
Updated by Jean-Philippe Lang almost 16 years ago
True, I knewn about that. But it also hides the field for those who do not want to use categories at all.
You can create a first set of categories in project settings then use the shortcut when one is missing.
I think it's pretty fair?
Updated by Brad Beattie almost 16 years ago
Jean-Philippe Lang wrote:
True, I knewn about that. But it also hides the field for those who do not want to use categories at all.
You can create a first set of categories in project settings then use the shortcut when one is missing.
I think it's pretty fair?
Yeah, the remaining issue of not being able to initiate categories from the new issue page is certainly of a much lower priority. I'm willing to ignore it for now. ;)
Updated by Axel Voitier almost 16 years ago
The empty drop down and the link could still be displayed when the user is authorized to create categories, no?
But that move the remaining minor issue on a new one: when we NEVER want to use categories.
Updated by Jean-Philippe Lang almost 16 years ago
- Status changed from Resolved to Closed
Merged in 0.8 branch in r2425.
Updated by Jean-Philippe Lang about 9 years ago
- Related to Feature #18004: Do NOT hide category and version fields on issue form when no category or version is configured added