Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Extracting content out of the description with automation not working in Jira Product Discovery

Karen Crawshaw
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 11, 2025

I am trying to configure automation rules to extract text from the Description of Jira Product Discovery ideas into custom fields; however, I get an error stating the set fields aren't available. 

Steps I took to create the rule: 

  1. Within my PD project I created a new field called 'Expected Benefits' 
  2. I created a template for new ideas which included the word 'Benefits:' 
  3. Created an automation: 
    1. When: Work item Created
    2. Then: Edit work item fields: 
      1. Expected Benefits: {{issue.description.match(".*Benefits: (\\S+).*")}}
  4. I've validated the rule and there are no errors 
  5. I created a new idea, completing the template 
  6. Go to the automation audit log and get the following error: 
    Edited work item successfully, however some of the set fields aren't available. Fields ignored:
    Expected Benefits (customfield_10419)

What am I doing wrong?

Thanks 

 

1 answer

2 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 11, 2025

Hi @Karen Crawshaw -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

  • an image of your complete automation rule in a single image for continuity
  • images of any relevant actions / conditions / branches
  • an image of the audit log details showing the rule execution, with the sections at the right side all expanded
  • explain what is not working as expected and why you believe that to be the case

Until we see those...

 

The Work Item Created trigger can have timing problems where the rule starts before the data is fully available.  This can cause unexpected behavior and strange rule errors.  The mitigation for that defect is to always add the Re-fetch Work Item Data action immediately after this specific trigger.  That will slow the rule a bit, reloading the data before it proceeds.

 

Kind regards,
Bill

Karen Crawshaw
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 12, 2025

Thanks for the reply Bill. 

I have PD board setup with a custom field for 'Expected Benefits': 1.jpg

When creating new ideas on the project my Description section has a template that includes the word 'Benefits': 2.jpg I have created an automation that I hoped would extract the text written next to Benefits in the description and populate the custom field: 3.jpg

When I create a new idea the rule runs but with the following error, and the custom field remains blank: 4.jpg

I've just tried adding the re-fetch work item data to the end of the rule, but it still doesn't populate the custom field. 

Many thanks for your help.

 

Like Susan Waldrip likes this
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 12, 2025

The Re-fetch should be immediately after the trigger, not at the end of the rule:

  • trigger: Work Item Created
  • action: Re-fetch Work Item Data
  • action: Edit Work Item...

Putting it there helps solve the problem of the work item being in an unstable state when the rule starts.

 

After we solve this error, we can examine your extraction of the data from the Description field (if you are seeing unexpected results).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events