Description
Context:
A recurring problem is that Portfolio is unable to import new releases due to the LexoRank length limitation. See JPO-3334 and JPO-3482.
This is a silent failure:
- Users would typically report that they can not seeing new releases when editing the issues sources.
- The only indication of this problem is a single error in the Jira application logs.
Example error message in logs:
[c.a.r.c.b.agile.rank.AgileRankOperationResponse] Agile call returned errors: -171665=ErrorCollection[errors=[ErrorCollection.ErrorItem[contextId=<null>,messageKey=gh.lexorank.service.error.reindex.required,params={}]],reasons=[CONFLICT]] XXXX-XX-XX XX:XX:XX,XXX http-nio-8080-exec-XXX ERROR XXXXX XXXXXXXXXXXXXX XXXXXX XXX.XXX.XXX.XXX,XXX.XXX.XXX.XXX /rest/jpo/1.0/plan/setup/projects [c.a.r.j.env.rank.BaseJiraEnvironmentRankService] com.atlassian.rm.common.bridges.agile.rank.BatchAgileRankException at com.atlassian.rm.common.bridges.agile.rank.AgileRankOperationResponse.create(AgileRankOperationResponse.java:44) at com.atlassian.rm.common.bridges.agile.InternalAgileRankService.rankLast(InternalAgileRankService.java:92) at com.atlassian.rm.common.bridges.agile.BaseAgileRankServiceBridgeJpo.rankLast(BaseAgileRankServiceBridgeJpo.java:38) at com.atlassian.rm.common.bridges.agile.AgileVersionDomainRankServiceBridgeJpo.rankLast(AgileVersionDomainRankServiceBridgeJpo.java:11) at com.atlassian.rm.jpo.env.rank.BaseJiraEnvironmentRankService.rankLast(BaseJiraEnvironmentRankService.java:53) at com.atlassian.rm.jpo.core.rank.BaseKeyRankService.stackUnknown(BaseKeyRankService.java:102) at com.atlassian.rm.jpo.core.rank.DefaultVersionDomainKeyRankService.stackUnknown(DefaultVersionDomainKeyRankService.java:11) at com.atlassian.rm.jpo.core.version.VersionOrderService.stackUnknownEnviromentVersions(VersionOrderService.java:43) at com.atlassian.rm.jpo.core.project.ProjectService.getDeepProjects(ProjectService.java:104) at com.atlassian.rm.jpo.core.project.ProjectService.getDeepProjectsById(ProjectService.java:81) at com.atlassian.rm.jpo.core.issuesource.context.DefaultIssueSourceContextService.getProjectInfosForIssueSources(DefaultIssueSourceContextService.java:61) at com.atlassian.rm.jpo.rest.service.plan.setup.projects.PlanSetupProjectsRestEndpoint.getProjects(PlanSetupProjectsRestEndpoint.java:51) ...
Atlassian's online documentation for Managing LexoRank only covers the standard issue rank field, and does not address the virtual fields added by Portfolio.
Suggestion:
- Report the problem to the user instead of a silent failure.
- Provide the administrator the means to monitor and manage Portfolio's virtual fields.