Defect #2619
closed
Categories field displays when no categories exist and user can't add new
Added by Brad Beattie about 15 years ago.
Updated about 15 years ago.
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.
- Status changed from New to Resolved
- Target version set to 0.8.1
- Resolution set to Fixed
Hrm. This fix hides the ability to add new categories to those that would otherwise have access to do so. :(
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?
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. ;)
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.
- Status changed from Resolved to Closed
Merged in 0.8 branch in r2425.
- Related to Feature #18004: Do NOT hide category and version fields on issue form when no category or version is configured added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by