[
https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-2071:
---------------------------------
Description:
UIMA AS JIRA report is currently being sorted with the resolution first, then
the key, then the type. It should be with the type, then the key, then the
resolution. This happened because Jira was recently upgraded, and the upgrade
reversed the meaning of the sequence of keys in the sorting specification. So,
reverse the sequence, so it corresponds to the new Jira.
Changing in the local uima-as parent pom, as well as the overall build
parent-pom. The local change should be removed (it will be redundant) once the
overall parent-pom is released and the uima-as parent pom is updated to depend
on it.
was:UIMA AS JIRA report is currently sorted in ascending order - oldest
issues first. Change the order to newest first.
Fix Version/s: (was: 2.3.2SDK)
build-parent-pom-3
Summary: Change the specification of sorting keys to correspond to
the sequence needed by the latest Jira upgrade (was: Change sort order of
issues in UIMA AS JIRA report)
> Change the specification of sorting keys to correspond to the sequence needed
> by the latest Jira upgrade
> --------------------------------------------------------------------------------------------------------
>
> Key: UIMA-2071
> URL: https://issues.apache.org/jira/browse/UIMA-2071
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: build-parent-pom-3, 2.3.1AS
>
>
> UIMA AS JIRA report is currently being sorted with the resolution first, then
> the key, then the type. It should be with the type, then the key, then the
> resolution. This happened because Jira was recently upgraded, and the
> upgrade reversed the meaning of the sequence of keys in the sorting
> specification. So, reverse the sequence, so it corresponds to the new Jira.
> Changing in the local uima-as parent pom, as well as the overall build
> parent-pom. The local change should be removed (it will be redundant) once
> the overall parent-pom is released and the uima-as parent pom is updated to
> depend on it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
