Roundup Tracker - Issues

Issue 667881

classification
Adding 'take' into index for unassigned issues
Type: rfe Severity: normal
Components: Interface Versions:
process
Status: closed fixed
:
: richard : htgoebel, jkew, richard
Priority: normal :

Created on 2003-01-14 17:51 by htgoebel, last changed 2003-09-18 23:42 by richard.

Messages
msg3131 Author: [hidden] (htgoebel) Date: 2003-01-14 17:51
The issue-index currently lacks a "take" action for
unassigned issues. The idea is to simple put a "take"
into the column of 'Assinged To' if an issue is
unassigned. Clicking on this link is a very easy way
get this issue assign to the loged in user.

Simply place this into issue.index (patch included):

   <td tal:condition="request/show/assignedto">
     <span tal:condition="i/assignedto"
tal:replace="i/assignedto" />
     <a    tal:condition="not:i/assignedto/plain"
           tal:attributes="href
string:issue${i/id}?:action=edit&assignedto=${request/user/id}">--
take --
     </a>
   </td>
msg3132 Author: [hidden] (richard) Date: 2003-01-14 20:45
Logged In: YES 
user_id=6405

That's a nice idea - but I think I'll include it as an example rather than have it 
implemented by default. I'll leave this issue open for a while to see if there's 
any other feedback though... 
 
msg3133 Author: [hidden] (jkew) Date: 2003-02-03 10:40
Logged In: YES 
user_id=598066

-1 on changing default templates, for three reasons:

1) I wouldn't want to take an issue without examining 
the full text and fields of the issue!

2) It's a slippery slope from there to also 
having "resolve" or "reject" links in the issue-index 
view -- all these are actions which rightly belong on the 
issue page itself, not on a multiple-issues overview 
page.

3) It also makes all issue views specific to "developer" 
users: I also have "manager" users who view the issues, 
are nosy on some of them, but will never want to take 
them on. Adding a "take" link on their issue lists just 
clutters the interface and reduces the real estate 
available for useful information.

Agree though it'd make a good customisation example -
- maybe even one which could be extended to consider 
user Roles.
msg3134 Author: [hidden] (richard) Date: 2003-09-18 23:42
Logged In: YES 
user_id=6405

added as an example in customisation doc.
History
Date User Action Args
2003-01-14 17:51:48htgoebelcreate