Version 7 bugs
Some of these may be new, and some may be still around from previous versions but have not been addressed yet. All of these symptoms are appearing on a clean install of v7.0 on Windows XP while using the latest version of Firefox.
[list=1:15b25b84eb] * When adding items to a subcategory, only the first 10 are visible in the configuration wizard. When you bring up the tree view, you can see all the ones you've added, but it does not make them visible to delete or edit them. This could potentially be a big problem. This does not appear to be a problem with subcategories, just items.
* When you set the subcategory field on the request form as mandatory, but you don't have subcategories under all the main categories, it is not possible to submit a request under one of those main categories. The same is true of items, subcategories without items cannot be used. This is a big problem because I want to force users to select a subcategory or item if they are available, but still use categories without them. The only workaround for this is to create a dummy subcategory or item where needed, which is not a very good option, as it will confuse end users. This problem was also present in 6.0.
* This one relates to the previous bug, and was present in 6.0 as well. If you set fields such as subcategory and item as mandatory fields on the request form, and then later disable the mandatory setting, the request closing rules still require that those fields be filled when closing a request. Perhaps this is by design, but it is not clear to admins that those request close rules are automatically activated but not deactivated. I thought it was a serious bug until I just now discovered the cause of the problem.
This is all I have found for now. I will report back with any more I find.
[list=1:15b25b84eb] * When adding items to a subcategory, only the first 10 are visible in the configuration wizard. When you bring up the tree view, you can see all the ones you've added, but it does not make them visible to delete or edit them. This could potentially be a big problem. This does not appear to be a problem with subcategories, just items.
* When you set the subcategory field on the request form as mandatory, but you don't have subcategories under all the main categories, it is not possible to submit a request under one of those main categories. The same is true of items, subcategories without items cannot be used. This is a big problem because I want to force users to select a subcategory or item if they are available, but still use categories without them. The only workaround for this is to create a dummy subcategory or item where needed, which is not a very good option, as it will confuse end users. This problem was also present in 6.0.
* This one relates to the previous bug, and was present in 6.0 as well. If you set fields such as subcategory and item as mandatory fields on the request form, and then later disable the mandatory setting, the request closing rules still require that those fields be filled when closing a request. Perhaps this is by design, but it is not clear to admins that those request close rules are automatically activated but not deactivated. I thought it was a serious bug until I just now discovered the cause of the problem.
This is all I have found for now. I will report back with any more I find.