In Slack, it was requested that items like projects can reuse their unique attributes without having conflicts with deleted items. For instance, I should able to create, for a tenant, a project with the same name, even if there is another deleted project with that same name:
TODO:
- Apply this rule for projects and activities.
- Check whether other items follow this policy.
- Specify explicitly the description of the items as not required in the API namespaces
- Re-run the migrations applying this policy (they must be re-written)
In Slack, it was requested that items like projects can reuse their unique attributes without having conflicts with deleted items. For instance, I should able to create, for a tenant, a project with the same name, even if there is another deleted project with that same name:
TODO: