You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we fetch the "create issue metadata" data from Jira, it limits the number of fields expanded to a maximum of 50 fields. For a given project & issue type that has more than 50 configured fields in Jira, some fields will not be shown if it happens to be omitted from the 50 that are returned from Jira.
The task here is to make sure we include the field data for all fields on a given project & issue type. We may need to change something about the existing request that expands the fields, or perform additional requests to fill in the missing data.
The text was updated successfully, but these errors were encountered:
Here is a minimal example that is returned from Jira. Notice the fields are in alphabetical order, and that fixVersions is the last listed field. Since Jira only returned 50 fields, all fields that come after fixVersions were omitted. In the case of the project & issue type in question, there should be other fields such as priority.
When we fetch the "create issue metadata" data from Jira, it limits the number of fields expanded to a maximum of 50 fields. For a given project & issue type that has more than 50 configured fields in Jira, some fields will not be shown if it happens to be omitted from the 50 that are returned from Jira.
The task here is to make sure we include the field data for all fields on a given project & issue type. We may need to change something about the existing request that expands the fields, or perform additional requests to fill in the missing data.
The text was updated successfully, but these errors were encountered: