Patch #33521
Use issue path instead of bulk update issues path when using the context menu with only one issue selected
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | Candidate for next major release |
Description
When changing the attributes of an issue from the context menu, the bulk update issues path is used even if only one issue is selected. Because of this, if the validation fails, the user is redirect to the bulk edit view to fill in the required fields. But if Description is one of those fields, the user won't have available the field because Description is not available in the bulk edit view.
The attach patch changes the behaviour in order to use issue path to update attributes when only one issue is selected. In this case, if the validation fails, the user is redirect to the issue edit page. The route change was necessary in order to allow Patch method for bulk routes as well.
History
#1
Updated by Marius BALTEANU about 1 month ago
All tests pass: https://gitlab.com/redmine-org/redmine/pipelines/150020738
#2
Updated by Go MAEDA about 1 month ago
Would you tell me the steps to cause a validation error through the context menu? Since the context menu only shows valid options, I could not find a way to cause a validation error.
#3
Updated by Marius BALTEANU 24 days ago
Go MAEDA wrote:
Yes, please follow these steps using the default data:Would you tell me the steps to cause a validation error through the context menu? Since the context menu only shows valid options, I could not find a way to cause a validation error.
- Make "Description" field mandatory for "In progress" status
- Find an issue in status "New" without "Description" filled in
- Using the context menu, try to change the issue status to in "In progress"
- You should receive the validation error and you can observe that the Description field is not available in the page.
#4
Updated by Go MAEDA 24 days ago
Marius BALTEANU wrote:
Go MAEDA wrote:
Yes, please follow these steps using the default data:Would you tell me the steps to cause a validation error through the context menu? Since the context menu only shows valid options, I could not find a way to cause a validation error.
- Make "Description" field mandatory for "In progress" status
- Find an issue in status "New" without "Description" filled in
- Using the context menu, try to change the issue status to in "In progress"
- You should receive the validation error and you can observe that the Description field is not available in the page.
Thank you, confirmed the issue.