Feature #9314: Filtering query with statement condition not mantain sort criteria - Redmine

Actions

Copy link

Feature #9314

closed

Filtering query with statement condition not mantain sort criteria

Added by pasquale [:dedalus] about 13 years ago. Updated over 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

My page

Target version:

Start date:

2011-09-23

Due date:

% Done:

Estimated time:

Resolution:

Fixed

Description

I want to change _issuesassignedtome block.
I want to display as _issuesassignedtome the first 10 records of one public query.
Simply I use Redmine classes as above:

custom_developer_query = Query.find_by_name(query_sorted_by_priority_and_custom_value) issues_to_you = Issue.visible.open.find(:all, :conditions => custom_developer_query.statement, :limit => 10, :include => [ :status, :project, :tracker, :priority ])

I have 10 records ordered by priority but not for custom field...

Related issues

Actions

Copy link

Updated by Etienne Massip about 13 years ago

Category changed from Search engine to My page

Actions

Copy link

Updated by pasquale [:dedalus] about 13 years ago

I think that the problem is that the :order directive can't use properly the query.sort_criteria; for example from my previous post, if I add the line :order => custom_developer_query.sort_criteria as above and where sort_criteria is "prioritydesccf_10asc" (as is returned quering custom_developer_query.sort_criteria)

custom_developer_query = Query.find_by_name(query_sorted_by_priority_and_custom_value)
issues_to_you = Issue.visible.open.find(:all,
:conditions => custom_developer_query.statement,
:limit => 10,
:order => custom_developer_query.sort_criteria,
:include => [ :status, :project, :tracker, :priority ])

Probably for better reflect this issue the title should be changed into "Cannot use query sort_criteria into :order directive"

Actions

Copy link