Incorrect or missing tracking flags on search results in REST API

REOPENED
Assigned to

Status

()

REOPENED
27 days ago
3 days ago

People

(Reporter: dylan, Assigned: dylan)

Tracking

Production

Details

Attachments

(1 attachment)

Created attachment 9026429 [details] [review]
GitHub Pull Request

:glob mentioned a user was seeing strange results when searching for multiple bugs.

The behavior is wrong or missing tracking flags. Yet if you search for a single bug, the tracking flags are correct. This lead me to believe it's a bug in Bugzilla->active_custom_fields and that appears to be the case.
(Assignee)

Updated

27 days ago
Summary: Incorrect or missing track flags on search results → Incorrect or missing tracking flags on search results in REST API
(Assignee)

Updated

27 days ago
Status: NEW → RESOLVED
Last Resolved: 27 days ago
Resolution: --- → FIXED
That was quick. Thanks!

When do you think this be deployed?
(Assignee)

Comment 2

27 days ago
The deployment bug is filed, and we're hoping today
(Assignee)

Comment 4

26 days ago
This has to be backed out due to memory usage problems
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I've noticed the problem with fields which are not tracking flags too. The 'flags' field for example. cf_backlog too, but I guess this one is the same as tracking flags?
(In reply to Marco Castelluccio [:marco] from comment #5)
> I've noticed the problem with fields which are not tracking flags too. The
> 'flags' field for example. cf_backlog too, but I guess this one is the same
> as tracking flags?

yes, cf_backlog is implemented as a tracking flag.
You need to log in before you can comment on or make changes to this bug.