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

Key: JRA-5740
Type: Bug Bug
Status: Closed Closed
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Ross Ryan
Votes: 0
Watchers: 0
Operations

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

How To Tell How Many Issues A Developer Has Resolved

Created: 24/Jan/05 10:51 AM   Updated: 30/Jul/06 07:34 PM
Component/s: Filtering & Indexing
Affects Version/s: 3.0.3 Professional
Fix Version/s: None

Time Tracking:
Not Specified

Environment: FreeBSD, MySQL, Tomcat
Issue Links:
Duplicate
 

Participants: Keith Brophy and Ross Ryan
Since last comment: 172 weeks ago
Resolution Date: 25/Jan/05 01:46 AM
Labels:


 Description  « Hide
I have a pretty default Jira Professional Setup.
How do I tell how many bugs a developer has Resolved?
Typically a Tester enters a bug, a developer Resolves it and then a Tester Closes/Reopens it.

So for bugs in the Resolved (Asignee = tester) & Closed (Asignee still = tester) States, how do I count how many bugs individual developers have fixed?

Many Thanks,

Ross.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Keith Brophy - 25/Jan/05 01:45 AM
Hi Ross,

At present, it is not possible to do this in JIRA. It may be possible to write a report plugin that searches through the change history and extracts the relevant data - but the change history is not indexed and hence, this search would be very slow.

Please add any further comments you may have or vote on the issue already logged under JRA-5536, which also addresses your request. I will close this issue so as we can track all information at JRA-5536 for this improvement.

Let me know if you have any further questions.

Regards,
Keith


Keith Brophy - 25/Jan/05 01:46 AM
This issue is duplicated in JRA-5536 - lets track all information at that issue.