When I first saw the Asset Management feature, my mind was blown. Like, I'd have given a kidney to have a tool like this back in some of my previous jobs. But then I started actually using it and I'm finding it pretty limiting. Like, this could be doing a lot of heavy lifting in JSM, but it just doesn't seem to be very well integrated. Some examples: * Unable to set default values or hide the field in in a request type.* [JSDCLOUD-11227] Default value for object attributes - Create and track feature requests for Atlassian products. * [JSDCLOUD-10317] Ability to hide Assets object custom field in customer portal - Create and track feature requests for Atlassian products. * This seems like essential functionality, and the "workaround" really doesn't solve the problem. * This one thing could solve a whole lot of problems for folks. * Unable to use a user's email address in place of the account ID for user attributes.* [JSDCLOUD-10487] Allow to use user email address when import user attribute in Insight - Create and track feature requests for Atlassian products. * I'd argue, that this should be a default option everywhere, not just for import. I'd want to use this in JQL/AQL as well. * Atlassian's own Entra ID integration plugin only supports a manual import with no apparent way to schedule or trigger it.* How to automate the import of EntraID users with J... (atlassian.com) * Why wouldn't they add a scheduling feature to this?! In what realm would an organization choose to import from Microsoft just one time and then never again? Of course you'd need to keep the objects synchronized regularly, so why not give us the ability to schedule the import? * The documentation is horrendous.* Here's an interesting trek. * Step 1: Automate your objects in Assets | Jira Service Management Cloud | Atlassian Support * This page has no useful information and points you to Learn more about automation for Jira. * Step 2: Learn more about automation for Jira. Well, I guess we go to Get Started? * Step 3: View the guide * Step 4: Give up I guess? * Install an asset management app | Jira Service Management Cloud | Atlassian Support* Why do I need an Asset Management App? Is there a way to filter for an Asset Manager App in the marketplace? What even is an Asset Manager App? Is it required? * What is the Assets objects field? | Jira Service Management Cloud | Atlassian Support* "The Assets objects field functions differently in Cloud than it does in the Server/DC version of Assets. In Assets for Cloud, users cannot use an Assets object field to sort search results in a JQL query."* WHY?!?!?! You are pushing people to the Cloud where some important features are just not implemented! * You can't use non-asset fields in a `aqlFunction(aql)` it only works with asset object custom fields. That means if you can't use things like `currentUser()` in an aqlFunction.* You can do things like: * Find issues where a website is reported and where the customer account manager is Mathias Edblom: customField in aqlFunction("Customer.\"Account Manager\" = \"Mathias Edblom\"") * But you can't do things like: customField in aqlFunction("Customer.\"Account Manager\" =currentUser()") So, back to my question, why isn't Asset Management more developed? I really want it to be good, and it's so close, but I keep running into roadblocks over and over again. It's making it challenging to advocate for this product at my organization.

There doesn't seem to be an easy way for each individual attribute to determine if it should be mandatory, read-only, hidden, or only accessible by specific roles. I discovered that there is a way to make an attribute mandatory. In the attribute's properties, in the Cardinality tab, set the minimum to 1. I can't really help with the rest, but that's one thing to mark off the list. I've had to work around most of these other issues using the API. No ability to set a default value for an attribute where it can be filled in automatically. I think you can do this during the import process, but their import process is pretty complex. Overall, I just wish they had better walkthroughs to demonstrate how to do things in addition to their documentation. Like, give us some real examples of things that you can do with assets so we can understand better how it works.

While I'm relatively new to JSM and Assets, I agree with just about everything that @Monty has said, especially when trying to use Atlassian's documentation for various features. I've come across some pretty poor product documentation before, but never as many as when trying to understand Jira/JSM better. Documentation is lacking at best. It feels like Atlassian either has a very small team working on the Assets feature, or Assets is a very low priority for them. Coming from other platforms with more robust CMDB configurations out-of-the-box, it's mind boggling to me that Atlassian doesn't have pre-defined schemas already set up and ready for use like Users, Companies, Locations, etc. so that the customer doesn't need to manually build out things that are already well defined (e.g., imports from Entra ID). While I will continue to develop our overall schema to store object information, I have quite a bit of frustration with how it is currently configured, and not sure if there will be any ROI for the time I've spent doing so. A few things that I think are missing that make working with Assets much more difficult than it needs to be include: * Object attributes have case sensitive names, and no way to define an attribute name with a separate display value.* As an example, configuring something similar in ServiceNow I would set the attribute (column) name to something like "account_enabled" and a display name of "Account Enabled". * If I want to then change the display name of the attribute to "Enabled", I don't need to worry about changing it EVERYWHERE in the system (e.g., Automations, Filters, etc.) like you do currently (Yes, it will break things if you don't). * Unable to search by individual columns/attributes makes filtering and finding the data you need more of a chore than needed. A text search box at the top of each column to filter values would be much more intuitive than either having to use the inefficient filtering by attribute or write an AQL statement to filter. * Pagination of objects stops after X number of objects. You will not be able to view and browse all of the data without filtering further to reduce the total number of objects below that X number. * There is no ability to group objects by an attribute within the UI (e.g., group all users by their Company and display the groupings). * No ability to conditionally hide attributes on an object. You can hide the unused fields, but that's it. * No ability to set a default value for an attribute where it can be filled in automatically. * As an example, I have a User object and want to associate that with the Jira User account so there is some relationship there. I can't set a variable like "object.mail" as the default so that it finds the Jira User with that email address and automatically populates the field. * Limited Type Value options. Currently you can only create attributes with the types Text, Integer, Boolean, Float, Date, Date Time, URL, Email, Text Area, Select and IP Address. Others should be available:* Auto-Increment (for numbering) * Counter * Currency * Day of week * Decimal * Formula * HTML * Icon * Image * JSON * Month of year * Password (masked) * Percent * Phone number * Reference * Script * String * Timer * XML * There should be a way to make the available options for an attribute depend on the value of another field, as defined by the customer. * Reporting is near useless at best. There just aren't very good options for analyzing data related to Assets. Limited chart types, limited ways to query or slice the data and it's frustratingly slow. * Object Keys can't be reset and just continue to increment, regardless of the schema that the object is in. After test imports, changing configurations, etc. asset keys are now in the 321,501 range even though I only have a total of 23k objects.* Further the keys should increment on a per schema basis, and not share the same numbering across all schemas. * There doesn't seem to be an easy way for each individual attribute to determine if it should be mandatory, read-only, hidden, or only accessible by specific roles. * No way to configure a field to be a calculation of other fields, or concatenation of multiple text fields.

It is however what you did suggest. But that does not change the point - the Assets team have a lot of things they would like to do, a lot of things that customers want them to improve, and simply not enough time to do it all now.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why isn't Asset Management more developed?

Monty_lrtlpy

When I first saw the Asset Management feature, my mind was blown. Like, I'd have given a kidney to have a tool like this back in some of my previous jobs. But then I started actually using it and I'm finding it pretty limiting. Like, this could be doing a lot of heavy lifting in JSM, but it just doesn't seem to be very well integrated.

Some examples:

Unable to set default values or hide the field in in a request type.
- [JSDCLOUD-11227] Default value for object attributes - Create and track feature requests for Atlassian products.
- [JSDCLOUD-10317] Ability to hide Assets object custom field in customer portal - Create and track feature requests for Atlassian products.
- This seems like essential functionality, and the "workaround" really doesn't solve the problem.
- This one thing could solve a whole lot of problems for folks.
Unable to use a user's email address in place of the account ID for user attributes.
- [JSDCLOUD-10487] Allow to use user email address when import user attribute in Insight - Create and track feature requests for Atlassian products.
- I'd argue, that this should be a default option everywhere, not just for import. I'd want to use this in JQL/AQL as well.
Atlassian's own Entra ID integration plugin only supports a manual import with no apparent way to schedule or trigger it.
- How to automate the import of EntraID users with J... (atlassian.com)
- Why wouldn't they add a scheduling feature to this?! In what realm would an organization choose to import from Microsoft just one time and then never again? Of course you'd need to keep the objects synchronized regularly, so why not give us the ability to schedule the import?
The documentation is horrendous.
- Here's an interesting trek.
  - Step 1: Automate your objects in Assets | Jira Service Management Cloud | Atlassian Support
    - This page has no useful information and points you to Learn more about automation for Jira.
  - Step 2: Learn more about automation for Jira. Well, I guess we go to Get Started?
  - Step 3: View the guide
  - Step 4: Give up I guess?
- Install an asset management app | Jira Service Management Cloud | Atlassian Support
  - Why do I need an Asset Management App? Is there a way to filter for an Asset Manager App in the marketplace? What even is an Asset Manager App? Is it required?
What is the Assets objects field? | Jira Service Management Cloud | Atlassian Support
- "The Assets objects field functions differently in Cloud than it does in the Server/DC version of Assets. In Assets for Cloud, users cannot use an Assets object field to sort search results in a JQL query."
  - WHY?!?!?! You are pushing people to the Cloud where some important features are just not implemented!
  - You can't use non-asset fields in a `aqlFunction(aql)` it only works with asset object custom fields. That means if you can't use things like `currentUser()` in an aqlFunction.
    - You can do things like:
      - Find issues where a website is reported and where the customer account manager is Mathias Edblom:
        customField in aqlFunction("Customer.\"Account Manager\" = \"Mathias Edblom\"")
    - But you can't do things like: customField in aqlFunction("Customer.\"Account Manager\" =currentUser()")

So, back to my question, why isn't Asset Management more developed? I really want it to be good, and it's so close, but I keep running into roadblocks over and over again. It's making it challenging to advocate for this product at my organization.

Accepted answers

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Assets is something Atlassian acquired, relatively recently, not wrote, and they are trying to integrate into JSM as best they can. The original product was not closely aligned with the way Jira does things, so it is slow going. (But the original product worked as well as it could given everything had to be done outside Jira)

I know that is a very apologistic thing to say, but the short answer is "time". Atlassian's Assets team simply has not had enough time to develop everything that we want.

John Funk

Well said

Patrick_ko51ej

The worst thing is that after implementing it is that they are not even part of any backups. There is not even a bin where you can restore from.

Thanks, Atlassian once again, forcing me to either manually export it as tables?? or having to buy some third party plugin. Its a joke.

Sorry, just wanted to add some of my frustrations here as well.

Vish Reddy {Revyz}

Hi @Patrick, Patrick, @Monty ,

I represent Revyz, While I can't solve all issues in using Assets, I can provide with our Assets Data Manager app for free for you for a period of a year if you are open to helping us improve it further, atleast it will help automate some tasks for you, I am by no means saying it will solve all the issues you have highlighted.

As of today we automate the backup and granular restore of Asset config and objects. We have a roadmap which addresses additional use cases and I would love to work with you to see what we can do further.

Please drop me an message (vish@revyz.io) if you are interested.

Thank you

Vish

Monty_lrtlpy

Ok, but they keep choosing to acquire new things that take time to integrate when they haven't finished integrating the last 10 things they acquired.

If they are going to acquire a product, they should allocate the resources to integrate it fully. Instead, they have this weird mashup of products that kind of work with each other, but everything has a unique licenses, and nothing is ever finished.

They are gung ho about Compass and Atlas, but still haven't finished integrating Assets. I get that it's hard, and it takes resources, but they are making the decision to spread those resources thin.

Monty_lrtlpy

As I said in my original post, this product has SO much potential. I advocated STRONGLY for buying the additional licensing to gain access to it. I'm now on the hook for showing its value and I'm struggling.

I can make some things work, but the places where integration isn't fully baked is alarmingly bad.

Here's an example. I can create an object with an attribute that connects the jira user account with the object. (It's even in their People template).

Great, so I have an object, and a user account is attached to the object, but then I can't use that asset in any place where a user would be useful. I can't assign tickets to that User's asset object. It doesn't automatically build relationships with that the jira account without creating a custom asset field (which I can't set a default for or hide).

So now, I have to create a custom asset field, then use automation (which is limited) to try to copy the assignee or reporter to the asset field when it should already be linked. From the issue view, now we have multiple fields that an agent has to see (and not touch) so that everything works.

Here's a real world example that I'm trying to solve:

An agent needs to escalate an issue to their manager.

We have an asset object called Person that has attributes for jira user, and manager (another Person object).

So, I have all the relationships I need right? I have the assignee (jira user), that jira user is in an attribute of a person object, that object has a relationship with another person object for their manager, and the manager person object has a relationship with its own jira user.

But I can't use any of those relationships because aqlFunction() can't use non-asset functions to lookup values.

I should be able to create a Queue with a JQL/AQL that says: If one of my employees raises an issue, put it in this queue.

Nic Brough -Adaptavist-

No sane organisation would stop everything else they are doing in order to consolidate and integrate one thing that they have acquired.

An organisation like Atlassian has dozens of products and services, and they have aspirations to do grow and do more. You are asking 10,000 people to stop doing anything until a new thing has been developed to the point that a customer is demanding, which is frankly silly, as most of the organisation does not have the skills to do anything to help.

Would you expect a supermarket to tell you "we're only going to sell you fruit for the next month, while we roll out our new dragonfruit product"?

Monty_lrtlpy

Monty_lrtlpy

Wait, what do you mean it's not backed up?!

So, we put all our asset information into this system and if something happens there's no way to recover or restore anything?

Oh gosh. What if someone comes in and mucks it all up? That's one mistake away from a major problem.

Vish Reddy {Revyz}

Hi @Monty

Part of the Cloud Security Shared Responsibilities is that a customer is responsible for their data that lives in the SaaS application.

This is true with all SaaS applications, be it Microsoft, SalesForce, Atlassian etc..

Nothing unusual about Atlassian in this context i.e. Atlassian is no different from other SaaS vendors.

Here are links to some of the leading companies Cloud Security Shared Responsibilities docs:

From an Atlassian perspective you should review these two docs:

1. Atlassian Cloud Security Shared Responsibility Model

2. Atlassian Security Practices

As you would see in the Atlassian Security practices doc -

"We do not use these backups to revert customer-initiated destructive changes, such as fields overwritten using scripts, or deleted issues, projects, or sites. To avoid data loss, we recommend making regular backups."

If someone on the customer side mucks up something it is the responsibility of the customer to be able to recover back their data and hence the need for a customer to backup their data.

In the most recent example from yesterday, Atlassian did an upgrade / change to the system which messed up Automation rules for a large no. of customers, in that scenario Atlassian was responsible for getting things back to normal (as they did or are in the process), on the other hand if someone on the customer side deleted something inadvertently (which of course happens) then it is the responsibility of the customer to have backup their Automation Rules (in this case) to recover back!

I am just the messenger here :-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management