Accepting as new issue.  Internal issue opened.

this seems to be fixed only partly. I now can search for users in IZ,
but I can't build queries with user name of two characters, I get
message: "The substring 'mh' is too short for a username search.
Username substrings should be at least 3 characters in length"

as a consequence the link "my issues" also show no results. I see this
as reason to raise prio to 2.

This has been fixed in the TR1 build.  Please verify.

steve, please reread my latest comments, "my issues" is not working
for me, because I'm a two letter user.

i reopened internal pcn 22634 with your comments.  sorry i did not 
read your comments before updating this issue.

An updated fix has been applied to RC1.  Please verify on the next 
staging server.

my issues is still not working for me, I got just one issue displayed
(9968, an issue I have nothing to do with).

reassigned.

Reassigning to Kerry
adding SEH to cc list.
louis

This issue was fixed in SourceCast RC1.  Engineering and Operations 
are currently looking at the OOo staging site to see why this still 
appears to be broken (maybe a patch didn't get applied correctly, 
etc.).  Stay tuned....

After some investigation, it looks like this is not a core product 
problem but a problem with a bad custom query.  It seems that the "my 
issues" query for mh@openoffice.org has been customized and a few 
problems introduced which is preventing the return of any query 
results:

- The only milestone being searched for is "OOo+1.0.2"

- There is nothing in the query specifying the issues to search for 
should belong to mh@openoffice.org

Using the default "my issues" query for mh@openoffice.org should work 
just fine.

I don't seem to be able to reassign this issue.  Louis, could you 
please pass it back to Martin for confirmation?  Thanks!

reassigning to mh.
louis

I don't think that the mixture of "my issues" and "default query" is
valid. There is no hint if the user save a query as default query that
this will have effect on the "my issues" link and far away from what
our users are expecting.

Understood. 

However, this is working as designed. The "my issues" link is the 
default query.  When the user selects "Remember this as the default 
query", the default query is updated the "my issues" link will run 
that query.  The user can save any query as default for the "my 
issues" link or specifically save (name) other queries to avoid 
updating the default query.

sorry, this is not consistent. the ProjectIssues clearly states: "My
Issues: View both active issues assigned to you and those you have
entered". On the Query page there is no hint that "save this as
default query" has impact to "my issues" query. I see this as a
regression, not as "work as designed"

For me the more interesting question is, whether there is an easy way
for a user to reset the default query ("My Issues") to the default.
(I hope that's not confusing :-)

The initially submitted issue "IZ users with 2 character user names
can't be searched" is fixed.
Changing title.

Our proposed solution is to change the text in the UI for updating 
the default query:

Old text:
  Remember this as the default query 

New text:
  Remember this as the default/"my issues" query

This is the best we can do to relate the two.

The resultant list already has the text "Issue list:(Default Query)" 
in the header.

There is currently no way to reset the query to default.  

This fix will be applied in the update tonight for your verification.

Brain freeze - if you alter the default query, the next time you are 
on the query page the link "Set my default query back to the system 
default" appears below the "sort by" drop down box.  So, Yes, there 
is a way to reset the query to default, just as in 1.1.3.

The update has been applied.  The new text is in place.  Please verify

verified.

close issue.