Error retrieving the work type fields for project/typeId -

[Daniel Gavrila]

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: 

This is the automation:

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:

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

[Trudy P Claspill · Accepted solution]

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.

[Daniel Gavrila]

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]

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.

[Trudy P Claspill]

I did a Google search for 

jira cloud automation "error retrieving the work type fields for"

jira cloud automation "error retrieving the issue fields for"

Permissions for the actor was discussed in a KB for that message. Examining the smart values used was listed in a forum Question where the problem was the user had used two periods:

{{issue..fieldname}}

That is why I suggested examining the smart values you have used. Sometimes the error messages don't tell you what the root cause is, and the root cause ends up being something that does not appear to have any relationship to the message you received.

To get custom field IDs for any field available in an issue refer to this document:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Daniel Gavrila]

Yes, I have also checked that thread and verified my smart values. I couldn't find something, maybe because it's not too obvious. 

Thanks for the tip about the custom field IDs.

[Daniel Gavrila]

Hi, @Trudy P Claspill
Indeed, some of the field names were the problem. I took them out one by one and then replaced them with smart values and it eventually worked. It didn't help that whoever created the fields has duplicated some names, so it took a bit of forensics to get to the right ones. 
Thank you for the support!
P.S.: I got to the field IDs faster by going to Jira Admin Settings/ Fields/- select Context and default values/ the separate tab has the Field ID in its URL. :)

[John Isherwood]

Hi @Trudy P Claspill   , thank you!!!

This smart value issue was the answer to my automation error "Error retrieving the work type fields for project/typeId" too. Thank you for the information!

I had a bulky automation generating 23 scheduled tickets, and it wasn't obvious but I had added too many brackets in the dot notation of the smart values for a few of the fields.

23 issues with different smart values like:

{{now.toDateTimeAtStartOfDay("Europe/London").plusHours(16).plusMinutes(30)}}