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

Key: JRA-4771
Type: New Feature New Feature
Status: Reopened Reopened
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 4
Watchers: 3
Operations

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

Search by resolver

Created: 05/Oct/04 12:10 AM   Updated: 06/Nov/07 09:32 PM
Component/s: Custom Fields, Custom Fields (new types)
Affects Version/s: 3.0 Standard Beta
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Cloners
 
Duplicate
 
Reference
 

Participants: Jeff Turner [Atlassian] and Scott Farquhar [Atlassian]
Since last comment: 187 weeks, 2 days ago
Labels:


 Description  « Hide
Various people want to be able to search by 'resolver'. From jira-user:

> Is there a way to search for a resolver of an issue?
> Our developers report for example which classes are changed by a fix and
> then assign the issue to Quality Assurance.
> Later they have to apply this fix on older versions of our program and
> would like to find again the issues they worked on.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 05/Oct/04 07:34 PM
I'm closing this as wontfix. A much better way to do this would be to index all the transition states, including the date and who performed the transition.

Jeff Turner [Atlassian] - 19/Dec/04 05:53 PM
Original suggestion is to implement this as a derived custom field (see Scott's reply).