Supervisory Node is not reset after rejection

Description

Steps to reproduce

  1. log in as srmanager4, create and submit a requisition

  2. log in as smanager4 and authorize the requisition

  3. log in as dsrmanager and approve the requisition

  4. log in as psupervisor and REJECT the requisition

  5. again submit and authorize the requisition

Expected

  • dsrmanager should see the requisition and be able to approve it

  • psupervisor should not be able to see the requisition and approve it

Actual

  • dsrmanager can't approve the requisition - it is not visible on the approve screen

  • psupervisor can approve the requisition but he should not

Note the same behaviour is for an emergency requisition

Probably the source of the bug: since the SN is not reset, we are immediately brought to the second approval after authorization.

Needed change:
Set the supervisory node to null when the requisition is rejected.

Environment

None

Assignee

Klaudia Pałkowska

Reporter

Łukasz Lewczyński

Labels

Story Points

1

Time tracking

6h

Components

Sprint

None

Fix versions

Affects versions

Priority

Blocker
Configure