Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11187

Ability to Persist Value of User Type Attribute (owner of an asset) in Insight

    • 3
    • 5
    • 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.

      When setting an Insight Object's "User Type" Attribute from users, it may not be possible to keep this information persistent. This user type value is filled from the Jira Service Management Users and if the corresponding user is deleted the asset's user information may be lost.
      The only possible workaround to this is making the user a reporter, assignee, or comment author on any issue. This requires every user who was set as the owner of an asset to make changes on the system or to be set as, at least, as a reporter for another issue. Otherwise, this information (owner, etc)is deleted after the user is deleted from the JSM Users.

      There should be a configuration to keep user type asset attribute for example owner of an asset persistent even it's populated from a dynamic source such as a User Directory and that user is deleted.

      This is required to keep track of Assets' attributes such as owners, persons who gave/distribute the assets, etc.

            [JSDSERVER-11187] Ability to Persist Value of User Type Attribute (owner of an asset) in Insight

            Hi,

            This presents a problem for our Asset management team. We track Hardware assets in Jira Assets and among other attributes "Assignee" of the Hardware (phone, laptop,...). When that user leaves and if it is deleted, there is no longer any record on that specific asset. We have no way of searching through Asset objects that represent Hardware equipment to see which of them were assigned to that deleted user. We need to find out which equipment was assigned to him/her. if we don't there can be money loss to our company. Also, I cannot write a script if I do not have the connection between username and userkey, since, only userkey is written in Asset history.

            So, we are asking to include a check for connections to Asset objects before deleting a user from Jira. That connection has great business value. Other workarounds are also appreciated. Creating an issue for every user ever is very unsustainable.

            Thank you!

            Cheers,
            Marina

             

            Marina Veselić added a comment - Hi, This presents a problem for our Asset management team. We track Hardware assets in Jira Assets and among other attributes "Assignee" of the Hardware (phone, laptop,...). When that user leaves and if it is deleted, there is no longer any record on that specific asset. We have no way of searching through Asset objects that represent Hardware equipment to see which of them were assigned to that deleted user. We need to find out which equipment was assigned to him/her. if we don't there can be money loss to our company. Also, I cannot write a script if I do not have the connection between username and userkey, since, only userkey is written in Asset history. So, we are asking to include a check for connections to Asset objects before deleting a user from Jira. That connection has great business value . Other workarounds are also appreciated. Creating an issue for every user ever is very unsustainable. Thank you! Cheers, Marina  

              Unassigned Unassigned
              c55b673763fb Alper Firengiz
              Votes:
              20 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: