Project

General

Profile

Actions

User story #8570

open

Missing API command to move Rules or Groups to another category

Added by François ARMAND over 8 years ago. Updated almost 7 years ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
API
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Currently, the API is missing what is needed to move groups (resp. Rules) to another category.

I see 3 possibilities:
- 1/ update the "update group categorie" (resp group category) to allow to specify a list of group
- 2/ update the "update group" (resp rule) to allow to specity the category, something like: "groups/${groupid}?newParentCategory=uuid"
- 3/ create a new URL to move groups (resp rules), something like "groups/${groupid}/move/${categoryid}" or "groups/${groupid}/move?dest=categoryid"

Some remarks:

1/ is clearly the weakest (I want to do something on the group, not the category).

2/ or 3/ could be OK, but something should be improved to avoid something too much looking like a GET URL.
I prefer 3/ to 2/, because I would prefer to semanticaly separate an update semantic to a move one. But perhaps there is some LDAP old memories for that. (on the contrario, have the category being a property of the group (resp rule) is more like a tag, and would make possible to have a group (resp rule) in several category easy).

Actions

Also available in: Atom PDF