Part of story #20111 change features priority How to test: - call PATCH /api/v1/program_increment/$id/content with a payload like this: { "add": [{"id": <feature_id>}] } - if the given <feature_id> does not exist (for example 0), you will get a 400 error - if the given id belongs to an artifact that is not part of the Program (for example a User Story ID in a Team), then you will get a 400 error - if the given id belongs to an artifact that is not a Feature (for example another tracker like Activity, that is not part of the program's Plan), then you will get a 400 error - The following payload with more than one "feature objects" should be rejected with an error { "add": [{"id": <feature_id>}, {"id": <other_feature_id>}] } - The following payload should be accepted but will lead to error 501 (Not implemented) for now. Later we will add reordering, and it's valid to reorder features without adding a new feature at the same time: { "add": [] } All other valid payloads should lead to error 501 (Not implemented) for now Change-Id: Iddaac063a1cbd17d499ff52547aa3c097814bcd2

+180 −19

Author

Joris MASSON (jmasson) 2021-04-21 16:06

Committer

Joris MASSON (jmasson) 2021-04-22 10:15

Hash 584ab468c0b8abfed23388e93b799b910b4ef1ee

Parent ee06f6fc69dce43222e01b53b1de8615dc71e408

Reference git #tuleap/stable/584ab468c0b8abfed23388e93b799b910b4ef1ee