How are custom fields treated when Altassian releases a new version

[Peter McCurdy]

This question is in reference to Atlassian Documentation: Adding a Custom Field

Ask your question here...

[Nic Brough -Adaptavist-]

I'm not sure what the question is here.  Are you worried about data loss or something else?

[Peter McCurdy]

I am concerned that the custom field we create will not be available after a new release and we will need to recreate it with each new release from Atlassian.

[Nic Brough -Adaptavist-]

That would be suicidal for a product.  You'll find all your standard custom fields (i.e. the types that ship with JIRA) will always come across.  They might change the way they work, and if any of them is to be deprecated, you can be sure it'll be a huge announcement before removal, but no, you'll not lose any fields.

Just about all the non-shipped-with-JIRA custom fields will be the same - you still might lose the content, but there are only three scenarios for that - when the vendor never intends a compatible upgrade, when the vendor hasn't got a compatible upgrade, or there are bugs in it.  Even then, the data will be transferred which will mean it'll come back when the add-on is upgraded (and hopefully if there's a bug too)

[MattS]

Also if you delete an add-on, the data is still preserved in JIRA in case you want to reinstall the same add-on later.