Jira Asset Management Evaluation

[khenson]

I will try and keep this concise, but I have a lot of questions. We are evaluating if Jira Asset Management will work for our needs and I would like to know if its capable of doing these things.

1. An easy way to schedule assets hourly. We have robots and systems they interact with and want to be able to link them all together clearly which JAM seems to do well, but the robots are booked in blocks down to the hour via Jira ticket and move between systems multiple times a day. I don't see a way to automate changing the links between booking request tickets based on a calendar, or Jira system. Is this possible? Or not the right tool for this use case?

2. Nested Object Hierarchy. In our sandbox I have a robots with an attribute "System". The system objects are nested by revision. When I go to a robot and want to assign "S-Ob 1.2" the only options I get are "System Rev1" and "System Rev2". In other words it only shows one level down, not all the sub-objects. Is this configurable once we have our own instance of JSM or will this always be an issue and I would need all the Objects only 1 layer down from the attribute?

System

- System Rev1

      - S-Ob 1.1

      - S-Ob 1.2

      - S-Ob 1.3

- System Rev2

      - S-Ob 2.1

      - S-Ob 2.2

      - S-Ob 2.3

- Ect

3. Can you update the Assets linked to a Jira ticket from the Jira ticket side, or only from the Assets side?

4. Is there a way to get an asset to show as "Inactive" and maybe highlight in red on the Jira side?, so its clear that the assigned resource isn't available. 

Thank you in advance

[Andy Rusnak]

Hi @khenson , 

Thanks for using the Atlassian Community!  I will be honest, this is probably best to submit through a Support Request so that we can review exactly how things are configured.  Without seeing the actual configuration it is difficult to fully answer your questions, but I will try to provide some insight here as best I can: 

1. If there is a Jira Work Item involved that 'schedules' these items, you should be able to potentially fire this off to modify the Asset Attribute via an Automation rule.  The Automation rule would need some type of trigger as to when to update the object, but if you have something like that, you should reasonably able to fire Automation rule that can update the Object's attribute either through an out the box action or via the Assets REST API and a Send Web Request Action.  
2. This is configurable.  The Attribute that defines the relationship has an Object Type set within it.  So if you set an object attribute type to the first level, that is all you will see.  The attribute is only configurable for a single object type, but it is defined by the hierarchy.  You should be able to use any object type within that reference for the attribute configuration.  
3. Yes you can.  
4. You can use a Status attribute for something like this.  Statuses will allow you to configure a colored attribute on the object type as an attribute. Then you just need to configure your Jira Assets Custom Field on the Jira Work Item to display the status chip on the Work Item view.  It won't color the whole object display on the custom field, but it should show the status attribute within that view then.  

Again some of these answers might be a bit vague since I don't know the totality of your set up, but hopefully this helps a little bit and if you need a more detailed in depth response a support issue with us might be the best way to go.  

Best,
Andy