History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-1802
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Minor Minor
Assignee: Unassigned
Reporter: Kristof Van Cleemput
Votes: 17
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
JIRA

assign issue to multiple developers

Created: 05/Jun/03 01:51 AM   Updated: 07/Jun/06 11:31 PM
Component/s: Issue Fields
Affects Version/s: 2.2 Pro
Fix Version/s: None

Time Tracking:
Not Specified

Environment: JIRA
Issue Links:
Duplicate
Reference
 

Participants: Erwin Achermann, JC, Jeff Turner [Atlassian], Kristof Van Cleemput, Lars Kühne, Mark Chaimungkalanont [Atlassian] and Tiscali Tiscali
Since last comment: 111 weeks, 3 days ago
Resolution Date: 25/Dec/05 01:22 AM
Labels:


 Description  « Hide
First of all : I made a mistake with my previous isue CORE-4 (it should be in JIRA not in the CORE I suppose). It has nothing to do with this one but it's only fair to mention it.(Sorry)

I want to assign an issue to more then 1 person (we use extreme programming => we work in pairs).
If an issue is created I need to create a second one and link it to the first one (there identical).

Seems a bit overkill doesn't it.

So my proposition is to make the assignee a collection, that way you can assign as many people to an issue as you want.

Also need the ability to delete a person from the assignee list + if it's the last one on the list allow it and set unknown.

Regards

Kristof



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Lars Kühne - 10/Jul/03 06:50 AM
seems to be very similar to JRA-1397

Jeff Turner [Atlassian] - 22/Aug/04 06:11 PM
This has been discussed a couple of times on the jira-user list:

http://forums.atlassian.com/thread.jspa?forumID=46&threadID=3447&messageID=80494719#80494719

So what are people specifically after when they ask for multiple assignees? Could it be achieved in some other way with JIRA? Please add comments here.


Erwin Achermann - 23/Aug/04 01:15 AM
It may be true that with future features the need for multiple assignments will fade, but not vanish. In our case e.g. we would like to use it to add a personal todo item to several assignees at once. So in fact it would duplicate the issue for each of the multiple assignee. The generated Issues at the end still have just one assignee.

Jeff Turner [Atlassian] - 23/Aug/04 01:29 AM
Erwin,

There will be a 'clone issue' in JIRA 3.0 which hopefully will meet this need.


Jeff Turner [Atlassian] - 25/Aug/04 07:19 PM
I think this is pretty much the same as asking for "assign to group", or "assign to multiple developers", so I'll close this as a duplicate. Please add comments to JRA-1802. Thanks.

Tiscali Tiscali - 15/Dec/04 05:59 AM
Develop this improvement is important because of the security limitation. Right now you can set the issue security level at Reporter level or Assignee level, this allow to use the security level dynamically, only for Reporter and Assingee. This is not true for groups, you have to specify groups name for each security level. If the group assignment will be implemented, the security level become dynamic also for groups

This duplicates JRA-1397 (and may be obselete for 3.4), please add any further comments there

JC - 31/May/06 02:01 AM
I would argue that this issue is not a duplicate of JRA-1397 because that issue only enables multiple users to be assigned to an issue as part of a notification scheme via custom fields.

Why can' t this same custom field be provided to enable a group or multiple users ASSIGNED directly to an issue? We have a major need for this as we have aup to four teams working with a project lead at any one time and in many cases the project lead will need to assign the same task brief to two users - one user may implement on set of programming whilst another one works on the same task brief but using a different set of programming.

Despite all its drawbacks one of the main benefits of Dotproject was how easy it was to assing multiple users to one task and set notifications as as a group notification or for individuals. When multiple individuals logged time against the same task DP would recognise each user and record it against

I vote to reopen this and explore the options available through the custom field picker - can we enable this to load under the Assign to dropdown as an optional mutli-user list?