Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Automation thinks field is unavailable for project type

caglad
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 28, 2024

I have a field that I am using in global automation to fill in the value. But error log suggests this field is not available for my project type. However, the issue type shows available for all issue types and available globally for all projects. I am able to use it in an import for project type but automation doesnt like it.storypointserror.jpgstorypointsissuetype.jpg

 

I have to be missing something.. welp

 

2 answers

0 votes
caglad
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 28, 2024

Jira Cloud - 

Here is the rule.. Create issue - from trigger issue - and everything is being created with the correct values except for this. 

rule2.jpgrule1.jpg

omg dont tell me its because I didnt put the brackets in

Julian Governale
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 2, 2024

Since it works from Import i assume it is on your create screen for that project and the task issue type but here are a few aspects to double confirm. 

  1. The field Story points (Est. Hours)  is present on the task issue type create screen
  2. If it's not present
    1. Ensure it's added to the Create screen
    2. Ensure it's not marked as hidden in the field config
  3. Confirm you don't have two fields with the same name in the system
    1. If you do, confirm you have selected the right field in the automation  (customfield_10014)

If all the above is confirmed, try to set the field through the additional field section.  First, remove it from the "Choose fields to set" area to avoid any conflicts. 

{
"fields": {
"customfield_10014": 2
}
}


 

Like Kelly Arrey likes this
0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 28, 2024

Hi @caglad 

Please post an image of your complete rule and the Create Issue action.  These will provide context to compare to the audit log details you show.

And, which version of Jira are you using: Cloud, Server, or Data Center?

 

Until we know that information...

I wonder: does the Create Issue action select the project and issue type explicitly?  If not, that may be causing a problem with the field.

 

Kind regards,
Bill

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 29, 2024

@caglad please try to stay in one thread when responding.  That will help others reading this question in the future know if there are multiple solution approaches.  Thanks!

 

Please post your complete automation rule, in one single image.  That will provide context for where the Create Issue action is happening within the rule.

Which version of Jira are you using: Cloud, Server, or Data Center?

If Jira Cloud, what type of project is this: company-managed, team-managed, etc.?

Is your custom field visible on the views for creating an issue?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events