Learn how to import to Assets using CSV

In this video, I will show you how you can import from a CSV file to Assets and then map references to other Object Types in the same Object Schema, or even to Object Types in other Object Schemas!
Assets in the Atlassian ecosystem is found in Jira Service Management, and it offers a very flexible way to manage different assets that you can use for support, or to visually show how your assets are connected.
#atlassian #assets #csv #jiarservicemanagement #import

Пікірлер: 11

  • @sidx001
    @sidx0012 ай бұрын

    Wooohooo!!! This video saved me A LOT of work! Thank you so much for this! You are very correct in that the documentation on this is not very good and I have been beating my head on the wall trying to figure this out. Well done!!

  • @jimiwikmanofficial

    @jimiwikmanofficial

    2 ай бұрын

    I am so happy you said that :) That was precisely the goal of making this video. Assets is amazing, but the documentation can use some work, so I'll do my best to do videos on it.

  • @sidx001

    @sidx001

    2 ай бұрын

    Just as an update, the expressions "Label = $()" didn't work for me... I had to use "name = ${}" to get it to work right.

  • @jimiwikmanofficial

    @jimiwikmanofficial

    2 ай бұрын

    @@sidx001 Are you by any chance on Server or Data Center?

  • @jerrodvan24

    @jerrodvan24

    Ай бұрын

    @@jimiwikmanofficial I am on data center and neither label or name worked for me.. its been frustrating

  • @M.AndrewPeercy

    @M.AndrewPeercy

    19 күн бұрын

    @@jerrodvan24 I really struggled with this too. Hopefully this will work for you. Hope the generic syntax makes sense. For the attribute that you are trying to set with the import that maps to an Object, use this AQL: objectType = "" and "" = ${} This will locate the object and filter it to match the key field to the value you have in the import file. I think this same syntax will work to filter an object by a previous set attribute as well, but that gave me some trouble when running the import. I think the earlier comments might work but you would need to substitute "Label" or "Name" with the name of the key value you set in the object.

  • @puzzlebrainiac5238
    @puzzlebrainiac5238Ай бұрын

    Your JSM Assets videos have helped me. Thank you! Once assets have been imported, can Automation be used to create new assets instead of adding each asset individually? If so, would you please elaborate? We have a lot of devices that are assigned to employees regularly and would like to use a Jira service ticket to trigger the creation of new assets. Thank you

  • @jimiwikmanofficial

    @jimiwikmanofficial

    Ай бұрын

    You have three actions related to Assets in your automation: Create object, Edit object and Lookup objects. So you can create new objects using automations and you can update existing ones as well. I am experimenting with my configuration settings, so I can automatically create new projects when requested and then also update the records through JSM requests. I will schedule a video for that to show you how it can be done.

  • @Migey11
    @Migey11Ай бұрын

    Hey. I appreciate this video a lot, but I'm still having problems. I've set up my import and attribute mappings, and can successfully import into a schema. Problem is, when I try to change something about the csv, add it, and import again to update some of my new objects, it instead creates new objects out of every entry in the CSV! I'm using Key + Name as identifiers when importing, with Name as the label attribute. Do you have an idea what I'm doing wrong?

  • @jimiwikmanofficial

    @jimiwikmanofficial

    Ай бұрын

    If you are matching the Key, then they should update properly, but there have been several bugs related to this, so one of those might still be around. Key is something that we can't really do much about, but try to set Name as unique if you do not have several items with the same name? Do that by configuring the attribute and check the Unique box. Let me know if that works for you, otherwise I'll see if I can replicate your problem and find another solution.