Jira asset object status change automation

Karl-Friedrich Lind

Taking a dive on jira assets and how it could apply to my situation. I am trying to create a simple raise a request where the end user can select and asset and select a status and have an automation change the status of the asset object So the request form is simple: Summary, the asset field (displaying the name and the status), and a dropdown field (containing: Active; Inactive)
What confuses me is the automation part
 how do i actually edit the object currently the Lookup object looks at the value in the "Asset Object Status" which can hold only one object and then creates a smartvalue for the status field called {{Statusvalue}} but I can't seem to edit the object keep getting
"This component may be incompatible One of the following needs to be produced earlier in the rule by the trigger or with a 'for each' branch for this component to work: CMDB object"
Tried reading the documentation but I am just getting more confused.

Robert DaSilva_a432as

Hi, @Karl-Friedrich Lind; welcome to the Community!

I want to repeat your use case to make sure I understand.

• You have a list of Assets you are storing inside of JSM Assets
• When users create a ticket, they optionally can select a specific asset, and optionally a new Status for that asset

 

The "Optionally" part I am inferring due to the fields not being marked as required.

 

If so, I think your Automation is nearly there. It would help if you could share the specific configuration of each step, but I'm going to assume things are configured correctly.

 

I believe the following automation structure should work:

1. TRIGGER: This is fine to leave at Issue Created
2. BRANCH RULE: Add the Branch Rule "For AQL"
   1. ACTION: Move the "Lookup Objects" into this new branch. I doubt you actually need this, based on the AQL options inside the branch rule though.
   2. ACTION: Move the "Edit object attributes" under the branch rule. You can also use Smart Values in this section, so you can try removing the Variable if you would like.

 

With those changes, your automation should trigger properly, but I would encourage you to test before deploying to production.

Let me know if that works!

Robert