Customer Fixed Issues and Known Issues Tahoe SP5 HF01
| Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (v1) << Tahoe SP3 HF02<< Tahoe SP3 HF03 << Tahoe SP4 << Tahoe SP5
On this page: Customer Fixed Issues | Known Issues
Merged Releases
Customer Fixed Issues
This section provides details about the fixed customer issues in following modules.
Service Management
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
120099 | In IM module tenant configurations, the Analyst section was not showing any data to configure. | Steps:
| In IM and SR modules tenant configurations, the Analyst section is showing data to configure successfully. |
120994 | The status of the ticket was not getting updated to In progress status for the SR which is having default analyst in the catalog configuration. | Steps:
| The status of the ticket is getting updated to In progress status for the SR which is having default analyst in the catalog configuration. |
121810 | The service name of the underpinning contract was not getting displayed in the drop-down list when selected any location under Vendor Information tab. | Prerequisite: The UNDERPINNING CONTRACT AGREEMENT should be created for vendor for ALL Location. (SLA > User > Underpinning Contract) Steps:
| The service name of the underpinning contract is getting displayed in the drop-down list when selected any location under Vendor Information tab. |
124436 | When the user was opening PR and clicking Submit without performing actions, the page was getting refreshed and triggering mail to Requestor, Assigned Analyst and Workgroup members. | Steps:
| No mail triggers when the user clicks Submit without modifying any data in PR and whenever status of PR changes, mail triggers to respective users. |
124713 | The Service Request Number was not visible on the Catalog details page when the user printed the page using the print icon option on the Catalog details. | Steps:
| The Service Request is visible on the Catalog details page when the user prints the page using the print icon option. |
124439 | Workgroup was not editable post approval of Problem Record. | Steps:
| Workgroup is editable when user Re-opens the Problem Record. |
123963 | Issue 1: The feedback icon missing on the My SR Page for Resolved and Closed SRs. Issue 2: The end user gets an email notification to provide feedback along with a feedback link on the Closed SR status. Upon clicking on the SR ID on the email, end user unable to provide Feedback. | Prerequisite:
Steps:
| A feedback option is available to the end users of the tool. The end user can provide feedback from the link provided on the email notification as well. |
123680 | Customer was unable to click the Next button during the raising of a Service Request (SR). | Prerequisites:
Steps:
| The Number attribute accepts only numeric values. |
124411 | In the Change Management module, a Change Record Status Change to Requested notification was triggered on clicking the Submit button without changing anything in the Change Record. | Steps:
| Notifications are not triggered on clicking the Submit button without changing anything in the Change Record. Note The notifications are triggered on modifying the following fields:
|
128525 | IVR changed to be implemented for New Incident for User. | Steps:
| IVR changes are implemented on the New Incident for User page. It accepts the phone number and UCID to find the Caller's name. |
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ