View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0020054||mantisbt||administration||public||2015-08-26 12:41||2023-03-15 08:20|
|Target Version||2.20.0||Fixed in Version||2.20.0|
|Summary||0020054: Cant modify configuration for All projects if only one project exists|
Where there only exists one project, the project selector is not shown, and current project is default for that only project.
If entering Administration pages, where configuration can be made eiter for "All projects" and specific projects, user is unable to modify configuration for "All projects" as there is no way to select that option.
Usually is not a problem because it wont happen once there are more than one project created.
some relatively simple fixes:
more proper fix:
|Tags||No tags attached.|
|related to||0007956||closed||cproensa||Disable project selection for users with only one project|
|has duplicate||0025134||closed||atrol||Cant edit configuration for ALL_PROJECTS when only one project exists|
|related to||0020055||new||More visbility on current project for adminitration pages, dedicated selector|
|related to||0032131||closed||dregad||access_project_array_filter can lead to many SQL requests|
MantisBT: master 2ec8df69
|Don't apply single project logic for some users
Eventhough the project selector may be hidden when there are not
multiple projects to choose from, it is still needed for editing manage
and configuration pages that apply to either specific project or
Here we add a condition that if the user has access to manage pages, the
project selector is never hidden, and both the specific project and
ALL_PROJECTS are available to be used.
|mod - core/current_user_api.php||Diff File|
|mod - core/layout_api.php||Diff File|