![]() ![]() ![]() ![]() Optionally an action may contain the windowId child tag, which defines the window identifier used to refer to the visual properties of the action window (for example, size, position, etc). The script may contain both defined actions (for example, change the status value to Closed for the Close action) and actions, which require user input (for example, get the user comment when the bug status is changed). The set tag, which defines the action script which runs when the action is applied.Action applicability can be defined either by referring to the condition defined earlier or by specifying a filter statement using the filter tag and the same syntax as is used for the condition definition. Action applicability condition, which defines which conditions a bug must meet to be eligible for the action.The name tag, which defines the name of the action shown in the UI components (for example, Workflow combo box).I think if we only want to implement this for the "reset assignee to default" case, that ought to be a separate bug (probably bug 1036834 :) ).It consists of three mandatory sub-elements: In either case, I haven't started working on the bug yet. So I want all bugs that come onto my list to get reset back to NEW, regardless of whether they came there via someone explicitly assigning them to me or via "reset assignee to default". In many installations, including mine, default assignees are actual people (many of whom share dual roles of "primary triager" and "primary developer" for the same component). b.m.o) the default assignee is a user with special meaning (e.g. No, my original request intentionally did not distinguish between your #1 and #2.īugzilla does not have any real representation of the "assignee not set" state in your table. > comment 16 seem don'#t differentiate between #1 and #2 below) - tweaking > misunderstanding of the request ( comment 4, comment 6, comment 15 and > It seems that some of the objections in this bug are due to a Note that if someone *really* wanted this state, they could manually change the status back again after using "reset assignee", or else manually set the assignee to nobody instead of using the reset feature) It seems that some of the objections in this bug are due to a misunderstanding of the request ( comment 4, comment 6, comment 15 and comment 16 seem don'#t differentiate between #1 and #2 below) - tweaking summary to be less ambiguous.ġ) I agree it is useful to have the bug status and the assignee field partially decoupled, since it allows for the "assign bug to self but only change status to IN_PROGRESS/ASSIGNED when actually working on it" workflow.Ģ) However, even with that workflow, resetting the bug to have an assignee of nobody but leaving a status of IN_PROGRESS/ASSIGNED does not make sense.Īssignee set + status:IN_PROGRESS/ASSIGNED => OKĪssignee set + status: => OKĪssignee not set + status:IN_PROGRESS/ASSIGNED => Not expected (and the subject of this bug) /Īs far as I can tell, reset_assigned_to() is called when mass-changing bugs, so my WIP in bug 1036834 should cover the mass change case too, right? ![]() I filed bug 1036834 which was duped here (there is a WIP over there as well). Maybe a bit of javascript that changes the status drop-down to NEW when you click the "edit" link next to the assignee? Although I don't like the idea of my bug triage workflow depending on whether somebody else has javascript turned on in their browser. The problem is that the current UI can't distinguish between these two cases:ġ) I know exactly what status I want the bug to have after the reassignment, and I've picked it from the status drop-down.Ģ) I don't care what status the bug has after the reassignment, and I haven't touched the status drop-down at all. I looked through the bugs in the dependency tree of bug 101179 and couldn't find any mention of this either. This was brought up way back in 2002 in bug 173341 comment 1, but that bug got resolved along with bug 92552 with no further discussion. The bug's status should be changed to NEW. Reassign a bug with status ASSIGNED, without touching the Status drop-down. So this change means that I'll no longer be able to search for NEW bugs assigned to me and find the ones that I haven't looked at yet.ġ. In my workflow, having a bug in the NEW state means that it's newly assigned to me (either b/c it's newly entered, or because it's been reassigned), and I still need to review it. In Bugzilla 3.2, reassigning a bug has no effect on the status. In Bugzilla 3.0, reassigning a bug in the ASSIGNED state changed its status to NEW. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |