Issue workers assigning issues to themselves
In my organization, we assign issues a few different ways dependent on the project lead. Some leads choose to have all new issues left unassigned on creation. Those types of leads, of which I am, allow the developers to pick issues from the unassigned list that they can handle, while keeping an eye on the unassigned queue through email notifications, etc. On the flip side, other leads ask that all new issues are assigned to the lead and the lead then assigns the issue to a developer to complete. Too much overhead for my style.
I can easily see how the 2nd scenario would work with Gemini. I'm not so sure about the first. I wouldn't necessarily want the developer to have "Edit Issue" permission, but I don't see any other way to allow them to change the "Assigned To" field. In this scenario, it also would be nice if the "Assigned To" was on the
View Issue page along with the editable status and resolution
drop-downs.
Another option would be to have a LinkButton that would "take the issue". That way, they couldn't assign another resource to the issue; they could only assign the issue to themselves.
Thoughts?
bob.banks
· 1 |
|
Wednesday, January 18, 2006, 5:46:30 PM |