Assets (Insights) Roadmap?

[Amos]

Does anyone know if Assets (or Insights) in Jira Service Management (DC) has a roadmap for future enhancements? I can't seem to find anything.

We use assets as an integral part of our system, but it's still lacking some really essential features, particularly related to security controls (e.g.);

- better fine grain access control akin to issues (like an asset security level scheme) to control visibility of sensitive assets by users, groups, projects etc.

- better control of asset permissions (like an asset permission scheme) that enables schemas, object types and objects actions to be tailor to a broader range of customised roles (not just owner, developer, user).

- Ability to custom define attribute classes (similar to how new custom fields can be built through a third-party plugin). For example, we'd really like to create a 'geometry' attribute that captures a compliant geometry standard data structure (coordinates - geojson as an example) and visually render that on a small web map.

Managing permissions of assets via object type is not a scalable solution for us long term.

[Brant Schroeder · Accepted solution]

@Amos 

You will find upcoming asset improvements in two places:

• The roadmap as you stated (None listed at this time) - https://www.atlassian.com/roadmap/data-center?&search=Assets 
• Atlassian enhancements (There are few in-progress here) - https://jira.atlassian.com/issues/?jql=project%20%3D%20JSDCLOUD%20AND%20type%20%3D%20Suggestion%20AND%20statusCategory%20!%3D%20Done%20AND%20summary%20~%20Asset%20ORDER%20BY%20status%20ASC 

On the enhancement site if the change you want is not listed you can submit it for review and voting.  I would suggest doing this.

[Amos]

Thanks Brant

[Viktoryia K_]

@Amos https://jira.atlassian.com/browse/JSDCLOUD-10621

[Amos]

@Viktoryia K_ as far as I'm aware, you can restricted object types (in data center) to users (each object type has it's own permissions). What I'm suggesting is it be far more fine grained so that you can define your own roles and sets of permissions.

Another issue is also being able to apply object level security (like issue level security) so that sets of assets are only visible to sets of users (assuming they have access to the model).

[Adolfo Almaraz]

Automation would be great when dealing with a large amount of assets.