+1

+1

+1

+1, waiting for this 

+1 with the addition of Asset Data Manager later this year we will have an ever increasing need for this limit to be removed.

+1 super limiting for our clients and customers

+1 Really need this ability please!

90325da67d46 Just wondering if there has been any progress on this?

Hi Team 👋,

First off, I want to apologise for the lack of updates on this feature request. We appreciate your engagement and understand how important this is to you.

As you might have seen on other forums, we’ve been making significant investments in upgrading our platform to improve reliability and performance. This work is critical to laying a strong foundation for future development and ensuring a smoother experience for all users.

Once these upgrades are fully released and stable, we’ll be in a much better position to revisit the roadmap and start addressing feature requests like this one.

We still absolutely want to address this issue and acknowledge the frustration it may be causing. Thank you for your patience and understanding as we work through these priorities. Your continued feedback is invaluable, and we’re committed to keeping you updated on our progress.

Thank you,
Mohamed Hassan | Product Manager, JSM Assets

This has become increasingly important to our business needs as we've grown and started using Jira Service Management for our field technicians.

We need the ability to link more than 20 assets to a ticket, especially for installation on equipment involving 100+ assets at a single customer. Currently, we've had to develop our own workaround, which is not ideal because the process differs between issue tickets with a single asset and project tickets with over 100 assets. This creates a cumbersome and inefficient workflow for our internal processes. 

Hi,

We need to add more than 20 objects in Assets field in Cloud. Indeed, we are currently migrating customer from DC to cloud that have several fields with more than 20 objects.

What are the workarounds ?

Integrating JSM and assets to mange ITIL processes of change and incident management etc this stops our ability to have a Parent service with x number of child services underneath and impacted when there is a change or incident at the parent level. Debilitating!

Atlassian any news about this limitation?
There have been no updates since 2022, we have several customers who are extremely dissatisfied with this limitation.

This is a seriously disabling limit for our logistical people

This limitation is really blocking and makes work difficult

+1

It's super necessary for us and we're facing a lot of difficulties because of this limitation

A really common use case... Vulnerability patching 50 + Windows servers. Would be great to link all those servers to a change record right? Well you're out of luck...

We're trying to use Assets for multiple workarounds / enhancements and the 20 object limit is making this unviable for those purposes too.

We use that for incidents and system accesses. This limitation affect our processes. For us, it is good to have limitation on 100 objects.

Please, we need that functionality. My team of 25 people will say thank you.

Hello everyone!

Thanks very much for your input on this suggestion. One of our big focuses for Insight is increasing scalability. For the most part we are focusing on increasing the number of objects we support as well as allowing larger imports. However, increasing the the number of objects supported by the Insight field could also form part of that focus and we are looking into how and when we could do that. 

I'll provide further updates as this progresses.

All the best,

Justin King
Product Manager, Jira Service Management

Hi Justin, 

I think that many IT organisations implementing a cmdb will have the need here and then to relate more than 20 objects on a field. 
This is often  because due to system dependencies when a core component  might be failing for example, causing multiple instances to be affected. 

On our daily operations we often need to relate more than 20 objects to a specific Jira field. 

Hi Justin!

For us we use tickets for incidents where we select connectors to banks that are affected, and sometimes A LOT of banks can be affected for us depending on the issue. I would guess 100 would be a good start, but 150-200 or more the merrier!

Hello! I'm one of the Product Managers for Insight. I was wondering if you some of you who are interested in this feature request could help me understand your use-case that involves adding more than 20 objects to the Insight field? It's not a scenario that we anticipated so we would love to understand the need better. If you could also estimate how many objects you typically see yourself needing to add to the field at once that would be very helpful. Looking forward to hearing from you!

had no idea this limitation existed when i put in several sprints implementing this as our CMDB, now i'm stuck - really need this prioritized and addressed

This is a huge limitation.. I hope you prioritise asap 

Could this issue be evaluated outside of the general workflow? It's been sitting in Gathering Interest limbo status for a long time. Kind of interested to know if this will ever be fixed or we should look elsewhere for a working solution.

Could we expect to have this limit raised at some point or at least make it configurable in Jira? The current limit of 20 objects is really low. Wouldn't want to see this request buried as it seems like a simple modification. The votes system doesn't really work here as it's a rather specific issue that doesn't affect many organizations.

Just wanted to highlight that this is a showstopper for us ever since our system grew and now requires relating more than 20 objects - a limitation we were not aware of nor couldn't we find it anywhere in the documentation. I'm sure others have also ran into this rather restricting limitation but have found workarounds or other ways. We rely heavily on utilizing object references and building queries on top of them. If we can't relate all required objects the queries just won't work. I hope this limit is raised soon otherwise we might need to look for other ways to do CMDB.