-
Bug
-
Resolution: Duplicate
-
Medium (View bug fix roadmap)
-
None
-
8.21.0, 8.20.6
-
None
-
8.2
-
1
-
Severity 2 - Major
-
NOTE: This is for JIRA Server.
Issue Summary
Custom Fields Filters in Advanced Roadmaps shows all available options for that custom field including those for which the User has no Permission to view
Steps to Reproduce
- Create a custom field such as"Custom_field_for_testing".
- Create Configuration contexts for this custom field such that each project has different options available for this custom field such as Options A,B,C available for Project A and S,C,R available for Project B.
- Create a user "User 1" and give him access to "Project A"
- Create a Plan whose issue source is "Project A" and add this custom field "Custom_field_for_testing" to the plan.
- When User A tries to filter the custom field "Custom_field_for_testing" in the plan, all the available values for this custom field are displayed in the drop down, including those for which the User has no permissions to view.
(Even though "User A" has permissions just for "Project A", he is able to see all the options in the filter for the custom field including S,R,C.
Expected Results
When a user tries to filter a custom field in the plan, only those options must be shown in the dropdown for which he has access to.
Actual Results
When a user tries to filter a custom field in the plan, only those options for which he has the permissions to view must be shown.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
https://jira.atlassian.com/browse/JPOSERVER-2772