...
Jira Tickets discussed in the session:
# | Key | Summary |
1 | Relating Activites to Accounts and Contacts | |
2 | Backdate Actvities | |
3 | Objects with Activity Component | |
4 | Surface Substantive Activity into Task pagelayouts | |
5 | As a Development Officer, I want to have my opportunity stage to be Early Cultivation or Late Cultivation | |
6 | As a Development Officer, I want to update Prospect Pool in opportunity in Late Cultivation stage before moving to Solicitation | |
7 | As a Development Officer, I want to update at least one of Gift Theme in opportunity in Late Cultivation stage before moving to Solicitation | |
8 | As a Development Office, I want to create opportunity with only with Identification & Qualification stage | |
9 | TAPSS-2016 (only briefly) | AQ 26: SmartBatch 2.0 soft credits on Batch Item Transaction need to adjust Batch Approval Reports |
Decisions
# | Jira # | Decision Summary | Labels Added |
D-022 | Focus on Household to reflect all the activities form all contacts associated with it. User stories to be reflected to this for further communication and training purpose. Priority = Must Have, T-shirt Size = XS | Training | |
D-023 | Define the business rule for backdating. Adding tracking function in the future may assist with future audit - this will be a separate build. Priority = Must Have, T-shirt Size = XS | Training, BusinessRule | |
D-024 | Business want the consistent acitvity visibility for Contact and Cases as well. UX for activity creation will be 'cut over' from Activity reports and surface Email, Event, Call, Task for Activity Priority = Must Have, T-shirt Size = S | Training | |
D-025 | Business decision to surface this fields for End user but only 'read only' or to be used purely for insights. 3 options are presented:
| BusinessRule | |
D-026 | Signed-off |
| |
D-027 | Signed-off |
| |
D-028 | Signed-off |
| |
D-029 | Signed-off |
| |
D-030 | Separately discussed with GA business |
|
...
# | Jira # | Action | Action Owner |
A-011 | Once Rommel update the user story and acceptance criteria, assign to Laila for review and sign-off | ||
A-012 | TAP Business confirm the business rule on backdate. We will not change this user story and solution but we highlight that system will provide created date vs backdate for potential report and audit if required. Once Rommel update acceptance criteria, assign to Laila for review and sign-off | ||
A-013 | Rommel to confirm the existing activity visibility for Contact and Cases for consistent record type. Update the user story with acceptance criteria for Contact/ Case and action buttons, assign to Laila for review and sign-off | ||
A-014 | Park for further development on this until business decision. TAP business to discuss and confirm. |
...