• 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue summary
      Custom fields of type Insight(Assets) objects do not have the pin option available in views.

      Steps to replicate

      1. Open a ticket in a JSM project that has a custom field of type Insight(Assets) objects
      2. Hover over the field name

      Expected result

      • Pin symbol is available to allow the user to pin the field.

      Actual result

      • Pin symbol is not available

      Workaround
      Currently, there is no known workaround for this behaviour. A workaround will be added here when available

            [JSDCLOUD-11729] Ability to pin custom fields of type Insight(Assets) objects to views

            https://community.developer.atlassian.com/t/shutdown-notice-update-on-deprecation-of-the-external-assets-platform/81193

             

            So, to recap, you're decommissioning the External Assets Platform, which allows pinning, forcing everyone to use your built in Asset platform, when said platform doesn't even allow you to pin it for easy access? 

            David Drosdick added a comment - https://community.developer.atlassian.com/t/shutdown-notice-update-on-deprecation-of-the-external-assets-platform/81193   So, to recap, you're decommissioning the External Assets Platform, which allows pinning, forcing everyone to use your built in Asset platform, when said platform doesn't even allow you to pin it for easy access? 

            Josh added a comment -

            We've been having focus group discussions with our JSM end users and the lack of ability to pin asset-based fields was a common theme. It would be really helpful to not have this limitation...

            Josh added a comment - We've been having focus group discussions with our JSM end users and the lack of ability to pin asset-based fields was a common theme. It would be really helpful to not have this limitation...

            Chris Kite added a comment -

            We heavily utilize Assets fields, so this would be very useful (plus, it's just good for the sake of consistency and not having to explain to users why some fields can be pinned and others can't).

            Also for reference, this does not just apply to JSM type projects. Assets fields can't be pinned in any projects.

            Chris Kite added a comment - We heavily utilize Assets fields, so this would be very useful (plus, it's just good for the sake of consistency and not having to explain to users why some fields can be pinned and others can't). Also for reference, this does not just apply to JSM type projects. Assets fields can't be pinned in any projects.

            I also would value this feature, it would make for more consistent behavior which is to be expected by such a well polished piece of software.

            Eric Haskett added a comment - I also would value this feature, it would make for more consistent behavior which is to be expected by such a well polished piece of software.

            For clients using Assets, often custom fields of this type are extremely relevant and need to be pinned!

            Iorio Cristian added a comment - For clients using Assets, often custom fields of this type are extremely relevant and need to be pinned!

            LAURENT added a comment -

            +1 !

            LAURENT added a comment - +1 !

            +1

            Tiago Pereira added a comment - +1

            Please, my team needs this functionality. 

            Tassia Tanaka added a comment - Please, my team needs this functionality. 

            Josh added a comment -

            Please provide pinning capability for asset objects. They should be given the same functionality as any other type of Jira field.

            Josh added a comment - Please provide pinning capability for asset objects. They should be given the same functionality as any other type of Jira field.

              Unassigned Unassigned
              c72c7cdc98e4 Aparna
              Votes:
              50 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: