Defect #33521

Use issue path instead of bulk update issues path when using the context menu with only one issue selected

Added by Marius BALTEANU about 1 year ago. Updated 2 days ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:5.0.0
Resolution:Fixed Affected version:

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.

0001-Use-issue_path-when-only-one-issue-is-modified-from-.patch Magnifier (12.6 KB) Marius BALTEANU, 2020-05-28 17:44

0001-Use-issue-path-instead-of-bulk-update-issues-path-wh.patch Magnifier (12.3 KB) Marius BALTEANU, 2021-07-04 17:31

Associated revisions

Revision 21089
Added by Marius BALTEANU 2 days ago

Use issue path instead of bulk update issues path when only one issue is selected in the context menu (#33521).

History

#2 Updated by Go MAEDA about 1 year 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 about 1 year ago

Go MAEDA wrote:

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.

Yes, please follow these steps using the default data:
  1. Make "Description" field mandatory for "In progress" status
  2. Find an issue in status "New" without "Description" filled in
  3. Using the context menu, try to change the issue status to in "In progress"
  4. 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 about 1 year ago

Marius BALTEANU wrote:

Go MAEDA wrote:

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.

Yes, please follow these steps using the default data:
  1. Make "Description" field mandatory for "In progress" status
  2. Find an issue in status "New" without "Description" filled in
  3. Using the context menu, try to change the issue status to in "In progress"
  4. 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.

#5 Updated by Marius BALTEANU 10 months ago

  • Target version changed from Candidate for next major release to 4.2.0

#6 Updated by Marius BALTEANU 4 months ago

  • Tracker changed from Patch to Defect
  • Status changed from New to Confirmed
  • Target version changed from 4.2.0 to 5.0.0

#8 Updated by Marius BALTEANU 2 days ago

  • Status changed from Confirmed to Closed
  • Resolution set to Fixed

Patch committed.

Also available in: Atom PDF