Dear Developers, I just stumbled upon the incredible long list of possible "status" values for our bug tracker entries. A few weeks ago -- right after the upgrade of the SF project environment -- we had like *six* options (Leo, do you recall the original statuses?), which were quite easy to arrange as a workflow.
However, we currently have no less than the following *twenty-three* statuses: * unread * open * open-accepted * open-fixed * open-later * open-out-of-date * open-remind * open-wont-fix * open-works-for-me * pending-fixed * pending-wont-fix * pending-rejected * pending-remind * closed * closed-accepted * closed-duplicate * closed-fixed * closed-invalid * closed-out-of-date * closed-rejected * closed-remind * closed-wont-fix * closed-works-for-me Does anyone recall any interaction with the SF support or our SF project itself that might have resulted in this utter nonsense? Anyway, we need to get rid of this. I see a major challenge in mapping the current statuses of our existing entries onto new, comprehensive statuses. Leo: Do you think, you could handle this? Best Regards, Franz ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
