Therefore, the POST needs to be send to /api/v3/work_packages/:id/relations. The body still needs to contain the from and to for both work packages participating in the relation which, given the path, shouldn't be necessary. Be that as it may, the body should look something like:
Therefore, the POST needs to be send to /api/v3/work_packages/:id/relations. The body still needs to contain the from and to for both work packages participating in the relation which, given the path, shouldn't be necessary. Be that as it may, the body should look something like:
Replies (2)
Hi Thomas,
relations are currently always created by an endpoint nested under work_packages. This helps finding the work packages for which creating a relationship to is possible and also those for which a relationship to the work package already exists.
Therefore, the POST needs to be send to
/api/v3/work_packages/:id/relations
. The body still needs to contain thefrom
andto
for both work packages participating in the relation which, given the path, shouldn't be necessary. Be that as it may, the body should look something like:Hope that helps you.
Regards,
Jens
Jens Ulferts wrote:
Oh, I've just look in the relations routes not in work_packages ones.
Thanks for your help Jens !