• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Assets - Import
    • 0
    • 3
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Tag object type can cause a performance bottleneck because of the way Assets retrieve it - for each object that can have tags, it seems there is a request to aws to retrieve all tags for that object, which can quickly add up for customer with a large number ob objects as well as the possible number of references.

      An improvement would be helpful

            [JSDSERVER-15699] AWS Assets import require significant time for the Tag ObjectType

            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count New: 2
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Marc Dacanay made changes -
            Labels New: ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 978898 ]
            SET Analytics Bot made changes -
            UIS New: 1
            Pablo Bartolome created issue -

              Unassigned Unassigned
              9f03f4114502 Pablo Bartolome
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: