Automatizacion de campo personalizado - Custom field automation

[Maximiliano Rojas]

Estimada comunidad,

Tengo la necesidad de resolver una automatización, la idea es que cuando se crea una EPICA, se automatice un campo personalizado y baje hacia la HISTORIA. Este campo esta completo en la EPICA y necesito que se autocomplete en la HISTORIA.

¿Es esto posible?

dejo la estructura:

Dear community,

I need to resolve an automation issue. The idea is that when an EPIC is created, a custom field is automated and transferred down to the STORY. This field is filled in the EPIC, and I need it to be auto-filled in the STORY.

Is this possible?

Here’s the structure:

[Dick]

Hi @Maximiliano Rojas 

I think you have a couple of problems here:

1. JSON: the use of both the update and set keywords 
2. JSON: the use of child expects an issuekey, not a customfield value
3. Smart values within the curly braces:
   I don't think that navigating to the child can take place after navigating to a customfield of the parent: {{triggerIssue.fields.customfield_10099.child.value}}
   
   try: {{triggerIssue.child.fields.customfield_10099.value}}

[Maximiliano Rojas]

Thanks for the answer Dick, It would look like this:

{
"update": {
"customfield_10099": [
{
"set": {
"value": "{{triggerIssue.fields.customfield_10099.value}}",
"child": {
"value": "{{triggerIssue.child.fields.customfield_10099.value}}"
}
}
}
]
}

[Dick]

Hi Maximiliano,

Please study Atlassian on advanced-field-editing-using-json/ 

Set is used only for filling in multicheckboxes. 

A custom field is filled with a value in quite a different way.

Hope this helps you

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Dick]

Hi @Maximiliano Rojas 

Any progress to share with us?

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)

[Maximiliano Rojas]

Hi Dick, i try to go for a more simple way,but in response of that, i have this:

[Maximiliano Rojas]

Im asking jira to copy the information of the custom field, wish is complete in the parent, to the history, whit the same field but empty. I cant do it yet.

[Maximiliano Rojas]

{
"update": {
"customfield_10099": [
{
"set": {
"value": "{{triggerIssue.fields.customfield_10099.value}}",
"child": {
"value": "{{triggerIssue.fields.customfield_10099.child.value}}"
}
}
}
]
}

[Maximiliano Rojas]

@Dick 

I can finaly can replicate the custom fiel, but this field has a cascading select whit 1 level that dont replicate. Do you know how to do it?

[Dick]

@Maximiliano Rojas 

you can always list contents of multiselect fields using the automation "Add value to audit Log" step. This way you can study what is inside a regular issue, and what should be inside your code to match the things you would like to change. 

With this in mind, adorn your automation with these steps in key places (like right before you want to edit the field. A copy of the logs and errors you encounter would be a great way to move forward in solving your question.

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)