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

Setting a multi-select field based on the parent Jira Project on ticket creation

Kit Friend_pvmg27

Hello hive mind!

I've got 0 JSON skills and suspect this is part of what's blocking me ...

We'd like to do the following:

1. New ticket is created

2. Populate a multi-select custom field with a value matching the project (e.g. if the issue is created in a project called NET, select NET from the field, if the project is DIGI, select DIGI etc)

Currently I'm struggling to work out:

1. How can we read which project the ticket is part of so that we can define this to be the value that's copied down (it doesn't appear to be a default field we can copy a value from)

2. How can I populate the target multi-select field - it doesn't appear to be available. I've found some community posts that indicate the fix is to use the More Options JSON but I can't find any training for coding novices on what to actually put in it.

Screenshot 2020-09-22 at 19.28.13.png

Accepted answers

All comments

Sherry Goyal

Hello @Kit Friend

Thanks for writing to us.

I would suggest you to use if/else condition block along with "Issue fields condition".

Trigger: Issue Created

Condition/Action: if -> project equals NET then -> edit issue(choose custom field from drop down ) and for value, select appropriate value from dropdown out of all the multi-select options you have.

else if -> project equals DIGI then -> edit issue(choose custom field from drop down) and select value from dropdown out of all the multi-select options you have.

No need to use advanced json part.

Something like this:

Screen Shot 2020-09-23 at 10.44.55 am.png

Hope this helps you.

Cheers
Sherry

Kit Friend_pvmg27

Hey Sherry - I agree but we wanted to try and avoid having 11 nested IF/else equations and do something a bit more dynamic :P

Is there a tutorial on how to use the JSON option?

Sherry Goyal

Hello @Kit Friend

Yes you can achieve this using JSON, something like this:


"update": {
  "your_custom_multiselect_field_name": [
    {
     "set": [{"value": "{{issue.project.key}}"}]
    }
  ]
 }
}

For more details and usage with examples, you can refer here.

Thanks
Sherry

Kit Friend_pvmg27

Hey Sherry,

Almost there I think. I thought this would work:

{
"update": {
"customfield_10054": [{
"set": [{
"{{project.key}}": "{{issue.project.key}}"
}]
}]
}
}

and I can successfully write in the Project Key as a label using a similar technique. But when trying to use it to set the content of customfield_10054 I get:

Error editing issues DEMO-42 (Field 'customfield_10054' cannot appear in both 'fields' and 'update')

Thoughts?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation