Hi,
with the new custom field type being implemented in 5.4, the old ones appear as deprecated.
Is there any way to change the custom field type without meddling around directly in the database? - The existing custom fields are used in broad variety of scripts and customer request types.
It would be quite a pain to redo those.
Best regards
Hi Thomas!
We are not removing the old field in near future, it's just a reminder to use the new one when creating new custom fields.
For more information on how to migrate the old custom fields, this is a page that describes how to "migrate" to the new Insight Field type: https://documentation.riada.se/insight/latest/insight-administrator-s-guide/insight-custom-fields/migrating-deprecated-insight-custom-field
See this new custom field as a field you should use from now on, when you create new Insight custom fields.
If you feel like this answered your question, please mark it as accepted :)
Cheers!
Alexander
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.
Hi,
Thanks about this documentation and the associated script.
Can you confirm US that issues which contain also "Insight Referenced Object (single)" fields which refer to the old "Insight Object (single) (deprecated)" will not be corrupted ?
How can we back-up the databases in case of errors ?
Thanks in advance for your help,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After execution of the script, no changes have been made to the referenced field, it will still point to the old deprecated one. As such they will work, but you should change the parent field in the configuration so that it points to the new custom field used instead.
As Insight is on the same database as JIRA, you could simply do a backup of the whole database, or a backup of the JIRA instance in JIRA, and that will include all Insight fields.
Cheers!
Alexander
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alexander,
Thanks for your answer. If I change the parent field in the configuration off the referenced field, what will happen on the historical issues ? Will their fields be erased ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The information will not be erased historically. But you need to make sure that the new field you point to is correctly configured of course, so that the references are the same (ie same object set), otherwise when editing the issue, you could possibly remove the references object if the parent object(s) has been changed.
Cheers!
Alexander
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Glad to hear this in advance, as I have not updated yet.
Could you explain what do you mean by deprecated? In the release notes it just says a new field type was added (previously 2 field types now 3).
Thanks
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.