User story (meta) #622

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

Added by Jonathan CLARKE about 4 years ago. Updated about 1 month ago.

Status:Rejected Start date:2011-01-05
Priority:3 Due date:
Assignee:- % Done:

0%

Category:Webapp - Node management
Target version:Ideas (not version specific) Estimated time:2.00 hours
Needs translating:Yes

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

History

#1 Updated by Jonathan CLARKE about 4 years ago

  • Status changed from New to Qualified

#2 Updated by François ARMAND over 3 years ago

  • Target version set to Ideas (2.5 specific)

#3 Updated by Jonathan CLARKE over 3 years ago

  • Needs translating set to Yes

#4 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from Ideas (2.5 specific) to Ideas (not version specific)

#5 Updated by François ARMAND about 1 month ago

  • Status changed from Qualified 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.

Also available in: Atom PDF