Project

General

Profile

Actions
Copy link

User story #622

closed

E02-01: Déterminer les critères « unusual »

Added by Jonathan CLARKE almost 14 years ago. Updated about 10 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Ideas (not version specific)
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

  • Liste de critères sur lesquels l'arrivée d'un nouvel inventaire depuis un serveur existant déclenche l'apparition dans « Unusual changes »
  • Réflexion sur les tests à faire pour implémenter ces critères
Actions
Copy link
 #1

Updated by Jonathan CLARKE almost 14 years ago

  • Status changed from New to 8
Actions
Copy link
 #2

Updated by François ARMAND about 13 years ago

  • Target version set to 24
Actions
Copy link
 #4

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 24 to Ideas (not version specific)
Actions
Copy link
 #5

Updated by François ARMAND about 10 years ago

  • Status changed from 8 to Rejected

Unusual changes were never implemented, and finding criteria to find them has proved to be VERY hard to find, due to the diversity of behavior, especially upon virtual run time.

Closing it, a new (full) user story could be open about "unusual changes" if needed.

Actions
Copy link

Also available in: Atom PDF