Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

TAPSS Refinement Sessions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

09/08/2024 Friday

Parcitipants: laila.valterio jessica.wood gaurang.fichadia sekar.krishnan rommel.ngo jing.xie seonah.choe

Jira Tickets discussed in the session:

  1. TAPSS-2143 Default picklist value for Mailing Address Status on Contact/Account to "Active"

  2. TAPSS-2124 Prevent Receipt from being sent more than once

  3. TAPSS-2129 Notification to case owner when a case has been updated

  4. TAPSS-2132 Only the owner can submit a spend plan

  5. TAPSS-2142 Activity Report field "Results" is a rich text box to be migrated to Salesforce Activity constraints

Decisions

#

Jira #

Discussion Summary

D-001

TAPSS-2143

Concern was raised for this requirement that defaulting ‘active’ will create active records without mail address, ultimately creating a similar problem for inconsistent data records.  Also, the solution of creating a new flow is not preferable for the business.

 Decided to park the ticket, focus on the training the users, and monitor this function with Marketing Automation (MA) stream.

+++

 Later the same day during the Enhancement Review session, another feedback was discussed:

Since the current interface for Lead conversion as well as AQ Account creation requires users to revisit the created Account records to update the address status even though address values are there, it will be worthwhile to re-visit this requirement for refinement. This kind of extra step usually cause more user errors as they have to manually check these details every time.

It was decided to revert the status to Refine and schedule for revisit in the future.

D-002

TAPSS-2124

Confirmed the ticket to be ‘ready’ with XS size, Could Have priority.  This ticket will now move to the future Sprint Planning session

D-003

TAPSS-2129

This requirement will also resolve another existing issue of already closed case with new enquiry not re-triggering case to open, as it will notify the team to look at.

Potential risk is raised that team might be receiving too many emails for notification; however, the volume of the notification will not be large, so risk is small.

Confirmed the ticket to be ‘Ready’ with S size, Should Have priority. .  This ticket will now move to the future Sprint Planning session

D-004

TAPSS-2132

Confirmed the ticket to be ‘Design’ with size 'M' for Sekar to review.

There is a current gap for the future point of contact for Spend Plan and we need to address this gap first.

D-005

TAPSS-2142

This is a part of ongoing discussion, and we will continue to refine.

Actions 

#

Jira #

Action Summary

Action Owner

A-001

TAPSS-2132

Gaurang to have discussion with Api to confirm the future end users and future point of contact for Spend Plan.

gaurang.fichadia

A-002

TAPSS-2142

Rommel to share the Activity field type migration impact analysis with Api and Laila for further discussion.

rommel.ngo

 

  • No labels