I have a existing request form that has a custom field type "Customer Request Type" from add on Extensions for JIRA Service Management that is located in the hidden section on the request form with a value set.
I need to remove it as it is not supported to migrate from server to cloud. It fails the migration.
The action section shows Show and Remove links and they are both greyed out.
I hover and it displays the field is required by the linked type.
I check the field configuration and it is optional. I check the create screen and the field is on the screen. I check all the other dynamic form configuration and the field is not used in it.
I do full reindex. does not solve it.
Anyone have any ideas? without re-creating request forms as there are many and have a lot of dynamic form configuration.
I ended up deleting the custom field from the admin/issues/custom fields page. It was then not showing on the request type as well. I did this approach because I did not need the field to be migrated at all. This solution will not work for all use cases.
Excellent. If my suggestion also helped you, then please click on Accept Answer button when you have a chance.
The only drawback of your action is that the data in the field is lost permanently.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is interesting.. If you deleted the actual field as you mentioned, it would removed the data completed out from your system. If you removed the field from your project's screen scheme, then the field would be (essentially hidden) from your project and the data is still retained.
I believe if you conduct a re-index process, you will find the data is removed.
It is my 2-cents... I could be wrong.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My initial problem statement stated I did full reindex and it did not solve the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I mis-read your statement of "Data was not needed" as "data was not deleted". Thus, it prompted my response back to you.
For deleting an acutal field - All I am trying to state is that removal of custom field by deleting it, you just need to be aware of that the data is removed permanently.
Since from your update that you stated the "Data was not needed", then it is fine. Otherwise, all of your existing issues with data associated with that specific field are also be lost.
Again, it is just my thought. Have a great weekend.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since this custom field "Customer Issue Type" is sourced /associated when you implemented the add-on Extension for JSM and not native to JSM, you have two options that I can think of -
NOTE - From your updated screenshots, it is not the field named "Customer Request Type" which it is native fot JSM.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I did submit a support request to the add on vendor. I have not received a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. You will need to follow-up with them for input on your support request. Otherwise, if you cannot wait, then you can try to uninstall the add-on to see if the field will be removed. Again, uninstalling the add-on will be a decision that you and your team have to determine/assess of possible impacts in your enviornment.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sheral Hewes ,
Customer Request Type is an essential field in JSM.
Can you share a screenshot please to indicate how Extension for JSM creates another custom field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.