Actions
Defect #37685
closed
Read-only field permission for the project field is ignored if the current project has subprojects
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
When project_id marked as readonly in workflow/permissions for a role say role1, if a user with role1 try to create an issue in a leaf project, everything is ok. But if that user try to create new issue in a project that has some subprojects, that projects was shown in issue creating form.
Files
Updated by
Updated by salman mp over 1 year ago
- File test_global_new_issue_and_hierarchy_projects_new_issue.patch test_global_new_issue_and_hierarchy_projects_new_issue.patch added
I have no experience in writing tests, but I hope these two tests can show that cases.
Updated by salman mp over 1 year ago
- File test_global_new_issue_and_hierarchy_projects_new_issue.patch test_global_new_issue_and_hierarchy_projects_new_issue.patch added
second test function's name was wrong and this file fixed that.
Updated by Go MAEDA over 1 year ago
- Category set to Issues workflow
- Status changed from New to Confirmed
Updated by Go MAEDA over 1 year ago
- Target version set to 4.2.8
Setting the target version to 4.2.8.
Updated by Go MAEDA over 1 year ago
- Subject changed from Show project field in Issue create form when project_id is not permitted field to Read-only field permission for the project field is ignored if the current project has subprojects
- Status changed from Confirmed to Resolved
- Assignee set to Go MAEDA
- Resolution set to Fixed
Committed the fix. Thank you for your contribution.
Actions