It's impossible to assign a requisition group to a different supervisory node

Description

When I was testing OLMIS-5981, I noticed that it's impossible to change the supervisory node to which a given requisition group is assigned when updating the requisition group.

Reproduction steps:

  1. Change the supervisory node for a requisition group (e.g. ID: 41d5cae2-a65c-4027-a6f9-0d5c1b3202fc) with the use of the PUT requisitionGroups/id endpoint from the SN (ID: 901085b9-04d6-49d8-80de-df1c7a7a59ac) to e.g. SN (ID: 9f470265-0770-4dd1-bd5a-cf8fe3734d79). 200 is returned, and the SN is seemingly changed accordingly. The GET requisitionGroups/id endpoint also returns a correct response - the SN is updated, as in the JSON:

  2. Query the GET supervisoryNodes/id endpoint with the ID of the new SN, e.g. (9f470265-0770-4dd1-bd5a-cf8fe3734d79).

  3. The response contains the ID of a different requisition group than the one which had been updated, e90da490-a371-4c2f-83c3-7c1dc9748d48, instead of 41d5cae2-a65c-4027-a6f9-0d5c1b3202fc, as visible below:

When I queried the GET supervisoryNodes/id endpoint for the data of the original SN, everything worked correctly - the SN no longer contained the RG.

Expected results:

  • It should be possible to change the requisition group's supervisory node.

Environment

None

Assignee

Paweł Pinker

Reporter

Joanna Bebak

Labels

Epic Link

Components

Fix versions

Priority

Major
Configure