Loop over asset objects and update them using Jira Automation
Hi,
I have asset objects created as below :
Name Assigned
A 0
B 0
C 0
I want to loop over all the above asset objects and update the assigned value to 1 based on the issues assigned to the team members i.e. If team member A is assigned an issue it should update the assigned value to 1.
typically, updating an asset object can be done using AQL branching and thats what i tried in the below automation:
In the above automation i am looping through my asset object "Cummins Deployment Team" and then querying the team members name using lookup issues and accessing the team members name as {{Object.User}}. However, {{Object.User}} returns all the users rather than the first one and hence the query also doesn't return anything. How can i ensure that I can loop through the objects one by one and query them with lookup issues?
Please let me know if there is any workaround for the same.
2 answers
2 accepted
Attached is the log output for the above rule:
(Please ignore the delay statements I have just put it to try something)
let me explain in brief on what i am doing:
1.) Return multiple Asset objects using the advance branching AQL statement.
2.) Loop through each object one by one. Ideally in the first iteration object should return only first object and will access the attribute user of that using {{Object.User}} statement. However, as per the above log it is returning all the objects.
3.) Lookup issues using a JQL query with the {{Object.User}} as argument. however, as per above log it doesn't return any issues as all the users are returned.
4.) Edit the asset object attribute "Assigned" and add the value as Number of issues found from JQL query i.e. {{lookupissues.size|0}} value.
I think the main problem is all the users are returned when i use {{Object.User}} inside the loop. Not sure how to access the object one by one inside the loop?
as suggested i constructed the query into a variable and added in the log. looks like the query was correct. However, i was using the property {{lookupissues.Size}}, which was incorrect as it was case-sensitive.
when i changed it to {{lookupIssues.size}} it took the correct values and updated them in Assets. Thanks for your suggestion !!
However, one strange thing is there in the above log that it still showing that lookupissues did not find any issues. but when we access the number of issues using {{lookupIssues.size}} it is getting the correct number.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.