19/09/2024 Thursday
Participants: laila.valterio rommel.ngo seonah.choe aoife.tully gaurang.fichadia
Sprint in review: TAPSS - Sprint 45 Sep R1, 30th Aug - 20th Sep
Sprint Goal:
- Opportunity Page layout enhancement with End user UAT
- AQ v25 Upgrade
- BT Upgrade
- Continue to accurately estimate the ticket size comparing with time tracking (Ongoing)
Jira Filter used: TAPSS Open Sprint Completed Tickets (Please note this filter will always show you currently ‘active’ sprint and any sub task is excluded in the view)
Issue key | Summary | Business Area | Labels | EPIC | Release Note | Fix versions | Status |
TAPSS-2136 | Assess and deploy BT v6.19, 6.20, and 6.22 from currently 6.18 | CG and GA | 2024Q3 | This task ticket aims to assess the new versions of BT Payment v6.19 and 6.20 and deploy them to production so that business is upto date with latest features and fixes from BT. | September 2024 Release 1 | 09 SIGNED-OFF | |
TAPSS-2037 | AQ Upgrade to v25 | TAP | 2024Q3 | V25 is mostly about SmartBatch 2.0 upgrade and a few bug fixes. This release is a stepping stone to more usable versions of SmartBatch 2.0 such as v26 and v27. | September 2024 Release 1 | 09 SIGNED-OFF | |
TAPSS-1873 | Gift/Pledge Opportunity Pagelayout Enhancement 1 | Development, TAP | 2024Q3, Enhancements | TAPSS-1656 Opportunity- Page Layout & Stage Uplift and Enhancement | There are 60 fields in the existing Opportunity page layout. Many of these fields are not used by the business and even more are not populated until the Solicitation stage. Using this ticket(s), after impact assessment and analysis, we hid those unused fields from Opportunity page layout (only for Gift/Pledge record type) and also added Key Field feature to provide the business user guidance to focus on across opportunity stages. | September 2024 Release 1 | 09 SIGNED-OFF |
TAPSS-2178 | Gift/Pledge Opportunity Pagelayout Enhancement 3 -Unchanged pagelayout&Validation Rule | Development, TAP | 2024Q3, Enhancements | TAPSS-1656 Opportunity- Page Layout & Stage Uplift and Enhancement | There are 60 fields in the existing Opportunity page layout. Many of these fields are not used by the business and even more are not populated until the Solicitation stage. Using this ticket(s), after impact assessment and analysis, we hid those unused fields from Opportunity page layout (only for Gift/Pledge record type) and also added Key Field feature to provide the business user guidance to focus on across opportunity stages. Also the team made sure this change does not impact existing validation rules nor other page layouts outside of the scope. |
| 09 SIGNED-OFF |
TAPSS-2177 | Gift/Pledge Opportunity Pagelayout Enhancement 2 - Stage Keyfields & Persona | Development, TAP | 2024Q3, Enhancements | TAPSS-1656 Opportunity- Page Layout & Stage Uplift and Enhancement | There are 60 fields in the existing Opportunity page layout. Many of these fields are not used by the business and even more are not populated until the Solicitation stage. Using this ticket(s), after impact assessment and analysis, we hid those unused fields from Opportunity page layout (only for Gift/Pledge record type) and also added Key Field feature to provide the business user guidance to focus on across opportunity stages. |
| 09 SIGNED-OFF |
TAPSS-2129 | Notification to case owner when a case has been updated | CG | Enhancements | In order for case owner not to miss a reply, this feature is to send notification when a case has been updated. | September 2024 Release 1 | 09 SIGNED-OFF | |
TAPSS-2247 | Apsona report issue with event briefing (Apsona Ticket # 00032194) | Prospect Development | L1Support | Because of some of the Guest are not really contact records, the report is not able to sort the the list by Total Giving which is stored in Account Record. Having no link to Contact then to Account is causing the merge action to not sort accordingly. The fix here is to filter out non linked contacts and subsequently remove empty lines from the report. | September 2024 Release 1 | 09 SIGNED-OFF | |
TAPSS-2195 | Campaign Member upload issue | Alumni Relation | L1Support | Based on Salesforce support’s response, the end user tried with 15 digit SF ID instead of 18 digit SF ID and accepted this as workaround. |
| 09 COMPLETE | |
TAPSS-2176 | Spend Plan approval submitting issue (SNOW# INC066875) | Spend Plan | L1Support | The incident was raised by the end user, having an issue with Spend Plan submission. This is more due to lack of user training issue rather than bug fix and end user confirmed that issue is no longer present. |
| 09 COMPLETE | |
TAPSS-2290 | BAT Issue : Indirect Contact Auto Gift Recognition (TAPSS-2037-007) zendesk # 11956 | GA | TestinUAT |
|
| 09 COMPLETE | |
TAPSS-2289 | BAT Issue : Peoplesoft Batch Validation is not triggering in UAT | GA | TestinUAT |
|
| 09 COMPLETE | |
TAPSS-2288 | BAT Issue : Batch Proof Report is not generating in UAT (Zendesk # 11935) | GA | TestinUAT |
|
| 09 COMPLETE | |
TAPSS-2283 | BAT Issue : Apsona Receipting Not working as epected for Standard User Profile (Zendesk # 11934) (Apsona Case # 00032388 ) | GA | TestinUAT |
|
| 09 COMPLETE | |
TAPSS-2181 | An error occurred with your "Usyd Copy Email Activity Files to New Activity Report" flow (SNOW #INC0672900) | TAP | Training | We noticed that there are some users having an issue linking their email to Jarvis as activity report as email message exceeds the max length of 32768, the system limit hit and stopping the automation work. In this case, activity report has to be manually created with email as attachment or summarized content. This has been communicated with Jarvis training team and they will reach out the end users to provide relevant training when encountered this issue. |
| 09 COMPLETE | |
TAPSS-2197 | Update filter field with the correct field "Event Start Date/Time" instead of "Event Start Date" | PD |
|
|
| 09 COMPLETE |
29/08/2024 Thursday
Participants: laila.valterio rommel.ngo seonah.choe aoife.tully gaurang.fichadia
The purpose of this meeting is to showcase the completed tickets (Enhancement, L1support, Tech debt) of the sprint before we close the active sprint and start the new one.
Sprint in review: TAPSS - Sprint 44 Aug R2, 9th Aug - 29th Aug
Jira Filter used: TAPSS Open Sprint Completed Tickets (Please note this filter will always show you currently ‘active’ sprint and any sub task is excluded in the view)
Key | Summary | Business Area | Labels | EPIC | Release Note | Fix versions | Status |
ASE, TAP | We want to track engagement program of campaign record types by adding a picklist field on campaign object. This is going to be used for internal tracking and analysis for Campaign 2.0 Engagement Goal | 09 COMPLETE | |||||
Event Brief Apsona report to exclude a future event for being pulled into Most recent event attended | PD | so that we can accurately show the most recent event a guest has attended on an event brief | 09 COMPLETE | ||||
Spend Plan | Provision access for multiple Spend Plan users. | 09 COMPLETE | |||||
Request to run Duplicate job on Account and Contact (SNOW# INC0660589 ) | Advancement | A one time request from DRS team to run the duplicate rule for Account and Contacts. | 09 COMPLETE | ||||
GIN Notifications when changing the owner not getting email notification | GA | Fix issue around emails that are not verify that is causing notifications to not be sent/received by the intended user. | 09 COMPLETE | ||||
iModule Integration, TechDebt, GA | A once off issue with the integration which when ran manually got fixed and integrated the data accordingly. |
| 09 COMPLETE | ||||
Question on reversing cheque batch on the same day (SNOW# INC0664842) | GA |
|
| 09 COMPLETE | |||
An Error Occurred with Your "Add Batch Item Transaction" Flow | Tech Debt, GA | User training is required so user can always ensure that the Signator is related to the Batch Item Account. |
| 09 COMPLETE | |||
SITS Integration - School Email to be added as an additional Alternative ID to Contact | TAP |
|
| 09 COMPLETE | |||
Student Address is not receiving when there is manual update within the address information | SITS Integration |
|
| 09 COMPLETE | |||
Tech Debt | This exercise is to confirm the existing flow logic will be intact after the new Salesforce release to come. | 09 COMPLETE |
