I am not sure if we can without severely messing with issue history. AS in the past had custom workflows, and you can only have one workflow set. The only solution that I can think of is splitting JBAS jira into an old and new project. On 4/14/11 6:01 AM, Kabir Khan wrote: > Can we enable this for JBoss AS? > > Begin forwarded message: > >> From: Randall Hauch<rhauch(a)redhat.com> >> Date: 5 April 2011 21:55:53 GMT+01:00 >> To: Kabir Khan<kabir.khan(a)jboss.com> >> Cc: The Core<thecore(a)redhat.com>, Mark Newton<mnewton(a)redhat.com> >> Subject: Re: JBoss Community announces GIT Pull Request Workflow >> >> It needs to be explicitly enabled on each JIRA project. See the last paragraph of Mark's email. >> >> On Apr 5, 2011, at 3:19 PM, Kabir Khan wrote: >> >>> I don't see this in the JBAS project? Does it need to be explicitly enabled, or am I looking in the wrong place (the options I get when clicking 'Resolve')? >>> On 24 Mar 2011, at 13:35, Mark Newton wrote: >>> >>>> Hi, >>>> >>>> The JBoss Community Team are proud to announce the availability of the "GIT Pull Request Workflow" in our JIRA instance (http://issues.jboss.org). >>>> >>>> This workflow may be a good choice for projects that want to use better GIT Pull Requests tracking. >>>> >>>> It adds a new step called "Pull Request Sent" into the workflow indicating that work was done for given issue and a pull request has been prepared to be applied into the upstream GIT repository. The "Link Pull Request" action allows a transition to this new step with the possibility to insert a pull request URL into a newly introduced custom field called "Git Pull Request". The issue is then Resolved after the GIT pull request is applied upstream. >>>> >>>> Special thanks go to Dan Allen who came up with the idea and the first version of the workflow for the Seam project. Thanks also go to Lukas Fryc who pointed our team to Dan's workflow and initiated the generalization (he now uses it for the ARQAJO and ARQRUSH projects). The current version of the workflow is slightly improved and generalized to be applicable for other projects too: >>>> >>>> https://issues.jboss.org/browse/ORG-973 >>>> >>>> To use this new workflow your jira project must be switched to use "GIT Pull Request workflow scheme". Project Leads can contact the JBoss Community Team by emailing eng-ops(a)redhat.com to create a ticket to perform this change if they can't do it themselves. >>>> >>>> Enjoy! >>>> >>>> Mark Newton >>>> JBoss Community Lead >>>> Mobile: +41 7657 47730 >>>> Office: +41 41 760 4636 >>>> Email: mnewton(a)redhat.com >>>> >>> >>> >> >> > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

The old "JEMS" workflow. It had special states like "support patch" On 4/15/11 2:00 AM, Dimitris Andreadis wrote: > What the existing workflow does? And what are the implications of changing workflow? > > On 14/04/2011 16:30, Jason T. Greene wrote: >> I am not sure if we can without severely messing with issue history. AS >> in the past had custom workflows, and you can only have one workflow >> set. The only solution that I can think of is splitting JBAS jira into >> an old and new project. >> >> On 4/14/11 6:01 AM, Kabir Khan wrote: >>> Can we enable this for JBoss AS? >>> >>> Begin forwarded message: >>> >>>> From: Randall Hauch<rhauch(a)redhat.com> >>>> Date: 5 April 2011 21:55:53 GMT+01:00 >>>> To: Kabir Khan<kabir.khan(a)jboss.com> >>>> Cc: The Core<thecore(a)redhat.com>, Mark Newton<mnewton(a)redhat.com> >>>> Subject: Re: JBoss Community announces GIT Pull Request Workflow >>>> >>>> It needs to be explicitly enabled on each JIRA project. See the last paragraph of Mark's email. >>>> >>>> On Apr 5, 2011, at 3:19 PM, Kabir Khan wrote: >>>> >>>>> I don't see this in the JBAS project? Does it need to be explicitly enabled, or am I looking in the wrong place (the options I get when clicking 'Resolve')? >>>>> On 24 Mar 2011, at 13:35, Mark Newton wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The JBoss Community Team are proud to announce the availability of the "GIT Pull Request Workflow" in our JIRA instance (http://issues.jboss.org). >>>>>> >>>>>> This workflow may be a good choice for projects that want to use better GIT Pull Requests tracking. >>>>>> >>>>>> It adds a new step called "Pull Request Sent" into the workflow indicating that work was done for given issue and a pull request has been prepared to be applied into the upstream GIT repository. The "Link Pull Request" action allows a transition to this new step with the possibility to insert a pull request URL into a newly introduced custom field called "Git Pull Request". The issue is then Resolved after the GIT pull request is applied upstream. >>>>>> >>>>>> Special thanks go to Dan Allen who came up with the idea and the first version of the workflow for the Seam project. Thanks also go to Lukas Fryc who pointed our team to Dan's workflow and initiated the generalization (he now uses it for the ARQAJO and ARQRUSH projects). The current version of the workflow is slightly improved and generalized to be applicable for other projects too: >>>>>> >>>>>> https://issues.jboss.org/browse/ORG-973 >>>>>> >>>>>> To use this new workflow your jira project must be switched to use "GIT Pull Request workflow scheme". Project Leads can contact the JBoss Community Team by emailing eng-ops(a)redhat.com to create a ticket to perform this change if they can't do it themselves. >>>>>> >>>>>> Enjoy! >>>>>> >>>>>> Mark Newton >>>>>> JBoss Community Lead >>>>>> Mobile: +41 7657 47730 >>>>>> Office: +41 41 760 4636 >>>>>> Email: mnewton(a)redhat.com >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> >