We have jira asset custom field which can take multiple asset objects.
We are programmatically able to create a ticket with more than 1000 assets objects (2000+) on this custom field.
When the ticket now with a large number of asset objects on this custom fields is edited,
On the edit panel this custom field shows empty assets.
So on save all the data is lost from this custom field.
The only way we are able to update details on the ticket with large number of asset objects is via a bulk edit option.
Is there a solution for this?. we want the edit panel also to load all the items which were there, so that the save does not empty this custom field.
Hello @Diwakar Murthy ,
Wow, that's a huge load. I liked!
I can't reproduce the behavior mentioned because I don't have such a large asset base under approval, but I try to use a variable in automation that stores its value before editing the field.
Then, when editing the field, use the {{field}} variable along with the new values.
I don't know if it's possible, but in tests with fewer assets it worked!
Please let me know if this solution helped you!
Hello @Luiz Ricardo Pereira da Silva , yes with fewer assets on this custom field it works fine.
But its the problem when we have large numbers of them like 2000+
And we have this on dev panel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.