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

Is there a way to archive Jira Insight objects?

George Bliss_vl36ti

Hello!

Context

We are using the Jira Insight database to document and track all current versions of software our customers are using. We have created an object type "current customer versions" which stores all the current versions of software for our customers. These versions will link to the support ticket raised by the customer dependent on the software the issue is with.

For example:

Component: Example API

Version: 1.0.0

Dialog: A support ticket is raised and it is against the component Example API therefore the insight version (through automation) will automatically be assigned to that ticket so we know which version has the issue.

Question

Because we don't want to clog up our object type with every version of every product the customer has used and we only want the latest version. Is there a way to archive objects so that previous tickets with issues for 1.0.0 will stay in that ticket rather than it automatically update to the latest version when we upgrade? Because we only want the latest version of the product for the customer, so we will always update the one object to the latest one rather than create multiple.

Accepted answers

Dirk Ronsmans

@George Bliss ,

Insight has a status attribute so you can just use an "Archived" status to show which ones are still active or not.

If you want to avoid that they show up in the general object type overview you can always create a sub-type and move them there but in your IQL set the reference to also include Children.

I feel a status has more value than just a flag as it can be more encompassing.

Things like: Active, Archived, To Be Released, Impacted, ... these statuses can also be used in your Incident Management process when tickets are raised against them.

All comments

Fabio Racobaldo _Catworkx_

Hi @George Bliss ,

in the past I had the same issue and I resolved with the following workaround.

Define a specific column with your desired name (example : active) with values T(true)/F(false)
Edit custom field configuration adding an IQL based on the objectType and to this new column

All not active object will be not selectable by end user.

Hope this helps,

Fabio

Dirk Ronsmans

@George Bliss ,

Insight has a status attribute so you can just use an "Archived" status to show which ones are still active or not.

If you want to avoid that they show up in the general object type overview you can always create a sub-type and move them there but in your IQL set the reference to also include Children.

I feel a status has more value than just a flag as it can be more encompassing.

Things like: Active, Archived, To Be Released, Impacted, ... these statuses can also be used in your Incident Management process when tickets are raised against them.

George Bliss_vl36ti

Hi Dirk,

Thanks for your reply. Your answer is very helpful.

I will give that a go.

Kind regards,

George

George Bliss_vl36ti

Hi Fabio,

Your reply is much appreciated and very helpful.

Kind regards,

George

George Bliss_vl36ti

Dirk, do you know if there is a way to move insight objects to a sub-type? Say if we wanted to have a sub-type where we could move all archived old versions. I can only see an option to clone. Do you know if this is possible?

Best,

George

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud