Unable to create multiple actions with Make Read only for different fields based on user group

In Azure Boards, when working with the “Make Read Only” action, you can only set one field per action within a rule. If you want to make multiple fields read-only for the same condition (e.g., “Current user is not a member of the group”), you don’t necessarily have to create entirely separate rules for each field. Instead, you can:

Edit the existing rule and add multiple “Make Read Only” actions within the same rule — one per field.

If the UI doesn’t allow adding another action directly, try duplicating the action and changing the field, or use the “Add action” button multiple times within that rule.

Make sure the rule order and scope are correct so there’s no conflict with other permission settings.

This approach keeps the configuration clean and avoids unnecessary duplication of conditions. I actually came across a detailed guide on Azure Boards rules while browsinghttps://universalmagzines.com/, which explained the multi-action setup quite clearly — might be worth checking for additional examples.

May consider below workarounds:

1. Go to Project Settings > Work Item Types.
2. Select the work item type (e.g., User Story, Bug).
3. Click Rules.
4. Create your rule with the condition:
   Current user is not a member of [Your Group].
5. Add one “Make read-only” action for a field.
6. Save the rule.
7. Now click Export Process (if using Inherited Process) or use Azure DevOps REST API to retrieve the rule definition.
8. Edit the JSON to include multiple fields under the actions array:

"actions": [
  {
    "actionType": "MakeReadOnly",
    "targetField": "Field1"
  },
  {
    "actionType": "MakeReadOnly",
    "targetField": "Field2"
  }
]

9. Re-import or update the process using the API or admin portal.