Argonaut task doesn't use ACL based on branch
Descriptive title for this enhancement
Argonaut task doesn't use ACL based on branch
Actual behavior
Argonaut task need an ACL on the root so that user could use scheduling
Expected behavior
Add ACL on a branch and the user may directly use scheduling. They not need Argonaut task right on root
Step by step description of new behaviour
- Add acl on a branch
- Tick a system and launch a scheduling
- Have the right to make the scheduling
Benefits
More easy to manage the ACL because we not need to remember that Argonaut task need ACL on root
Possible Drawbacks
None
Applicable Issues
Always when we use the Argonaut tasks