Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-9743

Not able to link more than 20 assets in a single Asset type field during the Edit operation

      Summary

      Not able to link more than 20 assets in a single Asset type field during the Edit operation

      Steps to Reproduce

      1. Create an issue
      2. Edit the issue and add try to add more than 20 assets to the "linked assets" field

      Expected Results

      Able to link more than 20 assets

      Actual Results

      When you try to link the 21st asset, the following error is reported

      Notes

      On the Issue create action, you can add more than 20 assets to a single asset field

      Workaround

      Link the assets on the Create issue screen

            [JSDCLOUD-9743] Not able to link more than 20 assets in a single Asset type field during the Edit operation

            frenchie added a comment -

            Thanks 3f7da8170c58 and sorry for the confusion. This ticket is related to the External Assets platform, which is due to shut down by the end of the year. If you want to follow the ticket related to the Assets/Insights native functionality, you can find it here: https://jira.atlassian.com/browse/JSDCLOUD-11828 . We are not deprecating Assets native.

            James

            frenchie added a comment - Thanks 3f7da8170c58 and sorry for the confusion. This ticket is related to the External Assets platform, which is due to shut down by the end of the year. If you want to follow the ticket related to the Assets/Insights native functionality, you can find it here: https://jira.atlassian.com/browse/JSDCLOUD-11828 . We are not deprecating Assets native. James

            R. Boswell added a comment -

            How does this have to do with the External Assets depreciation? This is an issue with Assets integration to Jira. Are you saying that Atlassian is also deprecating the Assets backend or the integration between the JSM and Assets?

            R. Boswell added a comment - How does this have to do with the External Assets depreciation? This is an issue with Assets integration to Jira. Are you saying that Atlassian is also deprecating the Assets backend or the integration between the JSM and Assets?

            Aline added a comment -

            The External Assets platform has been deprecated and will be shut down towards the end of 2024. As a result we unfortunately no longer prioritise non-critical bugs https://community.developer.atlassian.com/t/deprecation-notice-deprecation-of-the-external-asset-platform/73873

            Aline added a comment - The External Assets platform has been deprecated and will be shut down towards the end of 2024. As a result we unfortunately no longer prioritise non-critical bugs  https://community.developer.atlassian.com/t/deprecation-notice-deprecation-of-the-external-asset-platform/73873

            This is a TEST ENVRIONMENT THAT IS NOT INPRODUCTION THERE SHOULD BE NO TICKETS... Please provide a contact number.  I need to understand how you are accessing our tools that are for testing

            jeremiah.hyman added a comment - This is a TEST ENVRIONMENT THAT IS NOT INPRODUCTION THERE SHOULD BE NO TICKETS... Please provide a contact number.  I need to understand how you are accessing our tools that are for testing

            Any updates on this? We have been waiting years for this functionality to be implemented. 

            Nick Huizinga added a comment - Any updates on this? We have been waiting years for this functionality to be implemented. 

            We had a few automations fail again recently due to this limit of 20 objects - any updates please?

            Jennifer Luo added a comment - We had a few automations fail again recently due to this limit of 20 objects - any updates please?

            R. Boswell added a comment -

            Are there any updates on this bug? This is preventing us from fully integrating our CMDB into our ITSM process.

            R. Boswell added a comment - Are there any updates on this bug? This is preventing us from fully integrating our CMDB into our ITSM process.

              Unassigned Unassigned
              skahol Swati Kahol
              Affected customers:
              10 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: