moving to component www

reassigning to support

Just wanting to know more on this. Issuezilla provides many filters or options 
for the queries. By using those filters , we can get effective and expected  
results. How the 'select count' option adds value to issue tracker? 

Thanks,
Priya

Hi Priya,

have a look at http://qa.openoffice.org/iz_statistic.html
This html page is the output of the queries which I do every monday to get the
project status of each project on OpenOffice.org. Each number is based on a
single query.
The only way to get the numbers is to do a query which displays all its issues.
The issue count of these queries is at the end of each single query. Therefor a
html page has to be rendered by IssueTracker for each query.

This is an expensive job...

 Some of the queries have more than 4000 issues. The only thing needed is just
the count of the issues  - not the issues itself. Doing a 'select count' instead
of a 'select' would be much faster because the html rendering isn't needed in
this case. A good side effect would be that less resources are needed to create
such a statistic.

What I want is to have a "Display only the count" checkbox on the query page
which does the following on the database (this is just some example which has
been used in http://www.bugzilla.org/queries.html):

    SELECT count(ba.bug_id) AS confirmsum, p.login_name FROM profiles p,
bugs_activity ba WHERE ba.fieldid=29 AND ba.oldvalue="UNCONFIRMED" AND
ba.who=p.userid GROUP BY p.login_name ORDER by confirmsum INTO OUTFILE
"/tmp/blah3"; 

I hope Joost's explanations help...

Have filed an internal request for the Feature to be added

Time Frame : Will update the Response fo Engineers as & when posted in internal 
query

-Mohan

Updating whiteboard.

Here is the update from the product management:

"As the user to try getting the same statistics from the reports section 
of IZ in 2.6.2.  I think that they will find that they can get this 
information already.  Queries are used for getting the actual values in issues 
and reports are used to get counts of issues that meet a certain criteria.  
What is being asked for is the latter and I beleive that we have it already."

Please try using the report for this request.
http://collabtest.openoffice.org/issues/reports.cgi 

JA: unfortunately the query engine of the reports isn't sufficient for my
statistics where i eg need to query for keywords

.

JA->ST: this issue isn't fixed. One of the statistics which I have to do for the
OpenOffice.org project is to give the overall total number of fixed issues. It
would be sufficent to have a query which gives this number only. It would be
even better to have a checkbox within the query page which allows to do a SELECT
COUNT(xyz) on database side. The added feature on the collabtest site doesn't
help. Could you please take care of this issue as I do not want to always bump
against maximum row settings within the query engine of IssueTracker ?
Reassigned to you. Please discuss this with Collab.net

re-open issue and try to reassign to st@openoffice.org

try to reassign to st@openoffice.org

try to reset resolution to FIXED

JA: hmmm... I wanted to have this reopened....

Hi, reports are very helpful but can't provide numbers for queries with criteria
beyond column/row fields and combinations thereof.
With some queries we are hitting the max_query_resultsconfiguration options and
we have to increase this value despite better knowledge.

st,

I have updated the engineers with your comments.I will get back to you as soon
as I get any updates from them.

Regards,
Karishma
Support Operations

The product management team is looking into the possibilities of the requested
enhancement. Will keep you updated as and when we have a substantial update
regarding this.

Regards,
Jeeva
Support Operations

To CRM

Hi,

Accepted the case and working on it.

Thanks,
Pritha
Support Operations.

Hi,

We are discussing on this internally. Will update you with the concrete
information ASAP.

Thanks,
Pritha
Support Operations.

This particular feature request is already possible with Project Tracker  -
reports . Hence moving this issue to Resolved Later queue .

CollabNet Support is currently reviewing the issues under Resolved-Later. If the
issues are fixed currently in any of the present CEE releases, then it will be
marked as Resolved-Fixed.

There might be a few issues which might not be in our future roadmap which might
be closed as Wontfix unless it does not lie under any custom request.

This is available in PT, Marking it as fixed.