Jira Automation 'Team' field question

[Saurabh Chaudhary]

Hello there,

I have written a Jira Automation which is doing well for all fields except one, which is the 'Team' field (which we got when we upgraded to Jira Premium).

As this field is not directly available in the fields for Automation related action. I used the 'Additional fields' section to populate the Team that is allocated to the Parent issue (Initiative which is defined as parent to Epics) to the Child Issue (Epic Level) which this automaton is creating successfully.

It works for all other fields but Team. I have tried the Custom Field ID for Team as well but I get the error 'invalid Jason'. Can anyone please help what is the correct JSON here???

[Mohammed Aamer Khan]

Hi @Saurabh Chaudhary

Try below code once

{
  "fields": {
    "team": "{{issue.epic.team.id}}"
  }
}

You can find more information on another similar question asked on community Click Here 

I Hope it resolves your query

[Saurabh Chaudhary]

Hi @Mohammed Aamer Khan , the child ticket being created is at Epic level. It is the child of the Initiative level that we have defined in the hierarchy through Jira Premium.

So the one you shared above worked but did not populated the Team field.

[Mohammed Aamer Khan]

@Saurabh Chaudhary

Try using Branching Option and use trigger issue code in edit issue in branch action item.

In Branching you can select JQL and filter the required result. If You can share your Automation I will be able to guide you more on it.

[Saurabh Chaudhary]

Below is my automation which is working fine. The bit not executing is what I have shared above

[Bill Sheboy]

Hi @Saurabh Chaudhary 

Adding on to Mohammed's answer...

You note the "bit not executing" is what you have shared, but the rule you show does not attempt to set the Team field.  Have you posted the correct image?

Next, there are unfortunately several fields in Jira Cloud named "Team" and many of the fields related to Advanced Roadmaps/Timelines are not supported by automation rules.  I encourage you to use this how-to article to confirm your field is supported by automation rules before proceeding.

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

Essentially you identify an issue containing your field, call a REST API function with a browser tab, and then search for your field.  If you find it, the field is supported and you can learn the correct smart value or custom field id to use.  If the field is not listed, automation rules do not support it.

Kind regards,
Bill

[Saurabh Chaudhary]

Hi @Bill Sheboy Resharing the images I had shared above that were not executing. I had found the custom field ID and tried using that as well.

[Mohammed Aamer Khan]

Hi @Saurabh Chaudhary

I created an automation and tested above JSON. I can see it is working as expected. PFA

Please check once again and let me know if it is displaying any specific error.

Thanks