Project

General

Profile

Actions
Copy link

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 almost 11 years ago. Updated over 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
2.10.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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

Actions
Copy link
 #1

Updated by Dennis Cabooter almost 11 years ago

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. :)

Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 11 years ago

  • 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!

Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from 8 to In progress
Actions
Copy link
 #4

Updated by Nicolas CHARLES almost 11 years ago

  • 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
Actions
Copy link
 #5

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 11 years ago

  • 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
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 11 years ago

  • Tracker changed from User story to Enhancement
  • Pull Request set to https://github.com/Normation/rudder/pull/477
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 11 years ago

  • Parent task set to #4662
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.0~beta1, which was released today.
Check out:

The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000084.html
    The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
    Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions
Copy link
 #11

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from Enhancement to User story
Actions
Copy link

Also available in: Atom PDF