Project

General

Profile

Actions

Defect #27533

closed

Cannot change the priority of the parent issue in issue query context menu when parent priority is independent of children

Added by Vito Marolda over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues list
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

Also if Tracking settings are set to have parent priority independent of children, the context menu in issue query has priorities grayed out.
In fact, when normally editing, the priorities of parent issues are perfetcly editable.
This bug affects the context menu only.


Files

Redmine Version.PNG (13 KB) Redmine Version.PNG Screenshot of Version information Vito Marolda, 2017-11-14 19:58
Tracking settings.PNG (6.06 KB) Tracking settings.PNG Screenshot of tracking settings Vito Marolda, 2017-11-14 19:58
Priority grayed out.PNG (15.4 KB) Priority grayed out.PNG Screenshot of issue query context menu Vito Marolda, 2017-11-14 19:58
0001-Fixato-priority-disabilitato-in-query-list.patch (1.09 KB) 0001-Fixato-priority-disabilitato-in-query-list.patch resolving patch Vito Marolda, 2017-11-15 12:15

Related issues

Related to Redmine - Defect #20992: Parent priority "Independent of subtasks" setting doesn't workClosedJean-Philippe Lang

Actions
Related to Redmine - Patch #28168: Allow context-menu edit of % done and priority of parent issues if the fields are not derivedClosedGo MAEDA

Actions
Actions #1

Updated by Vito Marolda over 6 years ago

I have fixed my installation. Attached the patch. Fortunately it was very simple. I am not a Ruby programmer.

Actions #2

Updated by Toshi MARUYAMA about 6 years ago

  • Target version set to 3.3.6

LGTM.
This patch is same with #20992.

Actions #3

Updated by Marius BÄ‚LTEANU about 6 years ago

  • Related to Defect #20992: Parent priority "Independent of subtasks" setting doesn't work added
Actions #4

Updated by Go MAEDA about 6 years ago

Toshi MARUYAMA wrote:

LGTM.
This patch is same with #20992.

Absolutely. The following code is the change made by #20992 (r14671).

Index: app/views/issues/_attributes.html.erb
===================================================================
--- app/views/issues/_attributes.html.erb    (revision 14670)
+++ app/views/issues/_attributes.html.erb    (revision 14671)
@@ -11,7 +11,7 @@
 <% end %>

 <% if @issue.safe_attribute? 'priority_id' %>
-<p><%= f.select :priority_id, (@priorities.collect {|p| [p.name, p.id]}), {:required => true}, :disabled => !@issue.leaf? %></p>
+<p><%= f.select :priority_id, (@priorities.collect {|p| [p.name, p.id]}), {:required => true} %></p>
 <% end %>

 <% if @issue.safe_attribute? 'assigned_to_id' %>
Actions #5

Updated by Go MAEDA about 6 years ago

  • Status changed from New to Resolved
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed to the trunk. Thank you for detecting and fixing this issue.

Actions #6

Updated by Go MAEDA about 6 years ago

  • Status changed from Resolved to Closed

Merged from trunk to 3.4-stable and 3.3-stable.

Actions #7

Updated by Go MAEDA about 6 years ago

  • Related to Patch #28168: Allow context-menu edit of % done and priority of parent issues if the fields are not derived added
Actions

Also available in: Atom PDF