Allow context-menu edit of % done and priority of parent issues if the fields are not derived
|Assignee:||Go MAEDA||% Done:|
Following #27533, r17129 implemented a change to not check anymore whether all selected issues for a context-menu can be assigned a priority. This change however is incorrect and incomplete unfortunately.
The check to disable setting of the priority (and similarly but missed in #27533: setting the % done field) was originally done in the view there since originally, the priority and %done fields were always derived from child issues. That is, parent issues always had the highest priority of any of their child issues and a average % done. Later, Redmine gained the ability to configure whether the priority and % done fields should be derived on parent issues or should be settable on their own.
The patch, as it was comitted in r17129 unfortunately fails to check whether the priority field can indeed not be set because the priority field is derived). In that case, the context-menu options should still be disabled. In any case, the same issue also is present for the % done field and is there still unhandled completely.
The attached patch against current trunk (at r17192) fixes and unifies the behavior for both fields.
Allow context-menu edit of % done and priority of parent issues if the fields are not derived (#28168).
Patch by Holger Just.