Hello Martin, Checking the old state in a state machine rule is generally considered a bad practice. Could you please describe the workflow you try to implement?
i need a state "EstimationRequest". In this state the Developer has to set the Estimation. When the Estimation is set he has to set back the the state to the State setted before. For Example: New -> EstimationRequest; EstimationRequest -> New
EstimationRequest could be set from State: New or Reopened: When Old State = Reopened, it is impossible to transit from EstimationRequest -> New. In this case it is only possible EstimationRequest -> Reopened.
Checking the old state in a state machine rule is generally considered a bad practice. Could you please describe the workflow you try to implement?
Best regards,
Alexander
i need a state "EstimationRequest". In this state the Developer has to set the Estimation. When the Estimation is set he has to set back the the state to the State setted before. For Example: New -> EstimationRequest; EstimationRequest -> New
EstimationRequest could be set from State: New or Reopened:
When Old State = Reopened, it is impossible to transit from EstimationRequest -> New.
In this case it is only possible EstimationRequest -> Reopened.
I see. I'd suggest introducing two similar states (e.g. ToBeEstimated and ToBeReestemated)/
Regards,
Alexander