[cle-release-team] Extra resolved status in JIRA: Patch Ready

Neal Caidin nealcaidin at sakaifoundation.org
Mon Mar 25 07:05:07 PDT 2013


Hi Aaron,

Would it be desirable to be able to filter on patches in Jira regardless of the state of the workflow? For #1, I'm assuming that "Patch Ready" or "Ready for Review" are only temporary resolutions until after the patch is reviewed and merged? Then the resolution would go to one of the current standards (e.g Fixed, Won't Fix, etc)?

-- Neal


On Mar 25, 2013, at 7:54 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> Hey all,
> I think we should maybe look at putting in a new resolution in JIRA to
> make it easier to keep track of patches (and remove the "contributed
> patch" type).
> 
> I think there is a lot of confusion about the right way to handle this
> right now (use the type, resolve the issue or leave it open, put in
> comments or labels, etc.). The Contributed Patch type is confusing
> because often there are patches contributed on tickets which are
> already bugs or features and changing them over at that point is not a
> good idea and requires admin access.
> The resolution would allow us to put a ticket into a state that
> clearly indicates there is a patch which is waiting for someone to
> look at it. Options I can think of:
> 1) Add "Patch Ready" or "Ready for Review" or something like that Resolution
> 2) Add a new step to the workflow between Open and Resolved (but I
> think this might be harder to understand and easier to miss)
> 3) ????
> 
> Thoughts?
> -AZ
> 
> 
> -- 
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> 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