Restrict or pre-select status choices #15224
Unanswered
Azmodeszer
asked this question in
Q&A
Replies: 1 comment
-
I came across #1426. I assume nothing ever came of it? I could create a custom status order from scratch in FIELD_CHOICES and simply have Submitted be first, but that would apply globally... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My apologies if this is already covered in the documentation or a thread here. I did a search, but came up empty.
I am currently in the process of preparing a submission system for our Netbox instance that will restrict "regular" users to adding/modifying select objects only with a custom status "Submitted" (or similar). These in turn will then need to be approved (i.e. changed to Active or whichever applies) by the administrator(s). So far things are shaping up nicely and using a mixture of object permissions and custom constraints I think I've got something workable.
That being said, and this is more cosmetic than anything, I was wondering if it's possible to actually restrict the available dropdown choices for the Status field based on group membership/permissions, so that regular users only see the status they can actually work with. Alternately, a way to pre-select the "Submitted" status would work as well.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions