Issue Details (XML | Word | Printable)

Key: JRA-15196
Type: Bug Bug
Status: Verified Verified
Priority: Trivial Trivial
Assignee: Unassigned
Reporter: Sergiy Lizenko
Votes: 0
Watchers: 0
Available Workflow Actions

Start Progress
Operations

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

Cannot filter issues with UNKNOWN reporter

Created: 04/Jul/08 12:35 PM   Updated: 07/Jul/08 04:26 AM
Component/s: Filtering & Indexing
Affects Version/s: 3.12.3
Fix Version/s: 3.13.x

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. Portlet Parameters.jpg
(29 kB)
2. Portlet results.jpg
(16 kB)
Environment: MS SQL 2000, Tomcat5
Issue Links:
Reference
 

Participants: =Neal Applebaum, Dushan Hanuska [Atlassian] and Sergiy Lizenko
Since last comment: 8 weeks, 5 days ago
Labels:


 Description  « Hide
When I select in portlet Filter Statistics issues reported by unknown reporter, it shows all issues.
See screen-shots.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Sergiy Lizenko added a comment - 04/Jul/08 12:43 PM
One more thing - inconsistency in terminology:
  • portlet shows unknown when no reporter
  • in issue navigator - Anonymous

[ Permlink | « Hide ]
=Neal Applebaum added a comment - 04/Jul/08 04:37 PM
Just curious, how are issues getting created so that the reporter is unknown? CVS import? email? soap?

[ Permlink | « Hide ]
Dushan Hanuska [Atlassian] added a comment - 06/Jul/08 10:33 PM
When fixing this, replace word 'unknown' with 'anonymous' and remove the link from it.

[ Permlink | « Hide ]
Sergiy Lizenko added a comment - 07/Jul/08 04:26 AM

how are issues getting created so that the reporter is unknown?

Neal,
These are issues imported from prev tracking system we used before.
Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13-#330) - Bug/feature request - Atlassian news - Contact Administrators