Req ID Track Business Ranking Priority Severity

7615 Core Workflow 01 P3-Medium impact to be assessed
7305 Core Workflow 02 P2-High june release target
7128 Core Workflow 03 P2-High june release target, moved from march release
7296 Core Workflow 04 P2-High
7089 Core Workflow 05 P3-Medium
7343 Core Workflow 07 P2-High
7685 Core Workflow 09 P3-Medium
6297 Core Workflow 10 P2-High
6754 Core Workflow 11 P3-Medium 2 - No Workaround
7166 Core Workflow 12 P3-Medium
7699 Core Workflow 13 P3-Medium
6402 Core Workflow 14 P4-Low
7406 Core Workflow 15 P3-Medium
7621 Core Workflow 16 P3-Medium
7301 Core Workflow 17 P3-Medium impact to be assessed
7663 Core Workflow 18 P3-Medium impact to be assessed
7209 Core Workflow P1 for L2 Team P3-Medium
7446 Core Workflow P1 for L2 Team P3-Medium
7718 Core Workflow P2 for L2 Team P3-Medium
6415 Core Workflow P1-Urgent
7031 Core Workflow P2-High 2 - No Workaround
7110 Core Workflow P2-High 2 - No Workaround
7111 Core Workflow P2-High 2 - No Workaround
7120 Core Workflow P2-High 2 - No Workaround
6308 Core Workflow P2-High
7670 Core Workflow P2-High
6401 Core Workflow P3-Medium
6403 Core Workflow P3-Medium
6408 Core Workflow P3-Medium
6409 Core Workflow P3-Medium
6559 Core Workflow P3-Medium
6585 Core Workflow P3-Medium
6950 Core Workflow P3-Medium
7001 Core Workflow P3-Medium
7267 Core Workflow P3-Medium
7288 Core Workflow P3-Medium
7394 Core Workflow P3-Medium
7395 Core Workflow P3-Medium
7456 Core Workflow P3-Medium
7611 Core Workflow P3-Medium
7617 Core Workflow P3-Medium
7634 Core Workflow P3-Medium
7647 Core Workflow P3-Medium
7658 Core Workflow P3-Medium
7668 Core Workflow P3-Medium
6406 Core Workflow P4-Low
7609 Core Workflow P4-Low
Functional Comments
Need Assessment
Func-60, Dev-240, QA-80
Functional Complete
Leitas FSD
Func-3, Dev-5, QA-4
Func-20, Dev-120, QA-40
Func-24, Dev-140, QA-40
Func-20, Dev-120, QA-40
Summary
MAGMA: ancillary and primary segment issues
Enhancement - Magma – BSA collection interface performance should be improved
BSA ancillary information to be added in the auto closed analysis report
Core reanalyze/reopen feature in eps Portal
auto-closing user induced cores header message for analysis report mail
SAP Retry implementation for UI
EPS Portal - Problems with file tracker
Core dashboard in EPS Portal is not auto refreshed
PMBTA fails to parse some special characters of a public report
Burt tool exception while submitting analysis report for core 50055901
Corrupted ucores not reported by Magma
EPS Portal, Core details view page - Add info about recent cases for same system ID to Core details page
Junk values in the EPS portal dashboard
Cleaning up junk Core files (cleaner script)
core transaction has not been created for below panic, a full core has been uploaded by customer and core tool says everything is perfect but still Magma ignored this file.
: Core file moved but some blocks went missing after the movement
Defect - Core id becomes '0' for the Final core Analysis Report
File processing for notifyd.764.1574064424.2013-11-11.23_43_33.ucore.bz2 is getting recognised as invalid core file
Core stuck in initializing state
Issue in Analysis Report
P1 core notification for core in Core Received status
Core reanalyze feature in Magma
Retry for SAP errors
EPS Portal - Wrong BT translation for PMBTA input
Magma Notifications intermittently failing
'Could not find out the ONTAP version for the core file, hence PMBTA execution was skipped
EPS Portal, File tracker - Core case ID column need to be added in file tracker results page
EPS Portal, Core dashboard page - Remove option to set “Core Received” In coredashboard page
Conditional Wait_TSE rules should provide more control on core autoclose behavior and on Email notification message.
Core transaction creation time must be highlighted in red upon completion of 48 hours
EPS Portal -SAP - Need to change the core owner name
The e-mail message after core processing using EPS portal UI is complete needs improvement
EPS : checksum differs is not handled from coretool output
Need to handle parallel processing of CoreFile Processing on the same file.
Need to display informatory message on the case status if it is closed while sending core processing email
Core ID: 50057021 must have identified as bug 535363 by BTA but its not
New version of Coretool
Text needs to be changed for recomended solution regarding burt burt 394862
Regarding CPU Utilization in cyclngssvl02.eng.netapp.com
PMA/BTA output is confusing in Core Case view page
Parsing Issue in the core tool for Panic Message
Core stuck in initializing state
Bug / RFE for Core Search
The lighter version of coretool is wrongly identifying non core files as corefiles
Mini core file is not going to the intermediate state, when it got closed with matching BURT.
EPS Portal, Admin - Core analysis admin page where conditional wait tse rules, editing notes, archival rules.
SAP-User induced file template tab need not to be present for all the core transactions
Direct Cover Status Initiated By Requirement Type Status Associated Release Date
Not Covered asubodh Functional New
Not Covered kusha Functional Design 3/7/2014
Not Covered asubodh Functional Design 3/7/2014
Not Covered kusha Functional New
Not Covered kusha Functional New
Not Covered kusha Functional New
Not Covered aravintb Functional New
Not Covered asubodh Functional New 9/13/2013
Not Covered bhav Functional New
Not Covered samathad Functional New
Not Covered aravintb Functional New
Not Covered prasadga Functional New 9/13/2013
Not Covered bhav Functional New
Not Covered asubodh Functional New
Not Covered jyothir Functional New
Not Covered asubodh Functional New
Not Covered samathad Functional UAT
Not Covered samathad Functional Validate
Not Covered aravintb Functional New
Not Covered asubodh Functional Duplicate
Not Covered kusha Functional New
Not Covered kusha Functional New 12/13/2013
Not Covered kusha Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional Cancelled 9/13/2013
Not Covered vradha Functional New
Not Covered prasadga Functional New 9/13/2013
Not Covered prasadga Functional New 12/13/2013
Not Covered prasadga Functional QA 6/7/2013
Not Covered asubodh Functional New
Not Covered asubodh Functional New 9/13/2013
Not Covered bismita Functional New 3/14/2014
Not Covered asubodh Functional New
Not Covered asubodh Functional Analysis
Not Covered asubodh Functional New
Not Covered jyothir Functional New
Not Covered kusha Functional New
Not Covered jyothir Functional New
Not Covered jyothir Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered aravintb Functional New
Not Covered anushae Functional New
Not Covered vradha Functional New
Not Covered prasadga Functional New 3/14/2014
Not Covered asubodh Functional New
ServiceNow Incident ID Creation Date
1/23/2014
9/26/2013
INC811660 8/7/2013
9/25/2013
7/19/2013
10/3/2013
2/13/2014
INC661008,PRB6719 12/14/2012
PRB5737 4/5/2013
8/19/2013
2/20/2014
1/24/2013
10/29/2013
1/23/2014
9/26/2013
2/4/2014
8/27/2013
11/20/2013
2/27/2014
1/28/2013
6/19/2013
7/30/2013
7/30/2013
INC807098 8/2/2013
12/19/2012
2/5/2014
1/24/2013
1/24/2013
1/24/2013
INC683883 1/24/2013
INC709214 3/5/2013
3/13/2013
6/5/2013
INC769172 6/11/2013
9/17/2013
9/24/2013
10/22/2013
10/23/2013
11/21/2013
1/23/2014
1/23/2014
1/29/2014
INC924527 1/31/2014
INC910983 2/3/2014
2/5/2014
1/24/2013
1/23/2014
Req ID Track BRD Business Ranking Priority Severity
13209 Escalation yes Dup 7028? In QA? P1-Urgent 1 - Critical
10060 Escalation Scotts list P1-Urgent 2 - No Workaround
7026 Escalation Scotts List P2-High 1 - Critical
7027 Escalation complete QA Tested, remove P2-High 1 - Critical
7030 Escalation yes group 01 - mar rel P2-High 1 - Critical
7225 Escalation yes group 01 role group P2-High 1 - Critical
7029 Escalation yes Scotts List P2-High 2 - No Workaround
7048 Escalation Scotts list P2-High 2 - No Workaround
7622 Escalation Scotts list P2-High 2 - No Workaround
7661 Escalation done 01 April release P2-High 2 - No Workaround
7723 Escalation Scots List P2-High 2 - No Workaround
10102 Escalation done QA tested P2-High 2 - No Workaround
10509 Escalation Scotts List P2-High 2 - No Workaround
7028 Escalation yes IN QA P2-High 3 - Workaround Exists
7226 Escalation Yes Scotts List P2-High
7542 Escalation to add 01 role group P2-High
7612 Escalation Scotts List P2-High
7613 Escalation Scotts list P2-High
7618 Escalation yes group 01 role group P2-High
6832 Escalation P3-Medium 2 - No Workaround
7025 Escalation P3-Medium 2 - No Workaround
7032 Escalation DUP 7225? P3-Medium 2 - No Workaround
7101 Escalation P3-Medium 2 - No Workaround
7151 Escalation P3-Medium 2 - No Workaround
7396 Escalation P3-Medium 2 - No Workaround
7724 Escalation P3-Medium 2 - No Workaround
7725 Escalation P3-Medium 2 - No Workaround
10605 Escalation Scotts list P3-Medium 3 - Workaround Exists
7007 Escalation to add 02 role group P3-Medium
7011 Escalation P3-Medium
7014 Escalation P1 for L2 Team P3-Medium
7015 Escalation P3-Medium
7127 Escalation P3-Medium
7199 Escalation P3-Medium
7204 Escalation P3-Medium
7217 Escalation Scots List P3-Medium
7310 Escalation P3-Medium
7449 Escalation Scots List P3-Medium
7457 Escalation P3-Medium
7610 Escalation P3-Medium
7614 Escalation P3-Medium
7619 Escalation Scots List P3-Medium
7620 Escalation P3-Medium
This list is ordered by Priority then severity. Need to verify that that prioiritization is
preferred over 01s in business list
7648 Escalation P3-Medium
13232 Escalation Scotts List P4-Low 2 - No Workaround
5936 Escalation 02 P4-Low 4 - Nice to Have
Summary
Align BURT creation to identify clusters per newer BURT standard (use ONTAP MODE FIELD)
L2/L3-Need to be able to modify the SAP case # before approving (or acknowledging) an EPS escalation -- the case# change should be permanent in the magma dbase
Need indication of secure case in Magma esc portal, plus error/warning messages for non-secure personnel
Ensure that changes to BURT database can not impact Magma esc portal functionality
Defect - Magma esc portal BU/subtype changes must be allowed without impacting prior escalations or manipulation of in-flight escalations (e.g. approve/decline/on-hold)
Manager-privileged users need to be able to modify real name and SMS information for other users
Update EPS escalation submission questions
Alterations to IMPACT= dropdown in Magma esc portal
Escalation submission form should prevent email addresses with whitespace being added; breaks other esc processing
Different BUs can have the same Subtype name (e.g. there can be an "Other" subtype in more than one BU (Regression)
Need "EPS Escalation Type" categories to be changeable by admins
L2/L3-UI improvement: Add right-click to edit BU/Subtype, or maintain edit/delete/add buttons so they can't be scrolled off screen
L2/L3- Admin-modifiable customer type+email DL pairings for escalation submission approval to allow for direct SAP retrieval of customer type
Removal of the EPS_OntapMode keyword, use the native BURT "ontap_mode" field instead
Change formatting of emails and SMS-directed email templates for new escalation notification
Handling of changing Subtype in Escalation Page
Magma esc portal breaks if SAP has a null/empty BugID field for master caseThis bug has been created in regard
with one of the issue in the escalation process.
Inconsistency in auto-add and email cc: list handling in Magma esc portal
EPS -The backend DB doesn’t purge users when deleted from the portal.
Whitespace in case# pasted during escalation submission fails
Add vertical white space (blank line) before each question in Magma EPS escalation email summary
Need to re-design the user SMS / full name entry methodology in the Magma EPS esc portal to allow manager access
Data entry fields all need to be monospace in Magma esc tool, everywhere
Customer name should be editable before escalation approval
Regarding listing the usernames in alphabetical order in EPS Escalation -Magma: CSS Escalation Management Tool: Adding users
Do not auto-select "yes" for question 3 during escalation submission - user should be forced to answer Yes or No
Do not auto-select an answer for yes/no part of Question 6 during escalation submission
L2/L3-Escalation date search criteria should be smart enough to take 1- or 2- number days/months as well as 2- or 4-character years (YYYY); also need to fix the error message shown to match
Need to track changes for any Role Management in the portal.
Need the provision to decline escalation for closedSAP case
Defect - New user is not reflecting the escalation group list while approving an escalation
Display a message in the page when opening an existing escalation from the Manage Escalations page, to indicate the submission data is being loaded, if there is delay in the page coming up.
Need to remove dl-eps-case-esc@netapp.com from cc list
Decline text is appended to the very end of the original template as well? It shouldn't be (see the >>>> marks).
User management icons/buttons should be consistent across EPS portal (add/edit/delete user)
Back-end database doesn't reflect the changes for user name in escalation Management Tool
Need to send magma/EPS alerts to DL only if any action needs to be taken by L2.
Unable to create EPS Escalation Request when attempting to escalate a secure case
Need to let users know once the User Input limit is exceeded in Escalation Page in EPS Portal Application
L2/L3-EPS portal pages Core case viewer page and core search page are not in sync for Escalation case id
EPS portal - Core location contains core file name instead of just directory
EPS Portal - Cannot create an escalation for SAP case 2004183804
SAP-Issue while updating Private notes in EPS Portal Dashboard when there is '<' and '>' in the text.
EPS portal : Need small script to move core and analysis files
Incorrect wording in EPS Escalation Type drop-down
New escalation SMS emails -- need optional ability to split messages into 160 character chunks
Direct Cover Status Initiated By Requirement Type Status Associated Release Date
New leita Enhancement Change in requirement
New scottsch Enhancement Change in requirement 9/6/2013
Not Covered scottsch Functional New 9/13/2013
Not Covered scottsch Functional New
Not Covered chaitane Functional UAT
Not Covered scottsch Functional New
Not Covered scottsch Functional New
Not Covered scottsch Functional Resolved 6/28/2013
Not Covered asubodh Functional New
Not Covered samathad Functional New
Not Covered scottsch Functional New
New scottsch Enhancement Change in requirement 9/6/2013
New scottsch Enhancement Change in requirement 9/6/2013
Not Covered scottsch Functional Resolved
Not Covered scottsch Functional New
Not Covered kusha Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered samathad Functional New
Not Covered scottsch Functional New
Not Covered scottsch Functional New
Not Covered scottsch Functional New
Not Covered scottsch Functional New
Not Covered asubodh Functional New
Not Covered scottsch Functional New
Not Covered scottsch Functional New
New scottsch Bug Bug
Not Covered asubodh Functional New
Not Covered asubodh Functional UAT
Not Covered samathad Functional UAT
Not Covered samathad Functional New
Not Covered asubodh Functional New
Not Covered samathad Functional UAT 9/13/2013
Not Covered samathad Functional New
Not Covered samathad Functional New
Not Covered jyothir Functional New
Not Covered samathad Functional New
Not Covered venkatac Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered asubodh Functional New
Not Covered bhav Functional New
New scottsch Bug Bug
Not Covered kusha Functional New 3/7/2014
ServiceNow Incident ID Creation Date
Core Workflow Magma P2
Escalation Magma P2
6/18/2013
6/18/2013
PRB6025 6/18/2013
9/5/2013
6/18/2013
6/28/2013
1/23/2014
INC925023 2/4/2014
2/28/2014
Escalation Magma P2
Escalation Magma P2
6/18/2013
9/5/2013
1/6/2014
1/23/2014
1/23/2014
1/23/2014
5/6/2013
6/18/2013
6/19/2013
7/25/2013
8/15/2013
10/23/2013
2/28/2014
2/28/2014
Escalation Magma P2
INC770251 6/13/2013
INC775862 6/14/2013
PRB6026 6/17/2013
6/17/2013
INC811343 8/7/2013
8/22/2013
8/26/2013
8/29/2013
9/27/2013
11/20/2013
11/22/2013
1/23/2014
1/23/2014 scottsch
1/23/2014 scottsch
1/23/2014 scottsch
INC924561 1/31/2014 scottsch
Escalation Magma P2 scottsch
9/10/2012
Req ID Track Business Ranking Priority Severity
7552 File Upload Development P1-Urgent
7185 File Upload 1 P2-High
7548 File Upload 1 P2-High
7669 File Upload P2-High
5259 File Upload P3-Medium 2 - No Workaround
5602 File Upload P3-Medium 2 - No Workaround
5746 File Upload P3-Medium 2 - No Workaround
5685 File Upload P3-Medium 3 - Workaround Exists
6839 File Upload P3-Medium
7044 File Upload P3-Medium
7205 File Upload P3-Medium
7342 File Upload P3-Medium
7641 File Upload P3-Medium
7021 Performance P3-Medium 3 - Workaround Exists
6767 Performance P3-Medium
6880 Performance P3-Medium
Summary
290 - Magma business process logic must to support automated ingestion of PerfArchives
ISF (Integrated Support File Upload)
71 - Magma requirements for core files & support log files handling
'Unexpected error in file tracker in production
Omniture code for Magma
update the CASE BURT# in SAP CRM from BURT system
Core-file to CASE validation at Magma interface based on System ID
Magma file upload successful completion to update SAP Notes
Cleaning up of the directories - many uploaded data files are leaving empty directories behind in cs-cores1
Business is requested to increase the upload speed for Magma and Aspera
upgrade to the Aspera console and applying the license to App03 and App10
Aspera version upgrade for AsperaCentral Process is consuming more resident memory
Trying to upload some information but received an application block
Duplication in the private notes section of core truncation.
EPS Portal - add rescan button in core analysis report generator page to rescan the file list.
Please check if special characters work fine in core file name or not.
Direct Cover Status Initiated By Requirement Type Status Associated Release Date
Not Covered sridharm Functional Development 6/6/2014
--- michelly Folder New
Not Completed sridharm Functional Development
Not Covered vradha Functional New
Not Covered kusha Functional Candidates 3/14/2014
Not Covered sheelam Functional Queue 3/14/2014
Not Covered skunju Functional New 12/13/2013
Not Covered skunju Functional New 3/7/2014
Not Covered kusha Functional New
Not Covered tarini Functional New
Not Covered samathad Functional New
Not Covered kusha Functional New
Not Covered samathad Functional New
Not Covered jyothir Functional New
Not Covered bhav Functional New
Not Covered samathad Functional New
ServiceNow Incident ID Creation Date
1/6/2014
8/20/2013
1/6/2014
2/5/2014
3/14/2012
PRB5337 6/15/2012
8/1/2012
7/19/2012
5/8/2013
6/27/2013
8/26/2013
10/3/2013
1/29/2014
6/18/2013
4/12/2013
PRB5929 5/22/2012