You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2011/02/23 20:39:38 UTC
[jira] Created: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
Change sort order of issues in UIMA AS JIRA report
--------------------------------------------------
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: 2.3.1AS
UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reopened UIMA-2071:
----------------------------------
just to fix the title and description
> Change sort order of issues in UIMA AS JIRA report
> --------------------------------------------------
>
> 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: 2.3.1AS, 2.3.2SDK
>
>
> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (UIMA-2071) Change the specification of sorting keys
to correspond to the sequence needed by the latest Jira upgrade
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-2071.
--------------------------------
Resolution: Fixed
> 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
[jira] Closed: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-2071.
-------------------------------
Resolution: Fixed
> Change sort order of issues in UIMA AS JIRA report
> --------------------------------------------------
>
> 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: 2.3.1AS, 2.3.2SDK
>
>
> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik reopened UIMA-2071:
---------------------------------
Undo the previous fix. All that needs to be done is to change sortColumnNames from Type,Key,Status to Status,Key,Type due to the change in the latest JIRA system.
> Change sort order of issues in UIMA AS JIRA report
> --------------------------------------------------
>
> 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: 2.3.1AS
>
>
> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-2071.
-------------------------------
Resolution: Fixed
> Change sort order of issues in UIMA AS JIRA report
> --------------------------------------------------
>
> 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: 2.3.1AS
>
>
> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (UIMA-2071) Change the specification of sorting
keys to correspond to the sequence needed by the latest Jira upgrade
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ 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
Re: [jira] Updated: (UIMA-2071) Change sort order of issues in UIMA
AS JIRA report
Posted by Marshall Schor <ms...@schor.com>.
The issue here is that Apache infrastructure recently upgraded our Jira
installation. This had a side effect, in that the treatment of the sequence of
keys to use for sorting, was reversed in the newer Jira.
UIMA SDK 2.3.1 was released (and therefore the issuesFixed set was generated)
using the older, previous Jira.
This fix will keep the same sort as we used in the 2.3.1 release, now that it's
being run against the upgraded Jira.
I hope that explains it :-) -Marshall
On 2/23/2011 4:57 PM, Jörn Kottmann wrote:
> Don't we do that for 2.3.1 ?
>
> Jörn
>
> On 2/23/11 10:56 PM, Jerry Cwiklik (JIRA) wrote:
>> [
>> https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Jerry Cwiklik updated UIMA-2071:
>> --------------------------------
>>
>> Fix Version/s: 2.3.2SDK
>>
>>> Change sort order of issues in UIMA AS JIRA report
>>> --------------------------------------------------
>>>
>>> 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: 2.3.1AS, 2.3.2SDK
>>>
>>>
>>> UIMA AS JIRA report is currently sorted in ascending order - oldest issues
>>> first. Change the order to newest first.
>
>
>
Re: [jira] Updated: (UIMA-2071) Change sort order of issues in UIMA
AS JIRA report
Posted by Jörn Kottmann <ko...@gmail.com>.
Don't we do that for 2.3.1 ?
Jörn
On 2/23/11 10:56 PM, Jerry Cwiklik (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jerry Cwiklik updated UIMA-2071:
> --------------------------------
>
> Fix Version/s: 2.3.2SDK
>
>> Change sort order of issues in UIMA AS JIRA report
>> --------------------------------------------------
>>
>> 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: 2.3.1AS, 2.3.2SDK
>>
>>
>> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
[jira] Updated: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-2071:
--------------------------------
Fix Version/s: 2.3.2SDK
> Change sort order of issues in UIMA AS JIRA report
> --------------------------------------------------
>
> 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: 2.3.1AS, 2.3.2SDK
>
>
> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira