Vote for sticking with standard workflow. -- justin On Aug 26, 2015 12:05 PM, "Ivan Zhakov" <[email protected]> wrote:
> On 26 August 2015 at 18:48, Bert Huijben <[email protected]> wrote: > > Ivan, > > > > An initial (test?) import has been completed. See > https://issues.apache.org/jira/browse/SERF/ > > > I see. It's only test import. I've already installed test JIRA on VM > and improved my conversion program. > > The first question what workflow we're going to use. Google Code we > have the following statuses: > [[ > New > Fixed > WontFix > Accepted > Started > Invalid > Verified > Done > Duplicate > ]] > > While JIRA is very flexible and could adapted to any workflow I'm > inclined to choose simple way and map all these statuses to "OPEN" and > "RESOLVED": > [[ > case "New": > return "OPEN"; > case "Fixed": > return "CLOSED"; > case "WontFix": > return "CLOSED"; > case "Accepted": > return "OPEN"; > case "Started": > return "OPEN"; > case "Invalid": > return "CLOSED"; > case "Verified": > return "CLOSED"; > case "Done": > return "CLOSED"; > case "Duplicate": > return "CLOSED"; > ]]] > > Please note that CLOSED issues cannot be edited. > > With the different "resolutions": > [[[ > case "Fixed": return "Fixed"; > case "Invalid": return "Invalid"; > case "WontFix": return "Won't Fix"; > case "Duplicate": return "Duplicate"; > case "New": > case "Started": > case "Accepted": > return ""; > case "REMIND": return "REMIND"; > case "Verified": > return "Fixed"; > case "Done": > return "Fixed"; > ]]] > > Does it make sense or we want to customize JIRA workflow to match Google > Code? > > -- > Ivan Zhakov > > -- > You received this message because you are subscribed to the Google Groups > "Serf Development List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/serf-dev. > For more options, visit https://groups.google.com/d/optout. >
