Can you remove archived versions from forms in JSM?

[Daniel Ogulnick]

Hello everyone,

My company maintains a list of our software versions in JSM which go back many years, and would like to clean-up the list as it is displayed to users in the portal. We tried archiving versions that are currently out of support, but these versions still display in the portal. We would prefer not to delete the versions, so as to accurately maintain our historical data. Has anyone encountered the same issue or know if there is a workaround? It seems to me that this certainly should not be the case, as it essentially defeats the point in archiving them. Any advice would be greatly appreciated.

[Daniel Ogulnick]

We have a field called "Versions" in the form, which is linked to the Affected Versions Jira field. The field is not in the request type itself. 

[Marc - Devoteam]

Hi @Daniel Ogulnick 

What field is used on the portal to show version numbers, is the Fix Version, Affected Version or another field, like a custom field?

[Daniel Ogulnick]

Hi Marc,

It is the Affects Versions field.

[Marc - Devoteam]

HI @Daniel Ogulnick 

The only option you have is to archive the version.

[Daniel Ogulnick]

Yes, but the archived versions still appear on the list in the forms. Is this supposed to be the case?

[Marc - Devoteam]

So this is probably related to the not fully integrated forms bought app and the JSM

And Yes I can reproduce this.

Using the field on the request type, not in a form will not show archived version, but in from they will be shown.

I found an open feature for this, JSDCLOUD-16509 or create a support ticket and see if this can be classified as a bug