{{objectType.size}} Output Limited to 100??

David Hart
Contributor
November 13, 2024

When I use the smart value {{objectType.size}} it only displays 100 when I clearly have more objects than that. Is this a jira limitation??

3 answers

1 accepted

4 votes
Answer accepted
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 13, 2024

It is a limitation in automations, yes. Any lookup function in automation will only return the first 100 results it get back. The workaround would be to use a web request and the Post object AQL to get more than 100 objects. 

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 13, 2024

And if you are looking for the count you can use Post object aql totalcount.

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2024

Hi @David Hart 

Can you show your automation?

But I also seem to remember that smart values only get the first 100 options.

@Bill Sheboy can you confirm this?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2024

Hi @Marc - Devoteam 

As others have noted: yes, that is the limit.  The rule engine uses the REST API endpoints and those mostly have a 100 record limit.

Kind regards,
Bill

0 votes
Hans Polder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 13, 2024

@David Hart ,

As per the Automation service limits I would expect this to be a limitation of the lookupObjects action. It's not specifically defined here, but for its 'brother' lookupIssues, the limit of 100 issues is mentioned here.

Other than getting the number of objects, what are you trying to accomplish? Maybe there is another way if the context is clear :)

David Hart
Contributor
November 13, 2024

Unfortunately, just the number of objects. My goal is display our software assets (schema B) in a confluence page and in a separate schema (schema A) we track each software and how many employees have an account. So I setup automation, when a new object is created in schema A, schema B updates with the number of objects in a certain objectType in schema A. So our confluence page does not have to be manually updated every time we add a new account in schema A.

USE CASE: When someone views the confluence page they see the software description, the vendor, security policies, who is the admin etc. (data from schema B) and number of users (data from schema A brought into schema B via automation)

I sure hope this makes sense lol

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