Project

General

Profile

Actions

User story #6646

open

Document status for unknow return code in jobscheduler technique

User story #6646: Document status for unknow return code in jobscheduler technique

Added by Benoît PECCATTE over 10 years ago. Updated almost 8 years ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Techniques
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

In the jobScheduler technique, it is possible to interpret different return code into different status.
But the 3 statuses are given (kept, repaired and error) which means we have to explicitly list all return codes.
What is the default status for codes not listed ? and if it is an error we need a way to list all codes in a simple way.

Updated by Vincent MEMBRÉ over 10 years ago Actions #1

  • Target version changed from 2.10.15 to 2.10.16

Updated by Vincent MEMBRÉ over 10 years ago Actions #2

  • Target version changed from 2.10.16 to 2.10.17

Updated by Vincent MEMBRÉ about 10 years ago Actions #3

  • Target version changed from 2.10.17 to 2.10.18

Updated by Vincent MEMBRÉ about 10 years ago Actions #4

  • Target version changed from 2.10.18 to 2.10.19

Updated by Vincent MEMBRÉ about 10 years ago Actions #5

  • Target version changed from 2.10.19 to 2.10.20

Updated by Vincent MEMBRÉ almost 10 years ago Actions #6

  • Target version changed from 2.10.20 to 277

Updated by Vincent MEMBRÉ almost 10 years ago Actions #7

  • Target version changed from 277 to 2.11.18

Updated by Vincent MEMBRÉ almost 10 years ago Actions #8

  • Target version changed from 2.11.18 to 2.11.19

Updated by Vincent MEMBRÉ over 9 years ago Actions #9

  • Target version changed from 2.11.19 to 2.11.20

Updated by Vincent MEMBRÉ over 9 years ago Actions #10

  • Target version changed from 2.11.20 to 2.11.21

Updated by Vincent MEMBRÉ over 9 years ago Actions #11

  • Target version changed from 2.11.21 to 2.11.22

Updated by Vincent MEMBRÉ over 9 years ago Actions #12

  • Target version changed from 2.11.22 to 2.11.23

Updated by Vincent MEMBRÉ over 9 years ago Actions #13

  • Target version changed from 2.11.23 to 2.11.24

Updated by Vincent MEMBRÉ about 9 years ago Actions #14

  • Target version changed from 2.11.24 to 308

Updated by Vincent MEMBRÉ about 9 years ago Actions #15

  • Target version changed from 308 to 3.1.14

Updated by Vincent MEMBRÉ about 9 years ago Actions #16

  • Target version changed from 3.1.14 to 3.1.15

Updated by Vincent MEMBRÉ about 9 years ago Actions #17

  • Target version changed from 3.1.15 to 3.1.16

Updated by Vincent MEMBRÉ about 9 years ago Actions #18

  • Target version changed from 3.1.16 to 3.1.17

Updated by Vincent MEMBRÉ almost 9 years ago Actions #19

  • Target version changed from 3.1.17 to 3.1.18

Updated by Vincent MEMBRÉ over 8 years ago Actions #20

  • Target version changed from 3.1.18 to 3.1.19

Updated by Benoît PECCATTE over 8 years ago Actions #21

  • Tracker changed from Bug to User story

Updated by Vincent MEMBRÉ over 8 years ago Actions #22

  • Target version changed from 3.1.19 to 3.1.20

Updated by Vincent MEMBRÉ over 8 years ago Actions #23

  • Target version changed from 3.1.20 to 3.1.21

Updated by Vincent MEMBRÉ over 8 years ago Actions #24

  • Target version changed from 3.1.21 to 3.1.22

Updated by Vincent MEMBRÉ over 8 years ago Actions #25

  • Target version changed from 3.1.22 to 3.1.23

Updated by Vincent MEMBRÉ about 8 years ago Actions #26

  • Target version changed from 3.1.23 to 3.1.24

Updated by Vincent MEMBRÉ about 8 years ago Actions #27

  • Target version changed from 3.1.24 to 3.1.25

Updated by Benoît PECCATTE about 8 years ago Actions #28

  • Target version changed from 3.1.25 to 4.1.9

Updated by Vincent MEMBRÉ almost 8 years ago Actions #29

  • Target version changed from 4.1.9 to 4.1.10

Updated by Benoît PECCATTE almost 8 years ago Actions #30

  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions

Also available in: PDF Atom