Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Issue workers assigning issues to themselves

web-app

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
bob.banks
Replies (5)
helpful
0
not helpful

Bob,

We could add a "Take this issue" link that would enable a Developer to take assignment of an issue where the issue was unassigned -- new role.  If you like this approach, then please add this issue to our Gemini install.

 


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Another thought.

Have leads (default issue assignments) at the component level.

http://gemini.countersoft.com/Default.aspx?p=2&i=583


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

While that could be helpful in some cases, it wouldn't really work for us.  When we have multiple leads they are across different disciplines (tech, creative, ux, copy) and not across components.  Thanks for the replies.  I like the "Take this issue" approach.


bob.banks
· 1
bob.banks
helpful
0
not helpful

Harvey,

Do you also think you could add an option that would automatically change the status to "Assigned" when an issue worker took the issue? 

Also in some cases, the issue maybe already assigned to another individual and for some reason that individual can't complete the tasks so another programmer takes it from them.  Given that, "Take this issue" should probably be allowed regardless of status (except for "Closed" maybe).


bob.banks
· 1
bob.banks
helpful
0
not helpful

Sure.

Raise an issue so we can track it.


Harvey Kandola
· 212
Harvey Kandola