Trying to set "include-all" attribute for Auditor or SuperUser role will end up with
"Failed to save XYZ" error message on save.
I can see two issues in this
1) Usability - Error message should at least provide the information about why the operation failed
2) AFAIK "include-all" can be set for every role mapping. Why is this in console different? If this is meant as extra level of protection (I understand that both SuperUser and Auditor can read sensitive resources) then Administrator role should be included in this restriction as well.
Rephrasing this issue as it was explained to me that this is the intended behavior.
Thus the only issue remaining here is usability - "Failed to save" doesn't provide much information about what happened.. .
After revisiting this issue I think that the best approach would be to hide "Auditor" and "SuperUser" roles from "Add role mapping" and "Edit role mapping" dialogs for users with administrator role. This will avoid the confusion completely.
Harald Pehl <email@example.com> updated the status of jira HAL-281 to Coding In Progress
Harald Pehl <firstname.lastname@example.org> updated the status of jira HAL-281 to Resolved
Harald Pehl <email@example.com> made a comment on jira HAL-281
When the operation is not allowed, the error message reflects this.
New message is certainly an improvement, however I am still not satisfied.
Message "You don't have the permissions to access this resource!" is obviously incorrect, as I can read the resource, and thus confusing. Something like "You don't have the permissions to perform this operation!" might be more suitable.
Modified Doc Text content and marked for inclusion in the 6.2 Release Notes document.
In agreement with Catherine we've decided that UX issues will be tracked separately.
Issue moved under the UX component.
Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
UX will add this to the list of messages shown throughout the console that we need to review and improve with Dev & Doc.
Can me make the change in comment 7 and close this?
Harald Pehl <firstname.lastname@example.org> updated the status of jira HAL-292 to Resolved
Changed according to comment 7
DR3 still contains the message
"Failed to save Auditor
You don't have the permissions to access this resource!"
see comment 7
The error message now reads as "You don't have the permissions to perform this operation!"
See updated doc text.