[cle-release-team] Close 858 Jira tickets okay?

[Matthew Jones]

Yea, sounds good, looking at these incomplete/incorporated. Always nice to
bulk close tickets that we really don't have to pay attention to. Even
closing the "Won't Fix" will get most of these away and those others should
be closed quickly.

- (Incorporated) That they really were incorporated by some other ticket
(some really aren't and just marked incorrectly)
- (Incomplete) Why were they incomplete, is there a related ticket for
completing it?

Any ones you have questions about or that sound confusing at you can bring
up at the release meeting, but usually they just needed someone to spend a
few minutes looking at each of them.

On Mon, Aug 20, 2012 at 4:44 PM, Neal Caidin <nealcaidin at sakaifoundation.org
> wrote:

> I could take a cut at reviewing the 70 that are incorporated or
> incomplete. It would still reduce the number of issues in the Resolved
> state by over 1/2.
>
> Neal
>
> On Aug 20, 2012, at 4:37 PM, Matthew Jones <matthew at longsight.com> wrote:
>
> For the purposes of the new workflow that sounds good to me.
>
> For sure anything that's Won't Fix, Non-Issue, Cannot Reproduce, Duplicate
> or No Resource should just go to closed.
>
> There might be some argument for wanting someone to review the ones that
> are Incorporated or Incomplete. At least verifying why they are in this
> status and that the ticket that incorporates them is closed or that another
> jira was created if necessary to describe the incomplete part.
>
> On Mon, Aug 20, 2012 at 4:18 PM, Neal Caidin <
> nealcaidin at sakaifoundation.org> wrote:
>
>> Hi All,
>>
>> I've created a Jira filter called "SAK issues Resolved but not Fixed<https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13571>"
>>  .
>>
>> This filters to 858 issues in the SAK queue.
>>
>> The Resolution field (status field is "Resolved" but the resolution field
>> is separate):
>>
>> Won't Fix - 698
>> Incorporated - 40
>> Non Issue - 35
>> Incomplete - 30
>> Duplicate - 29
>> Cannot Reproduce - 24
>> No Resource - 2
>>
>>
>> Is there any reason not to set the Resolution to all of these to Closed?
>> Nobody would be expected to take any action on these, correct? I could do a
>> mass Close and boom, they would be gone. If I shouldn't do this, any
>> suggestions on how to proceed?
>>
>> I think this would move our Resolved total from 1432 to 574.
>>
>> Thanks,
>> Neal
>>
>> ----------------------------------------------------
>> Neal Caidin
>>
>> Sakai CLE Community Coordinator
>> nealcaidin at sakaifoundation.org
>> Skype: nealkdin
>> AIM: ncaidin at aol.com
>>
>>
>>
>>
>>
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120820/64fd2e59/attachment-0006.html