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; } } }

Unable to retrieve initiative key value from Parent using custom field

hshivanna

Hello Experts,

I am trying to set sub-task ''Initiative Key'' from its parent by using below JSON automation. But I am receiving error '(Operation value must be a string (customfield_21602))'. Could anyone please help me on this.

Below is the JSON query used in automation rule:

{

"fields": {

"customfield_21602": { "value": "{{triggerissue.parent.customfield_21602.value.asJsonString}}" }

}

Accepted answers

All comments

Trudy P Claspill

Hello @hshivanna

Welcome to the Atlassian community.

What is the field type of customfield_21602?

I see that you are trying to set this field from data in the same field in another issue. In JSON you should be able to use this rather than "value":

"customfield_21602" : "{{triggerIssue.parent.customfield_21602}}"

Have you tried that?

Are you trying to use this JSON code in an Edit Issue action? If so, are you not able to select the field you want to edit from the Choose fields to set list? If you can, then you should be able to use the COPY option to then copy data from the same field in the issue's parent.

Screenshot 2024-11-06 at 8.55.56 AM.png Screenshot 2024-11-06 at 8.56.08 AM.png

hshivanna

Hello Trudy,

Thank You for the reply.

When i tried with first option, i see below error

(No issue with the key: {id=********, key=***********, , name=Initiative, subtask=false, avatarId=12606}}} (customfield_21602))

I would like to pass key=*********** as the Initiative key value.

I dont have initiative key available in edit field dropdown. Hence trying with advanced field option.

***********

Trudy P Claspill

Thank you for that additional information.

What is the field type of customfield_21602?

Can you provide screen images that show your entire rule? Sometime errors occur due to the context of the step within the rule.

Can you show us a screen image of all the output of the rule execution log, including the section on the right where it shows the issue keys for issues referenced during the rule execution?

Are you able to access issue AHPCOM-5395 directly?

What is the Project Scope of the rule, from the Rule Details page? Who is specified as the Actor for the rule?

You are trying to access information from the issue that triggered the rule. What type of issue triggered the rule? Was it a subtask, or a standard level issue that has a parent Epic?

Can you show us a screen image of the issue that triggered this rule, showing us the value in customfield_21602 and showing us the breadcrumbs at the top of the issue that show the issue key and the issue key of its parent.

hshivanna

Hello Trudy,

Thank You!Please find the answers inline:

What is the field type of customfield_21602? This is something i am unable to figure out from JIRA

Can you provide screen images that show your entire rule? Sometime errors occur due to the context of the step within the rule. I have attached Automation Rule Screenshot

Can you show us a screen image of all the output of the rule execution log, including the section on the right where it shows the issue keys for issues referenced during the rule execution? I have attached audit log screenshot

Are you able to access issue AHPCOM-5395 directly? - Yes, I can

What is the Project Scope of the rule, from the Rule Details page? Who is specified as the Actor for the rule? - To have Intiative KEY added to Sub-task

You are trying to access information from the issue that triggered the rule. What type of issue triggered the rule? Was it a subtask, or a standard level issue that has a parent Epic? - It is a sub task

Bill Sheboy

Hi @hshivanna -- Welcome to the Atlassian Community!

When a rule references smart values through the associated issues, such as with {{issue.parent.customfield_12345}} or {{issue.subtasks.customfield_12345}} most of the data is not loaded. Instead, only a subset of the fields are available, such as: key, summary, assignee, status, etc.

If the associated issues loaded all of their data, you could imagine a scenario where an entire tree of issues would be pulled in, ever increasing in number / size. Worse still, there could be cross-linkages leading to loops.

When you need to access the other fields in the parent or subtasks, please use either branching or the Lookup Issues action with JQL to fully load all of the fields for the issue.

And for Jira Data Center, Lookup Issues will only load some fields, not including custom fields. The workaround for that situation is to use branching or use the Send Web Request action to load the data with the REST API issue search with JQL.

Kind regards,
Bill

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-cloud