• 737
    • 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.

      Problem Definition

      At the moment, for user attributes, the data must use account id value.

      Suggested Solution

      It will be best if the admin can use their email address instead for an easier process to import user attributes.

      Workaround

      Admin can get user Account Id from "Export User" file at User Management and update the CSV file accordingly: How to import Jira User Attributes to Assets via CSV with either Atlassian Account or Customer IDs
      You can also use Automation to update the user type attribute of the corresponding user as detailed in this article: Update user type attribute of an Insight objects using Automation after Import

          Form Name

            [JSDCLOUD-10487] Allow to use user email address when import user attribute in Assets

            I think this would make life way way way easier for many partners

            Jaime Escribano added a comment - I think this would make life way way way easier for many partners

            Throwing my support behind this very useful enhancement

            Gabriel Points added a comment - Throwing my support behind this very useful enhancement

            It's crazy to me that this isn't already built in. Essential requirement for my business.

            Richard Malone added a comment - It's crazy to me that this isn't already built in. Essential requirement for my business.

            Any update on this feature? It's a huge blocker.

            Simen Vågsæter added a comment - Any update on this feature? It's a huge blocker.

            We have more and more use cases for our cloud org to include Assets. Some of them are blocked because of this ticket. our cloud instance has over 35.000 users. please implement this ticket soon. at least move it from gathering interest to longterm backlog or some other progress.

            Mehmet Sari added a comment - We have more and more use cases for our cloud org to include Assets. Some of them are blocked because of this ticket. our cloud instance has over 35.000 users. please implement this ticket soon. at least move it from gathering interest to longterm backlog or some other progress.

            Especially with external connections importing into the schema, it seems to be a huge loss since we can't map an email address to a user field - there's too many extra steps involved which make it less of an automated process and more of an inconvenience.

            Jennifer Luo added a comment - Especially with external connections importing into the schema, it seems to be a huge loss since we can't map an email address to a user field - there's too many extra steps involved which make it less of an automated process and more of an inconvenience.

            Very helpful addition as tracking users' assets is what we need. We can access the user list through various pickers but some standard of how to pass them is necessary.

            Kurt Anderson added a comment - Very helpful addition as tracking users' assets is what we need. We can access the user list through various pickers but some standard of how to pass them is necessary.

            it is very critical to add this feature

            patrick.hajj added a comment - it is very critical to add this feature

            Of the differences between Insight on Server/Data Center and Insight on Cloud, this one hurts the most.  This makes importing Insight objects by CSV onerous by limiting the size of the imports because we have to closely watch what we put for Users associated with an object.

             

            Robert Wen_Cprime_ added a comment - Of the differences between Insight on Server/Data Center and Insight on Cloud, this one hurts the most.  This makes importing Insight objects by CSV onerous by limiting the size of the imports because we have to closely watch what we put for Users associated with an object.  

            bweberg added a comment -

            This feature is necessary for using Jira Insight which we've started to transition to for Asset Management capabilities. Without this, we are needing to find a method of pulling all Atlassian IDs and mapping each time which can get quite tedious.

            bweberg added a comment - This feature is necessary for using Jira Insight which we've started to transition to for Asset Management capabilities. Without this, we are needing to find a method of pulling all Atlassian IDs and mapping each time which can get quite tedious.

              8f5df932eda6 Dorothea Linneweber
              asantos2@atlassian.com Augusto Pasqualotto (Inactive)
              Votes:
              374 Vote for this issue
              Watchers:
              163 Start watching this issue

                Created:
                Updated: