...
Update Set (Original Names) | Description | ||
|---|---|---|---|
[2012/10/26 - 1 https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=75bf6b792b11f840fcb01abf59da15f4 | Requirement 516 - Email Notifications: remove mention of 'additional information' from incident on-hold email notification. | ||
[2012/10/24 - 5 https://yale.service-now | Requirement 566 - request for new Service Request; see SCTASK0004241 | ||
Requirement 675 - Migration of Yale accounts from Legacy Systems; see SCTASK0018823 | |||
Requirement 683 - 5 day turnaround for Req 672 | |||
[2012/10/24 - 2 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=a87ed4b92b91b840fcb01abf59da15bd Requirement 566 - request for new Service Request; see SCTASK0004241 5c7e90b92b91b840fcb01abf59da1553 Reqirement 680 - Request ticket has been Approved: Subject of the email currently reads - 'Your Request Item RITM0019830 has been approved'. It should be corrected to read - 'Request for ITS Support Approved - Ticket Number: REQXXX'. | ||
[2012/10/24 - 4 1 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=a57e54b92b91b840fcb01abf59da15ac | Requirement 675 - Migration of Yale accounts from Legacy Systems; see SCTASK0018823 | [757e50b92b91b840fcb01abf59da1521 Reqirement 672 - Request ticket is Resolved notification has wrong content: Remove extraneous paragraph. |
https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=ea7e58792b91b840fcb01abf59da159e | Requirement 683 - 5 day turnaround for Req 672 | ||
[2012/10/24 - 2 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=5c7e90b92b91b840fcb01abf59da1553 Reqirement 680 - Request ticket has been Approved: Subject of the email currently reads - 'Your Request Item RITM0019830 has been approved'. It should be corrected to read - 'Request for ITS Support Approved - Ticket Number: REQXXX'. | ||
[2012/10/24 - 1 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=757e50b92b91b840fcb01abf59da1521 Reqirement 672 - Request ticket is Resolved notification has wrong content: Remove extraneous paragraph. | ||
[2012/10/23 - 4 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=617edc792b91b840fcb01abf59da15c2 | Requirement 527 - add personalized signature added to the on-demand email function for Incidents. | |
[2012/10/23 - 3 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=ba7e5c792b91b840fcb01abf59da1577 | Requirement 678 - Request for DSP Request Type-672-Request should be configured to work with the mobile view. | |
[2012/10/23 - 2 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=047e5c792b91b840fcb01abf59da157c | Requirement 677 - Request for DSP Request Type-672-Request needs to be viewable to only folks in the CTS organization. Only people members of the assignment units that begin with the prefix CTS should be able to see this request. | |
[2012/10/23 - 1 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=e67d58792b91b840fcb01abf59da152c | Requirement 680 - Make changes to the client facing Request email notifications. See attachment for the changes. These changes are necessary to bring the new DSP request type (Enhancement Request 672) live. | |
[2012/10/22 - 1 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=027dd4792b91b840fcb01abf59da15a8 | Requirement 680 - Make changes to the client facing Request email notifications. See attachment for the changes. These changes are necessary to bring the new DSP request type (Enhancement Request 672) live. | |
[2012/10/19 - 2 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=4b7d94792b91b840fcb01abf59da15cc | Requirement 672 - Add a new request type for DSPs so that they may submit a request and assign it to themselves and close it on first pass. Attached are the work-in-progress requirements. (continuation of development) | |
[2012/10/19 - 1 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=187d94792b91b840fcb01abf59da1518 4 | Requirement 527 - add personalized signature added to the on-demand email function for Incidents. | |
Requirement 678 - Request for DSP Request Type-672-Request should be configured to work with the mobile view. | |||
Requirement 677 - Request for DSP Request Type-672-Request needs to be viewable to only folks in the CTS organization. Only people members of the assignment units that begin with the prefix CTS should be able to see this request. | |||
Requirement 680 - Make changes to the client facing Request email notifications. See attachment for the changes. These changes are necessary to bring the new DSP request type (Enhancement Request 672) live. | |||
Requirement 680 - Make changes to the client facing Request email notifications. See attachment for the changes. These changes are necessary to bring the new DSP request type (Enhancement Request 672) live. | |||
Requirement 672 - Add a new request type for DSPs so that they may submit a request and assign it to themselves and close it on first pass. Attached are the work-in-progress requirements. (continuation of development) | |||
[2012/10/17 - 1 https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=647d14792b91b840fcb01abf59da15ec 19 - 1 | Requirement 672 - Add a new request type for DSPs so that they may submit a request and assign it to themselves and close it on first pass. Attached are the work-in-progress requirements. (continuation of development) | ||
[2012/10/17 - 8 https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=aa7d90792b91b840fcb01abf59da1553 1 | Requirement 672 - Add a new request type for DSPs so that they may submit a request and assign it to themselves and close it on first pass. Attached are the work-in-progress requirements. | ||
Requirement 633 - Knowledge Status Page Update Screen: Hide template field in the top left hand corner of the Knowledge Status Page Update screen. | [2012/10/17 - 7 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=027d14392b91b840fcb01abf59da1570 Status Page Update screen. | |
Requirement 632 - deactivate assignment units that haven't gone live | [2012/10/17 - 6 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=be7ddc392b91b840fcb01abf59da1567 t gone live | |
Requirement 628 - In the RITM the Request number is editable which means that someone can go in and associate this Requested Item with another Request. I can also go into the SCTASK and associate the SCTASK with another Request Item. These fields should not be editable, once a Request/Request Item/SCTASK is created the users should not be able to change the associated REQ, RITM or SCTASK. | [2012/10/17 - 5 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=5b7d5c392b91b840fcb01abf59da153c , RITM or SCTASK. | |
Requirement 700 - Each primary web category-Academic Applications - Business Applications - Email and Calendaring - Information Security - Phones & Directories - Wifi and Networks need an "Other" secondary term added to the drop-down. | [2012/10/17 - 3 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=9f7c10752b91b840fcb01abf59da1573 drop-down. | |
Requirement 500 - Add the 'notify' feature to the SC Task, RITM, Changes, Problems, Change Tasks, Problem Tasks Functionality like in Incident module. | [2012/10/17 - 2 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=707c10392b91b840fcb01abf59da150a like in Incident module. | |
Requirement 527 - add personalized signature added to the on-demand email function for Incidents. | [2012/10/16 - 3 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=d27c9cf52b91b840fcb01abf59da151e email function for Incidents. | |
Defect 373 - NetID is no longer a display field when viewing a list of people, when: | [2012/10/16 - 2 | https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=2f7c1cf52b91b840fcb01abf59da15e4 , when: | |
Defect 349 - Change Task and Problem Task do not show the new 'Affected Component' field. They show the 'Configuration Item' field instead. | |||
[2012/10/16 - 1 https://yale.service-now.com/nav_to.do?uri=sys_update_set.do?sys_id=4b7cd8f52b91b840fcb01abf59da15a5 | Defect 331 - ITIL users cn change the approver on a Change or a Request. To replicate submit a change, go into the approver record, switch the approver, and save. Approver is now whomever is selected. ITIL users should not be able to change the approver. |
...