Open tanhl2000 opened 2 years ago
Changed from low to veryLow. Cosmetic issue as the team feels that it is not wrong that this message is displayed while an empty list is shown. An empty list perfectly conveys that no policy has been assigned, but we recognise that an explicit message stating that there is no policy would be a cosmetic improvement. Thank you sir/ma'am
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: Thank you for the insightful response, however I still believe this should be low. When the message says "Listed all policies for David Li" however the client list is still what is being shown may confuse users and make them think that there is an error with the command. If an empty list were to be shown, I believe that would be indeed be a good indication to the users that their command was indeed run on the backend and there are no policies assigned to David Li, however in this case leaving the client list is confusing to me.
Initial state (to reproduce): use the listAssigned command on a client with no policies assigned
Expected: Message informing me there is no policy assigned
Actual:
The empty space after makes me doubt if there was an error in the running of the command.
severity low as this may confuse some users, but would not be a hindrance to usability. FeatureFlaw as I believe this was intended.