Hello guys.
I need to retrieve jira field information by projectKey/issueType/fieldId.
From I what I know there is no REST call which would let me return such information from Jira - I can only retrieve all fields for certain project/issue combination and then work with it by filtering data for certain fieldId. Like this:
https://jira.my.server/rest/api/latest/issue/createmeta?expand=projects.issuetypes.fields&projectKeys=MYPROJECT&issueIds=1
The problem arises when I need to get info for many fields from the same project/issue: in this case I run the same request many times and then filter it by fieldId. It is excessive and causes too much load at jira server.
So, I decided I will cache this call and save a list of jira fields:
@Cacheable(JIRA_FIELDS_BY_PROJECT_AND_ISSUETYPE)
public List<CimFieldInfo> getCimFieldInfos(String projectKey, Long issueTypeId) {
GetCreateIssueMetadataOptions metadataOptionsBuilder = new GetCreateIssueMetadataOptionsBuilder()
.withProjectKeys(projectKey)
.withIssueTypeIds(issueTypeId)
.withExpandedIssueTypesFields()
.build();
return new ArrayList<>(jiraRestClient.getIssueClient()
.getCreateIssueMetadata(metadataOptionsBuilder)
.claim()
.iterator().next()
.getIssueTypes()
.iterator().next()
.getFields()
.values());
}
And here is where I get hazelcast error:
Caused by: com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable serializer for class com.atlassian.jira.rest.client.api.domain.CimFieldInfo
When I check CimFieldInfo I see that it doesn't implement Serializable. I think that is why Hazelcast complains.
One of the ways I see is to map CimFieldInfo to some custom serializable entity and cache it instead. But it will have too many fields and I don't want to bother with it.
Is there any other solution to this issue?
