User story #4592
closed
User story #4662: When a report was not received, call it "No report" instead of "No Answer" in compliance details
When a report was not received, call it "No report" instead of "No Answer" in compliance details
Added by Nicolas CHARLES over 10 years ago.
Updated over 9 years ago.
Category:
Web - Compliance & node report
Description
Status "No answer" is kind of misleading, we are not asking quesiton, but rather have a "state" for a Directive
So we'd need to find a better name for this
What about "No status" or "Not available"? Or maybe even better "No report". Would also be nice to disable a status if it's known, but you can't do anything about it for the moment, but maybe that's a bit offtopic. :)
- Subject changed from Change No answer for a better term to Change "No answer" status to "No report"
- Status changed from New to 8
- Assignee set to Nicolas CHARLES
I like "No report" a lot! It describes exactly what the situation is: we have no idea if the node is dead or alive, exists or not, has network issues, or the agent is disable, all we know is that we were expecting a report, but didn't get one.
Thanks Dennis!
- Status changed from 8 to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/477
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Tracker changed from Bug to User story
- Subject changed from Change "No answer" status to "No report" to When a report was not received, call it "No report" instead of "No Answer" in compliance details
- Category changed from Web - Config management to Web - Compliance & node report
- Tracker changed from User story to Enhancement
- Pull Request set to https://github.com/Normation/rudder/pull/477
- Status changed from Pending release to Released
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF