On 2009-02-20, Bruce Atherton wrote:
> Since the workflow is now configurable, presumably that means that we
> can define new states.
I asked the bugzilla admin whether that would be possible.
> Could we ask the admin to change all assigned to a custom state and
> then reset the email addresses
Since the workflow is now configurable, presumably that means that we
can define new states. If so, why couldn't we create our own state
(WORKINGON or something) to indicate that someone is tackling the bug
without changing the email address?
Could we ask the admin to change all assigned to a
On 2009-02-20, Stefan Bodewig wrote:
> From our nice Bugzilla admin:
>> I would like to go further and remove the ASSIGNED status
>> completely. If this will cause your project any issues, please let
>> bugzilla-admin know.
I will notify them about our discussion and follow up after we've come
On 2009-02-20, wrote:
> Another discussion could be migrating to Jira.
Yes, a completely different discussion.
> BTW where can I see the defined workflows in BugZilla + Jira?
No idea, sorry.
Stefan
-
To unsubscribe, e-mail:
>We do use the ASSIGNED feature and I guess it may be more difficult to
>say "I work on this" without it. I do understand the "notification
>mail is changed" problem, so maybe removing ASSIGNED is the right
>thing to do.
>
>We should talk about how we could change our workflow and maybe even
>ask
from our nice Bugzilla admin
> Bugzilla has been upgraded to 3.2.2. Of the several new features,
> the most significant is that the workflow is now configurable.
>
> I have taken the opportunity to remove ASSIGNED from the possible
> states that a bug may transition to. The reason for this is tha
