Jira service management and automation of sub tasks aren't working, fields or permission issue?

Gil Erez

I've been trying to build automation that when a service request comes in, tasks are created depending on the type of service request and some data within. My problem is:

1) Even transitioning the created service request doesnt work (No transitions were performed by this user.)  - error

 

2) Sub-tasks are created and linked properly, but cant have assignee and due date defined upon creation, nor can they be edited after creation automatically

(Edited work item successfully, however some of the set fields aren''t available. Fields ignored: {0}

Assignee (assignee), Due date (duedate)

No fields or field values to edit for work items (could be due to some field values not existing in a given project) - error

 

Ive manually given automation for JIRA permissions needed for the space, and the subtask scheme, screen, etc.. are all the same that I use for other regular JIRA spaces (all company managed). I'm on cloud version. 

 

Anthony Morais

Hi @Gil Erez 

Regarding the errors below, have you already tried the following?

- Transition error (“No transitions were performed by this user”)
That usually happens because the current status doesn’t have a valid outgoing transition for the automation user.
Try opening your workflow and, for the destination status, check the box:

Allow all statuses to transition to this one

This ensures the automation can perform the transition regardless of the issue’s current status.
Alternatively, verify that the automation actor has permission to execute that specific transition (no validator or condition blocking it).

- Sub-tasks: assignee / due date not being set
For this one, confirm that:

Both fields (Assignee and Due date) are included in the Create and Edit screens of the sub-task issue type.

The fields are also present in the Field Configuration and Field Context for that issue type and project.
If they’re missing in the screen or restricted by context, automation will skip them with a message like “Fields ignored”.

- Same principle for any other ignored fields
Yes — the same checks apply.
Whenever automation reports “some of the set fields aren’t available”, it almost always means the field isn’t on the screen, isn’t available in the field context for that issue type, or is being edited before the issue is fully created.
If that’s the case, you can add a short “Re-fetch issue data” action before editing fields.

Hope this help.