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

Key: JRA-14687
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Claudio Valderrama C.
Votes: 0
Watchers: 0
Operations

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

More than one assignee

Created: 23/Mar/08 04:01 AM   Updated: 24/Mar/08 08:24 PM
Component/s: Project Management
Affects Version/s: 3.8.1
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Anton Mazkovoi [Atlassian] and Claudio Valderrama C.
Since last comment: 16 weeks, 4 days ago
Resolution Date: 24/Mar/08 08:24 PM
Labels:


 Description  « Hide
Hello, we at the Firebird (RDBMS) project have a special license for being an open source project.
We use the tracker to derive reports and guides for new features, including a "What's new" that's part of the documentation.
One thing we miss from time to time is to be able to have more than one assignee to a feature request (less commonly is the need to assign several people to a bug). Things are complex and/or big there and sometimes one person is not enough, but for giving due credits to anyone is easier if we track all assignees officially instead of putting one person as the official assignee and having to remember later who else worked on the same issue.
Thanks.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] - 24/Mar/08 08:24 PM
Hi Claudio,

I believe the feature request for this is JRA-1397 and therefore I will resolve this issue as a duplicate.

Please have a look at the comments on JRA-1397, which suggest several possible solutions, such as using a custom field to help keep track who is working on the issue.

Cheers,
Anton