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; } } }

Assets objects versioning

Ksenia Abdulina

Hi there!

Is there any way to have objects versions in Assets? There is a history log of changes made to an object but there is no "revert to previous version" function or even object version term.

What I can think of is an attribute with at least version number but there's no chance to compare two incremental changes of an object.

Any thoughts?

Accepted answers

All comments

Kai Becker

Hi @Ksenia Abdulina

thank you for your question.

AFAIK there is no solution to your problem I can imagine.
Assets does not allow to compare two versions, neither does Jira for Issues in terms of history.

Ksenia Abdulina

Hi @Kai Becker

I just wonder if that just isn't the right way to use Assets?

For example, I have Assets Object Schema with all my company servers with theirs parameters, such as CPU, RAM, Disks etc. I've built a process that update my server object using fields from Jira issue. So in Service desk portal I have a request type "Change server parameters". Using SR I update assets attribute values in cmdb. But then, I need to revert changes from previous request. For now I can do so by simply look at the history log and edit values manualy. If I have more than one issue affected my object it has become more difficult to understand what values should I revert exactly.

Anyway, my current idea is to create a csv file attached to the object where I can store changes from each issue. Hope this solution will help anybody else.

Kai Becker

Hi @Ksenia Abdulina

thanks for updating on your question.

There might be something that could make your life easier.
What about writing the current state of the object into the JSM issue, after updating values?
You could use an Automation rule, that reads the attributes and write a comment to the issue.
You could then use the object view to take a look at the connected issues and see the changes. Hope this helps.

Ksenia Abdulina

Hi @Kai Becker

The list of connected issues are great but there's no chance to see what attributes were updated by specific connected issue from an object view. E.g. if in history log there is a line like

UserMadeChange: 'CPU' changed from '2' to '4', source 'KEY-N'

that would be kind of a solution.

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-server

jira-service-management

assets

jira-service-management-server