Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.9.0-b1
-
Component/s: None
-
Labels:None
Description
When attempting to delete a service from a client profile page in the admin UI, expanding the table row before clicking "Delete" leads to the failure of the service to be deleted. Also, a success message stating that the service was scheduled to be canceled, but such an action is not performed.
- Go to a client profile in admin interface
- Select a deletable status in the services widget
- Expand any service row
- Click the delete option on any service row and confirm
- You will receive a message "The selected services were successfully scheduled to be canceled."
It is not true that it was scheduled for cancellation and that was not the desired action in the first place
Activity
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.9.0 Sprint 6 [ 104 ] |
Tyson Phillips (Inactive)
made changes -
| Assignee | Tyson Phillips [ tyson ] |
Tyson Phillips (Inactive)
made changes -
| Fix Version/s | 4.9.0-b1 [ 11301 ] |
Tyson Phillips (Inactive)
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Tyson Phillips (Inactive)
made changes -
| Summary | Service deletion fail after widget row expansion | Service deletion fails if widget row expaned first |
Tyson Phillips (Inactive)
made changes -
| Description |
* Go to a client profile in admin interface
* Select a deletable status in the services widget * Expand any service row * Click the delete option on any service row and confirm * You will receive a message "The selected services were successfully scheduled to be canceled." It is not true that it was scheduled for cancellation and that was not the desired action in the first place |
When attempting to delete a service from a client profile page, or from the billing services page in the admin UI, expanding the table row before clicking "Delete" leads to the failure of the service to be deleted. Also, a success message stating that the service was scheduled to be canceled, but such an action is not performed.
* Go to a client profile in admin interface * Select a deletable status in the services widget * Expand any service row * Click the delete option on any service row and confirm * You will receive a message "The selected services were successfully scheduled to be canceled." It is not true that it was scheduled for cancellation and that was not the desired action in the first place |
Tyson Phillips (Inactive)
made changes -
| Description |
When attempting to delete a service from a client profile page, or from the billing services page in the admin UI, expanding the table row before clicking "Delete" leads to the failure of the service to be deleted. Also, a success message stating that the service was scheduled to be canceled, but such an action is not performed.
* Go to a client profile in admin interface * Select a deletable status in the services widget * Expand any service row * Click the delete option on any service row and confirm * You will receive a message "The selected services were successfully scheduled to be canceled." It is not true that it was scheduled for cancellation and that was not the desired action in the first place |
When attempting to delete a service from a client profile page in the admin UI, expanding the table row before clicking "Delete" leads to the failure of the service to be deleted. Also, a success message stating that the service was scheduled to be canceled, but such an action is not performed.
* Go to a client profile in admin interface * Select a deletable status in the services widget * Expand any service row * Click the delete option on any service row and confirm * You will receive a message "The selected services were successfully scheduled to be canceled." It is not true that it was scheduled for cancellation and that was not the desired action in the first place |
Automated transition triggered when Tyson Phillips (Inactive) created pull request #810 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour, 40 minutes [ 6000 ] | |
| Worklog Id | 13292 [ 13292 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #810 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
