516278 - Editing a tabular report involving a user field (reporter, assignee, QA contact) ignores the user field

Status: NEW

(Bugzilla :: Reporting/Charting, defect)

Description

[Erik Magana]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: 

When trying to edit the search on the results of a tabular report, if one of the parameters, used to filter the report, is "reporter", "assigned_to", or "qa_contact"; the edit search form does not load those parameters into the form and so when the search is conducted those parameters are no longer applied. 

View comment #6 from bug 281503, where the feedback is that the edit field is broken. 

Reproducible: Always




Possibly add those parameters to the boolean section

Comment 1

[Frédéric Buclin]

Please stop reporting the same bug again and again. We know about bug 281503. And you already filed bug 515694.

Comment 2

[Erik Magana]

Frederic,

Why is this considered a duplicate of bug 281503. The issue described in that bug revolves around incorrect bug data displaying from a tabular report, that issue was fixed in august 2005. Although it was not applied becuase another issue was reported to still be broken, a seperate issue having to deal with the "edit search" piece of the form. 

I strongly feel that that issue comment #6 is a seperate issue from the originally filed issue and as such deserves its own bug number, this bug which i have filed. 

If you feel that this should not be the case please explain to me why. The issue itself still exists with or without the august 2005 patch, AND it applies not only to the "qa_contact", but the "reporter" and "assigned_to" person as well.

Comment 3

[Erik Magana]

This is the original description of the other bug. Please note that no where does it describe or mention any break in the functionality of the "Edit Search" link. The bug 516278, which i have filed is in respect to the "Edit Search" link being broken whenever parameters are used that cannot be represented in the advanced search form, such as reporter, qa_contact, and assigned_to

I believe bug 281503 can be closed out and resolved with the changes supplied by the august 2005 patch. This bug however still exists seperate of bug 281503

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
> Gecko/20040113
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
> Gecko/20040113
> If you generate a tabular report and use QA Contact as the Virtical axis, and
> then click the URL for a cell in the table, the resulting bug report isn't for
> that cell, but for the totals column.
> For example, look at this tabular report:
> https://bugzilla.mozilla.org/report.cgi?x_axis_field=&y_axis_field=qa_contact&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Bugzilla&target_milestone=Bugzilla+2.18&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=
> it is a tabular report against all target milestones of Bugzilla 2.18 that are
> resolved, and have the QC contact as the virtical axis.  If you follow the URL
> for the first cell (for default-qa @ bugzilla.bugs), you should go to a bug
> list
> showing only 4 bugs (currently).  Instead, you go to a bug list showing 1095
> bugs, which happens to be the total bugs applicable to the original query.
> Here's another example:
> https://bugzilla.mozilla.org/report.cgi?x_axis_field=qa_contact&y_axis_field=bug_severity&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Bugzilla&target_milestone=Bugzilla+2.18&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=
> This is a similar report to the previous one, the only difference being that
> the
> virtical axis is now Severity, and QA Contact has been moved to the horizontal
> axis.  Again, when you click on a cell's URL, you don't go to the bug list for
> that cell, but for the totals of that row.
> This bug might be related to a similar bug I've raised: bug 279590.
> Reproducible: Always

Comment 4

[Frédéric Buclin]

(In reply to comment #0)
> When trying to edit the search on the results of a tabular report, if one of
> the parameters, used to filter the report, is "reporter", "assigned_to", or
> "qa_contact"; the edit search form does not load those parameters into the form

What kind of filter are you talking about? These fields are working fine.

Comment 5

[Erik Magana]

An example is if you create a tabular report, using assigned_to as an axis field, and status as the other axis field. Once you run the report you'll select a specific instance of the data points. This will give you a short bug list filtered by the selected assigned_to and status. If you then click on "Edit Search" you are navigated to the Advanced Search form where the Status is preselected based on the value that was used to create the short list; however the assigned_to value is neither in the emailassgined_to section or the boolean parameter section. 

At this point if you click on search, without making any modifications you will get a bug list that consists of only the bugs for that particular status and the assigned_to is not filtered out. 

In the URL string you find info like field-1-0-0=assigned_to (respectively), but as you are probably aware in order to have it in the boolean section it must be field1-0-0=assigned_to.

Please let me know if you need more detailed specifications, and I will generate the requested information. I noticed this only happens with the reporter, assigned_to and qa_contact parameters.

Comment 6

[Frédéric Buclin]

The problem still exists in 4.5.