Hi Andy. > It's always possible to switch to a different workflow
I have read some of the Jira documentation pages under [0]. Currently I think the easiest way would be for you to export the current workflow as an XML [1] and contribute it somewhere into Docs project git repo. Then we can use Gerrit to contribute alternative workflows which you can import. I hope no big changes to buttons [2] will be needed. > as long as you have a mapping of current states to new flow states > and there's a valid transition mechanism to get there. Looking at Jira community answer [3], no machine-friendly way is used to define this. But I guess we can describe the mapping by adding XML comments to the new workflow definition. Vratko. [0] https://confluence.atlassian.com/adminjiraserver071/configuring-projects-802592363.html [1] https://confluence.atlassian.com/adminjiraserver071/using-xml-to-create-a-workflow-802592824.html [2] https://confluence.atlassian.com/adminjiraserver071/advanced-workflow-configuration-802592741.html#Advancedworkflowconfiguration-customisingtransitionsonviewissue [3] https://community.atlassian.com/t5/Jira-questions/how-to-migrate-issues-to-a-new-custom-workflow/qaq-p/68037 -----Original Message----- From: Andrew Grimberg [mailto:[email protected]] Sent: 28 September, 2017 21:23 To: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) <[email protected]>; Daniel Farrell <[email protected]>; OpenDaylight Discuss <[email protected]>; [email protected]; OpenDaylight Dev <[email protected]> Subject: Re: [OpenDaylight Discuss] The long awaited JIRA On 09/28/2017 10:58 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: >> Hovering over > > Thanks, it forgot hovering could do something. :) > >>> then extended with the few extra state transitions our Bugzilla has in play. > > So someone has decided > what the state and button names would be? > Can we propose better names? I'm open to suggestions from the community. The states that were added by me specifically are the 'In Review' and 'Verified' states as those are not standard BZ states and were added at the communities request. The rest of the workflow is what I got from Atlassian, but all of the naming is changeable. Alternatively, if any projects want to switch to the more 'standard' JIRA workflows we can do that either during the final import or after the fact. It's always possible to switch to a different workflow as long as you have a mapping of current states to new flow states and there's a valid transition mechanism to get there. -Andy- -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation _______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
