Defect #5385
closed
Status filter should show statuses related to project trackers only
Added by Bo Hansen about 14 years ago.
Updated almost 7 years ago.
Description
Using 0.9.3 I define a project to use only an issue tracker without the usual "new, assigned, ..." issue statuses. However when I create a filter on the issue status field I'm still presented with a list of both my new statuses but also the usual ones.
Thanks for a great project!
Best regards,
Bo
Ruby version 1.8.7 (i686-linux)
RubyGems version 1.3.1
Rack version 1.0
Rails version 2.3.5
Active Record version 2.3.5
Active Resource version 2.3.5
Action Mailer version 2.3.5
Active Support version 2.3.5
Edge Rails revision unknown
Application root /home/redmine/redmine-0.9.3
Environment development
Database adapter mysql
Database schema version 0
About your Redmine plugins
Stuff To Do Plugin 0.4.0
Redmine Question plugin 0.3.0
Timesheet Plugin 0.6.0
Files
Could you attach screenshots of Administration - Statuses and the Filter page with statuses dropdown open?
Reread our defect report. I don't think this is a defect. If those statuses are defined in the system they should be possible to filter on. This is because you may save an filter that finds issues in all projects (or all subprojects).
I think this is as it is intended.
Still if you are creating a filter while standing in a subproject I think it would be cleaner if only the issue statuses of the available trackers for this particular project. Especially if you have users only having access to this particular project. Then it would be nice if they are not bothered with a bunch of issue statuses they never use.
I understand about the global filters. In that case it should definitely show all issue statuses.
May i suggest a change to Feature Request on this one, since i agree that it would be nice.
Turned out that Query.rb already selects trackers available per project and subprojects. The attached patch utilizes this information and thus the global filtering issue is also taken care of.
Are there any plans to include this patch in a future release?
It would be nice to include this fix in Redmine 3.1.2 or 3.2.
Attached is a patch (slightly different, but works) for Redmine 3.x, as the code of the previously attached patch became a bit old, and that part was moved from query.rb to issue_query.rb in more recent versions of Redmine.
- Target version set to Candidate for next major release
- Related to Feature #7703: In issue filtering view, only allow issue status selections which are available in the current project added
- Related to deleted (Feature #7703: In issue filtering view, only allow issue status selections which are available in the current project)
- Has duplicate Feature #7703: In issue filtering view, only allow issue status selections which are available in the current project added
+10
any chance to plan this sooner than next major?
- Has duplicate Defect #10647: Other projects statuses show up at pull down list on issue filtering added
Here is an updated patch that restricts the statuses in the issue filter only to the statuses used by the current project and its subprojects. For the global issues page, all statuses are listed in the filter.
I think we should change the current behaviour (which lists all the statuses regardless the project) for the following reasons:
- consistency: with tracker and custom fields behaviour (#25501#note-4)
- privacy: for example, in our instance, we have some internal projects with multiple statuses (not related to our development workflow) that we don't want to be visible for our customers (they don't have access to the respective projects) each time when they access their projects.
As a technical note, I tried to use the patch made by Olivier Houdas, but it doesn't work too well because some issues statuses from WorkflowTransition are not returned by the query. I can add some examples, if it is necessary.
- Target version changed from Candidate for next major release to 3.4.0
Marius BALTEANU, thank you for improving the patch. It looks good to me. Passed all tests.
Marius BALTEANU wrote:
I think we should change the current behaviour (which lists all the statuses regardless the project) for the following reasons:
- consistency: with tracker and custom fields behaviour (#25501#note-4)
- privacy: for example, in our instance, we have some internal projects with multiple statuses (not related to our development workflow) that we don't want to be visible for our customers (they don't have access to the respective projects).
Indeed.
Setting target version to 3.4.0.
- Subject changed from All issue statuses shown when creating status filter to Status filter should show statuses related to project trackers only
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Patch applied, thanks. I've also updated the time entry query in order to show the same trackers and statuses.
- Has duplicate Feature #14217: issues view: only list relevant status in filter drop down added
- Related to Patch #27772: Issues reports should show only statuses used by the project added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Toshi MARUYAMA 
Updated by 
Updated by 
