Issue context menu and bulk edit form show irrelevant statuses
|Assignee:||Jean-Philippe Lang||% Done:|
A parent project is setup with several custom trackers with custom workflows. It's child project uses a completely individual tracker with its own workflow (not overlapping with any of its parent's).
When I right-click an issue in the issue list of the child project and select Status, it shows me all statuses from the parent project (as disabled) along with the ones for the current tracker/project. Much unneeded staff to scroll through.
Similar on the bulk edit screen: all statuses from parent project are listed as available, although the current project only has one tracker and one workflow with none of those statuses relevant.
Is it the same in the latest release? Any way to filter them more strictly?
#2 Updated by Victor Dulepov about 8 years ago
For bulk edit (when you edit issues belonging to different trackers) the page is still somewhat misleading (not all field changes will apply to all issues); however, you can restrict the list of statuses to only really allowed values by replacing line 195 of app/controllers/issues_controller.rb
@available_statuses = Workflow.available_statuses(@project)
with an equivalent of what is done inside app/controllers/context_menus_controller.rb :
if (@issues.size == 1) @issue = @issues.first @available_statuses = @issue.new_statuses_allowed_to(User.current) else @available_statuses = @issues.map do |i| i.new_statuses_allowed_to(User.current) end.inject do |memo,s| memo & s end end
#4 Updated by Jean-Philippe Lang about 8 years ago
- Subject changed from Issue list and Bulk Edit: irrelevant Statuses from a parent project available to Issue context menu and bulk edit form show irrelevant statuses
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 1.4.0
- Resolution set to Fixed
Fixed for 1.4.0.