-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an "owner" field to all primary objects #988
Comments
What permissions do you predict being needed to change the Owner field? Our current system has a Reserved For field to track who is using a given test device in the lab, and it changes fairly frequently. We don't have any permissions around changing the field, as it mostly serves to ensure that people don't accidentally clobber boxes that other people are using with automated scripts, or to track down who is currently using a box if you're curious. It would be neat if we could keep this process but also adopt Owner. |
Would you propose that the object is inherited if not set... Similar to how tenant is inherited for prefixes? |
This records a single 'owner' against an item. I think it would be useful if:
|
Hi, I suspect this feature originated from itil practices. If so I would replace "owner" with "accountable" and add responsible. In itil these are not the same. PS: I also needed this and solved this by using custom fields (accountable & responsible). |
With the addition of object-based permissions in v2.9, this doesn't seem particularly useful anymore: the new permissions offer a much more flexible approach to designating "ownership" of objects. I'm going to close this issue, but if anyone still has a need for it, please open a new FR citing your specific use case. |
Issue type: Feature request
Originally proposed by @CassioFabius in #979. This would entail adding a new optional
ForeignKey
field pointing to the User model. Each primary object type (listed below) could be assigned an owning user. Proposed objects include:The text was updated successfully, but these errors were encountered: