-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.11.5
Description of problem:
[RFE] promote_or_remove_content_views and promote_or_remove_content_views_to_environments both role needs to be renamed or merged
How reproducible:
1. Create a role "lifecycle Role" with permissions "publish_content_views" and "promote_or_remove_content_views"
2. set it to the user "ansible_provsion", but this user is unable to use the promote option.
3. Along with this role, below standard roles are also set for the user.
Roles:
Edit hosts
Viewer
View hosts
Actual results:
Scenario1.:
With this permission set user is able to promote and publish a new version as below:
Go to content >> content view >> select the cv >> publish new version >> enable the promote tab
Scenario2:
If we click on the existing version of any CV and try to publish it he is getting the below error:
Error: Could not find content_view_version resource with id 4. Potential missing permissions: promote_or_remove_content_views, promote_or_remove_content_views_to_environments
4. Now, if we add promote_or_remove_content_views_to_environments permission then the user can perform both scenarios.
Expected results:
Either these roles should be merged or renamed so that it will serve their purpose as expected.
that is,
- promote_or_remove_content_views: Only for new versions.
- promote_or_remove_content_views_to_environments: for all including existing.
- impacts account
-
SAT-27717 Lifecycle environments are not shown when changing the host content source,even if the edit_host permission is granted.
- In Progress