Hi all, Our migration to our new, improved JIRA Workflow is now complete!
So, DSpace JIRA now uses the new workflow diagrammed on this page: https://wiki.duraspace.org/display/DSPACE/JIRA+Workflow+Improvements After the migration, I was able to automate the cleanup of some tickets. However, we currently have a "Received" backlog of 302 tickets (which are a mixture of old, possibly obsolete tickets & brand new ones). https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DS+AND+status+%3D+Received+ORDER+BY+key+ASC%2C+priority+DESC As mentioned, this is the JIRA backlog we'll need to dig through manually little-by-little. I'll start this discussion with the Committers at tomorrow's IRC DSpace Developer Meeting (at 20:00UTC in #duraspace IRC if anyone wishes to join). - Tim On 1/8/2013 1:01 PM, Tim Donohue wrote: > Developers & DCAT members, > > This week, I've been working (behind the scenes) on making the > previously approved DSpace JIRA Workflow changes happen: > > https://wiki.duraspace.org/display/DSPACE/JIRA+Workflow+Improvements > > Here's where things stand so far & what the end result will look like. > (I'm giving a lot of details here...no need to understand it all. It's > just here for those who may be interested.) > > 1) COMPLETED: Setup new workflow in JIRA (NOTE: I ended up slightly > renaming a few statuses in the workflow. The latest status names are now > on the Wiki page above.) > > 2) TODO (later today): Enable new workflow & migrate all existing DSpace > JIRA Tickets to new statuses. This will involve migrating the following > ticket statuses which no longer exist in the new workflow: > * 205 "Open" tickets -> revert back to "Received" stage, so they > can be recategorized manually. > * 2 "In Progress" tickets -> move to the new "Accepted" stage > * 2 "Re-Opened" tickets -> move to the new "Accepted" stage > * 627 "Resolved" tickets -> move to "Closed" stage > > 3) TODO (ongoing cleanup): After the migration, we will be left with a > total of 418 tickets (205 "Open" plus 213 "Received") which will be in > the "Received" stage. This set of tickets is essentially our "JIRA > backlog". Most of these tickets will need to be manually (re-)reviewed > in order to determine the appropriate status for each ticket, likely > either: > * "Volunteer Needed" (if ticket is ready to work on, but needs a > volunteer) > * "More Details Needed" (if ticket needs more details) > * "Accepted" (if ticket is already assigned to someone -> I may > be able to locate & move these tickets in bulk) > * "Closed" (if ticket now obsolete) > > > My plan is to actually implement the initial migration (Step #2 above) > later today. (Note for developers: I will be temporarily turning off > JIRA email notifications in order to avoid spamming everyone on > dspace-devel. I'll re-enable those email notifications after the bulk > migration work is completed.) > > After that, Step #3 may take some time. I'll automate what is possible > to automate. But, the manual review process may take weeks or months to > work through the backlog of tickets. I plan to talk to the Committers in > our meeting tomorrow about how we'd like to try and tackle this manual > review process (and whether we can write up a "guide/script" so that > DCAT members or other volunteers can chip in during their free time). > > If there are any questions or concerns, feel free to let me know. I'll > send another email once the migration is completed & the cleanup work > can begin. > > - Tim > > ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
