Allow deleting dependent resources when they have not yet been created #5890
Replies: 5 comments 1 reply
-
|
hmm, I though we were already doing this, but maybe not as an oversight we already have the logic for checking for "create" permission for new resources but "edit" for existing ones: would look something similar, but for delete Related, but removing independent resource doesn't require delete permission as rather than deleting the independent resource, it simply removes the reference to it: |
Beta Was this translation helpful? Give feedback.
-
|
Mentioned as a big QOL improvement if we can resolve soon |
Beta Was this translation helpful? Give feedback.
-
|
This might be a 5 line PR (excluding testing) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @grantfitzsimmons - just wondering if there was an update on this? It has come up again from a user and likely to have more users using the clone function soon too. Not being able to delete dependent resources that aren't needed is a bit of a sticking point. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@maxpatiiuk Can you tell us which 5 lines? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Requested by: CSIRO on Asana
Beta Was this translation helpful? Give feedback.
All reactions