Am 12.03.2013 11:53, schrieb Lev A. Stejngardt:
Dear Developers,
we had these *five* original statuses:
* unread (initial state; ticket just created without an owner)
* open (ticket has an owner; if you assign a ticket to an owner, use
this state)
* open-accepted (ticket was accepted by owner and s/he's working on it)
* pending-fixed (task is done but needs a verification by someone)
* closed-fixed (ticket was verified and the task is done)
In addition, we had special statuses but these were not available at
SF so we didn't assign them:
I remember myself to assign such statuses ....
* wontfix (could be 'pending-wont-fix'; but I think it's more like
"I'm the owner but I won't fix it" so it's like 'unread')
Wontfix = Defect in a 3rd party library that is no longer be maintained
or the 3rd party library does not offer methods
to fix the bug != "I'm the owner but I won't fix it" .... well yes
.... what the fuck oO
* rejected (could be 'pending-rejected'; same as wontfix)
Rejected is not the same was wontfix ... I mostly use this field if
someone thinks he has spotted a bug ... but
it turns out that the bug is not a bug ... the user thinks that Saros
should do something that is not implemented nor
specified = Feature request
BR,
Stefan
* outofdated (could be 'closed-out-of-date')
* duplicate (could be 'closed-duplicate')
I'm note sure whether we need all available statuses.
BR Lev
2013/3/12 Zieris, Franz <franz.zie...@fu-berlin.de
<mailto:franz.zie...@fu-berlin.de>>
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
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
