[cle-release-team] Indie Filters and JIRA Workflow

Thomas, Gregory J gjthomas at iupui.edu
Thu May 10 13:19:22 PDT 2012


I meant:

project = MSGCNTR AND status = Resolved AND ("2.9.x Status" = Merge OR
"Merging " = "3.0 code line") ORDER BY updated ASC

Greg

On 5/10/12 4:17 PM, "Thomas, Gregory J" <gjthomas at iupui.edu> wrote:

>I think MSGCNTR is unique with the Merging/code line method.  But yes, I
>think this would work as a combined search:
>
>project = MSGCNTR AND status = Resolved AND ("2.9.x Status" = Resolved OR
>"Merging " = "3.0 code line") ORDER BY updated ASC
>
>There's none for 2.9.x as Resolved right now, but that should work for
>both.
>
>Greg
>
>On 5/10/12 3:54 PM, "Bryan Holladay" <holladay at longsight.com> wrote:
>
>>> MSGCNTR - has the sakai 2.7.x, 2.8.x, and 2.9.x status flags on the
>>>jiras,
>>> but it's indie version is actually 3.0 for 2.9.x.  I'm not really sure
>>>how
>>> to interpret this one
>>
>>Msgcntr was one of the early Indy projects and the concept of merge
>>status's for different versions other than Sakai main releases wasn't
>>fleshed out yet.  I'm not sure if others use this setup, but MSGCNTR
>>has custom settings called "Mergeing".  Right now there are only two
>>options:
>>
>>Merging
>>2.8 code line
>>3.0 code line
>>
>>So you can write the search query like:
>>
>>project = MSGCNTR AND status = Resolved AND "Merging " = "3.0 code line"
>>
>>
>>However, I've found that most people don't know this and end up
>>putting the Sakai merge field to 2.9.x (or whatever), so you'd
>>probably have to have two searches to pick up all intended ones which
>>account for both MSGCNTR and Sakai merge fields. (can you concat
>>searches into one?)
>>
>>-Bryan
>
>_______________________________________________
>cle-release-team mailing list
>cle-release-team at collab.sakaiproject.org
>http://collab.sakaiproject.org/mailman/listinfo/cle-release-team




More information about the cle-release-team mailing list