-
Bug
-
Resolution: Can't Do
-
Major
-
None
-
None
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
If an erroneous value is given for a reassignment timer for "Expires At" (which does not correspond to a time definition 2m, 4h, 6d, etc.), the timer is defined with the value 0. We think that it should be under control and warn user about this error.
- clones
-
RHPAM-3586 [GSS] (7.z) Workflow with reassignment timer with an incorrect "expiresAt" value causes the creation of a timer at 0
- Closed
-
RHPAM-3587 [GSS] (7.z) Runaway of the reassignment timer if the value "Expires At" is at 0
- Closed