Select fields for workflow locking
When creating an item type, you can specify "required" or "suspect". It would also be nice to exclude some fields from system locking. Here's my scenario:
I have reviewed a bunch of items and marked them approved and applied a system lock and now I need to:
These are actions that are common to perform post-approval that are very tedious to get right with system locking and workflows.
I have reviewed a bunch of items and marked them approved and applied a system lock and now I need to:
- tag them
- sync the tagged items to Jira
- write the jira url into a field in the jama item
- unlocking the system lock manually, which is tedious given the current lock management UI and lack of method to re-system-lock the items easily afterwards
- move the items back to draft, perform the sync, and then move them back to approved
These are actions that are common to perform post-approval that are very tedious to get right with system locking and workflows.
Jonah Caplan
QNX
QNX
0
Comments
-
Hi Jonah, I agree that it should be made possible to leave unlocked the custom fields used for categorization, assignment or prioritization.0
-
+1 for this, it would be very useful
Similar to the read-only field it could also be helpful to have an option for fields that are system locked in the UI, but still writable through the API0 -
Hi, I found an older request on same topic => +3:0
-
+1Alessandro
Systems Engineer
SICK AG0 -
+1 from us also0