For my customer I am currently setting up Asset, with Asset custom fields to present/select for customers when creating tickets. When I set up my request form, with the Asset custom fields, Jira automatically wipes the whole setup. I assume this is a bug, but would like to hear if anyone else have experienced the same thing and that it is in fact an user error on my behalf: What I have done/am doing, that currently is not working at all: * The roles for Object type has been updated with jira-users as User (I do not think this is needed? Nevertheless, has been done in my bug-fix journey) * Asset custom fields created * Asset custom fields added to issue type screens * New Request type (for testing purposes) has been added, and in the setup both the Asset custom fields as well as other standard Jira fields are added. Both in portal view as well as Issue view. When doing this, save has been done (on repeat!) * When finalised setup of the request type, all fields are present when switching between Request form and Issue view. All good so far * I then navigate back to request types overview. * When so going back to the new request type, the whole setup is wiped and my setup is no where to be found. So - what is happening here? Has anyone else experienced the same or should I report this as a bug?

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

Bug? Asset fields are removed from request type

ihe

For my customer I am currently setting up Asset, with Asset custom fields to present/select for customers when creating tickets.

When I set up my request form, with the Asset custom fields, Jira automatically wipes the whole setup. I assume this is a bug, but would like to hear if anyone else have experienced the same thing and that it is in fact an user error on my behalf:

What I have done/am doing, that currently is not working at all:

The roles for Object type has been updated with jira-users as User (I do not think this is needed? Nevertheless, has been done in my bug-fix journey)
Asset custom fields created
Asset custom fields added to issue type screens
New Request type (for testing purposes) has been added, and in the setup both the Asset custom fields as well as other standard Jira fields are added. Both in portal view as well as Issue view. When doing this, save has been done (on repeat!)
When finalised setup of the request type, all fields are present when switching between Request form and Issue view. All good so far
I then navigate back to request types overview.
When so going back to the new request type, the whole setup is wiped and my setup is no where to be found.

So - what is happening here? Has anyone else experienced the same or should I report this as a bug?

Accepted answers

ihe

I´ve received response from Atlassian (I issued a bug ticket) and the answer is this:

* when fields are added to portal view, they automatically are added in issue view as well

* if manually adding same fields in issue view, the portal view is nulled out

I have retested and by only adding in portal view, the whole thing works. I have however given feedback that this should be clear in both the knowledge articles as well as in the actual issue view, as this was not clear to me. I see other people here in Community have experienced/done the same as me.

For instance: https://community.atlassian.com/t5/Jira-Service-Management/Can-t-save-Request-type-changes/qaq-p/2077843

All comments

Joseph Chung Yin

@ihe -

Hi there:

Happy 2023. Don't know if you click on the "Save changes" button when you switched out to "request types overviews"? This is something that users may missed after he/she conducted configuration changes often.

One other thing - For Assets Jira custom fields, your customers must also be granted with the appropriate Assets (Insight) schema rights for your field to work properly via the Portal UI.