nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error retrieving the work type fields for project/typeId -

Daniel Gavrila_xhc5hh

Hi,

I am embarrassed to ask again for help, but my automation to create a ticket in Jira Software based on the transition of a Jira Service Management ticket is not working anymore, failing with the error in the title and below: Screenshot 2025-07-17 at 20.36.13.png

This is the automation:
Screenshot 2025-07-17 at 20.37.16.png

Issue type ID 10011 must be Bug, as above, and project ID 10004 must be RBR.

The rule is set to be global when I checked it today it was set to a single project, the trigger one. There is no mention in the audit logs of anyone else changing the scope, but I am positive I left it as global because I talked about it on a previous request for help here and I even have a screenshot. Anyway, here are the current rule details:

Screenshot 2025-07-17 at 20.37.30.png

What is weirder is that I have another automation almost identical, triggering the creation of a ticket to a different project, that is also set to a single project and it works.

Thank you very much

Accepted answers

Trudy P Claspill

Hello @Daniel Gavrila

What type of project is RBR? Get that information from the View All Projects page under the Projects menu.

Can you manually still create a Bug type issue in the RBR project?

Have you confirmed that 10011 is the ID associated to the Bug issue type in the RBR project? There may still be a Bug issue type in the RBR project, but it may now have a different back end ID than it had previously.

All comments

Trudy P Claspill

Hello @Daniel Gavrila

What type of project is RBR? Get that information from the View All Projects page under the Projects menu.

Can you manually still create a Bug type issue in the RBR project?

Daniel Gavrila_xhc5hh

Hi, @Trudy P Claspill , nice to hear from you again!
RBR is a company-managed software. And yes, I can create a bug type issue manually from the project.
I have confirmed that 10011 is the id associated with this type, indeed.

Trudy P Claspill

Thanks for double checking those elements.

Another thing to check is the permissions of the Rule Actor within the RBR project. Automation for Jira (the actor) gets its permissions through the group atlassian-addons-project-access. Is that group assigned to all the permissions in the RBR project?

You may also want to review the fields you are setting in the Create action to make sure all those fields are still available in the RBR Bug issue type.

Also review the smart values you are using. I noticed this one has a comma in it. Is that one field name that includes a comma? Smart values can be sensitive when using field names. If that is one field name that includes a comma you may want to change it to use the "customfield_#####" nomenclature instead.

Daniel Gavrila_xhc5hh

Thanks for getting back!
Automation for Jira has the permission to create issues in RBR, it was one of the things I checked last times and I double checked again today.
I have reviewed some of the changes, and I also have doubts about the one with the coma. That's its name, but I will resort to the "customfield_##" like I did for components. I am a bit in the dark about finding those ids, but like I found the one for components, I trust I will find the ID for this one too.
But this still leaves that error.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management