Forums

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

How to copy information from a drop-down list field to another asset field

Kevin Vancrutsen
Contributor
January 7, 2026

Hello,


In a space with approximately 1,500 tickets, I have a ‘Buildings’ field that is a drop-down list. I want to copy the content to another field called ‘Buildings V2’, which is an asset field based on an object schema whose main attribute is ‘Name’. I tried to create an automation rule but couldn't figure it out. Do you have any easy ideas?

Thank you in advance for your help.

1 answer

0 votes
Marc -Devoteam-
Community Champion
January 7, 2026

Hi @Kevin Vancrutsen 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

I assume you have now objects in assets that represent a building.

So in your automation you need to have all work items with an option from the original custom field then branch on every each found issue and set the new asset custom field to the relevant object in assets.

smart value for the asset custom field: key = <key of the relevant building object>

Kevin Vancrutsen
Contributor
January 7, 2026

Hey Marc,

Thanks for reply, here are the anwsers : 

1. Service management project
2-3-4. here all screenshot form rules, field view and asset view (sorry UI in french)field 1.pngasset.pngstep 5.pngstep 4.pngstep 3.pngstep 2.pngstep 1.png

5. i don't know what's the matter

Hope you will help me 

Marc -Devoteam-
Community Champion
January 8, 2026

Hi @Kevin Vancrutsen 

Your rule trigger should be based on a manual or scheduled trigger.

Then do a lookup of issues where field department is option A

Ten branch over the found issues and within the branch do an edit action where the field Department V2 is set key = <key of the related object from assets>

Repeat these actions in the rule, or replace them with new values after the rule has run.

You can't find all issues at once and do an action to replace multiple issues with a singel value in field to copy this to a similar value from an asset object.

Kevin Vancrutsen
Contributor
January 9, 2026

Hello @Marc -Devoteam- 

Thank you for your reply, but I don't understand it. Could you explain it another way, please?

Marc -Devoteam-
Community Champion
January 11, 2026

Hoi @Kevin Vancrutsen 

Create your rule as follows:

  1. Trigger: Manual or Scheduled 
  2. Action: Lookup Work Items (Issues)
    use JQL where issues have a single value of the field Department
  3. Advanced Branch, use smart values {{lookupIssues}}
  4. Action (in the branch): Edit work Items
    Choose field Department V2, from dropdown and set this field to Key = <key object id>,

    example: Key = CD-17353
  5. Repeat the actions 2 tile 4 for each value from the field "Department"

You can to this in the same rule or create separate ones.

Kevin Vancrutsen
Contributor
January 12, 2026

hi @Marc -Devoteam- 

Thanks for the reply, i made a new rule and here are the screenshot : 
rule 1.pngrule 2.pngrule 3.png
rule 4.pngUnfortunately, it doesn't work, i try on a issue DI-1513

Capture d'écran 2026-01-12 112221.png

So the data in "Bâtiment" are not copy ine the new field "Bâtiments V2"

Thanks in advance for help

Marc -Devoteam-
Community Champion
January 12, 2026

Hi @Kevin Vancrutsen 

For that issue, what is the current value of the field Batiment?

Kevin Vancrutsen
Contributor
January 12, 2026

@Marc -Devoteam- for this issue, it's "Pentagone" but i have a list of 60 different value, may i need to do each one ?

Marc -Devoteam-
Community Champion
January 12, 2026

Hi @Kevin Vancrutsen 

Yes, you do have to do this one by one, as each option of the field is a separate object with a key in assets.

Or we need to change the rule.

In the branch create a variable.

name: batiment, smart value issue.batiment.name}}

Then add a lookupobjects action to find objecttpe = batiment and name = {{name of created variable}}

Then do an edit action where field Batiment V2 is set with smart value {{lookupObjects.key}}

 

Please adjust the naming to the correct ones on your instance.

Suggest an answer

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

Atlassian Community Events