The default bug view has changed. See this FAQ.

Feature Request: Reassign resolved bugs

RESOLVED FIXED in Bugzilla 3.2

Status

()

Bugzilla
Creating/Changing Bugs
--
enhancement
RESOLVED FIXED
14 years ago
10 years ago

People

(Reporter: Michael Soulier, Assigned: Frédéric Buclin)

Tracking

unspecified
Bugzilla 3.2

Details

(Whiteboard: [blocker will fix])

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030

Currently when a bug is resolved, you cannot reassign it for verification. A
great feature would be to permit reassignment of resolved bugs, indeed bugs in
any state. Otherwise, how do you give a bug to a particular individual for
verification, closing, etc.?

Reproducible: Always

Steps to Reproduce:
N/A
Actual Results:  
N/A

Expected Results:  
N/A
That's what the QA Contact field is for.
That said, there is merit to being able to change the assignee of a bug after
it's been resolved, and I thought there was a bug for it that I was going to
dupe this to, but I can't find it.  Guess this will be it. :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
(Assignee)

Updated

12 years ago
Target Milestone: --- → Bugzilla 2.24

Comment 3

12 years ago
WORKSFORME. use change several bugs at once, make sure one of the bugs you want to change is open and just change the one bug whose assignee you want to change :).

Updated

11 years ago
QA Contact: mattyt-bugzilla → default-qa
(Assignee)

Comment 4

11 years ago
see bug 92552
(Assignee)

Comment 5

11 years ago
*** Bug 343639 has been marked as a duplicate of this bug. ***
(Assignee)

Comment 6

11 years ago
We are in "soft freeze" mode to prepare 3.0 RC1.
Assignee: myk → create-and-change
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
(Assignee)

Updated

10 years ago
Assignee: create-and-change → LpSolit
Depends on: 92552
Whiteboard: [blocker will fix]
(Assignee)

Updated

10 years ago
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.