Hi folks, our team has recently purchased Jira Assets and connected our MDM so that a live inventory can exist there. Objects representing our hardware can be found easily and attributes are updated daily via API.
Regardless of that fact, we have yet to figure out how to connect Jira users to specific Jira Assets automatically. I should emphasize that we only have hardware assets in Assets and do not have objects set up for our users as well. I wanted to post here and find out of such a solution exists before completing the tedious process of making a user object for each of our couple hundred employees.
Has anyone found a way to tie an incoming IT issue (or any JSM issue) to a Jira user account automatically? We have the user attribute attached to our hardware objects, but we are scratching our heads at how we can automate a device connection to a specific Jira user. There seems to be no way to connect something like the issue reporter to the Jira Asset "User"(User attribute type) property we have created for our objects.
Any ideas? Hopefully we're just missing something obvious but if we truly have to create user objects for all employees in order for this to work please let me know.
Thanks!
Yes, this can be done, you just have to add an attribute of the type User. That way you can set the owner based on the users that you have in your Atlassian environment. You can then have an automation that adds the asset to requests based on the reporter.
Hi Mikael, thank you for your response. We do currently have this configured and the objects have an attribute that shows who owns/uses the device, as shown in the screenshot. I think the part I'm missing is that when said user files a ticket/issue with IT via our portal, the linkage to the request is missing, and we do have the object field on the request type issue view, so it is ready to be filled in.
Are you aware of an automation option that would find the asset based on the reporter? Or any ideas on how you might start with that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is something that you control in the custom field, you have to set the filter issue scope, similar to what I have for our peripherals field:
I am not 100% sure if you can set that to the reporter or not since I have not tried that yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you want to set the asset after the request is created automation is the way to go and the edit issue step in it would look something like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for the additional information; I'll play around with those scopes as I definitely misunderstood their function. You've got us moving in the right direction!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.