New FieldTypes in API causing problems

[Nathan Frost]

We recently started having trouble parsing new FieldTypes that appeared this weekend. We are seeing "any" and "option" for the first time in the field type schema.

Is there an explanation on why we are seeing these types of fields all the sudden? Were some custom fields switched to these new types? Is there a way for us to put them back to their previous types?

It looks like the Rank fields have the new type of "any". And one of our version fields has a type of "option". Unfortunately we parse these string values and if it fails it crashes our program, we are working on a more graceful failure.

Here is a list of known field types we have, please let us know which ones are missing and what they mean:

STRING(),
NUMBER(),
COMPONENT(),
DATE(),
DATETIME(),
EPOCHDATETIME(),
USER(),
GROUP(),
PROJECT(),
ISSUETYPE(),
VERSION(),
RESOLUTION(),
STATUS(),
PRIORITY(),
TIMETRACKING(),
VOTES(),
ARRAY(),
SECURITYLEVEL();

Thank you,

Nathan

[Marek Pazik]

Hi Nathan,

Here is the list of all types used in JIRA:

string
number
date
datetime
comments-page - a page with comments
array - if type is array, you will see item type in items field in field schema
option - used in select and multi select fields
option-with-child - used by CascadingSelect fields
any - means JIRA doesn't know what the schema of field value is. But if something was being returned previously, then it is still returned in the same form. So each field type with that any type has to be supported individually.
resolution
user
group
version
votes
watches
component
attachment
issuelinks
priority
status
project
issuetype
securitylevel
worklog
timetracking 

Hover JIRA's plugins can define own set of types for fields.
Let me know it that helps or if you need more detailed information.

Regards,
Marek