개선(improvement) #447
closed
[FE/dotBizChannel] Personal information should be masked with HanaCard account.
Added by Lexi Kim 9 months ago.
Updated 9 months ago.
Files
- Copied from 개선(improvement) #420: [Plan/dotBizChannel] Personal information should be masked with HanaCard account. added
- Description updated (diff)
- File deleted (
picture754-1.png)
- Assignee changed from Joseph Vo to Mon Nguyen
- Due date changed from 05/30/2025 to 06/04/2025
- Status changed from 신규(New) to 진행(Doing)
- Start date set to 06/04/2025
- Estimated time set to 2.00 h
- Assignee changed from Mon Nguyen to Lexi Kim
Dear Lexi
Please help me reply some question
1. How about the email address with text before character , is it makup all or without the first character ?
2. About the Email address and Phone number, user can change on that form, so what happening when user click into that input ? is it revert the makup info or do something ?
Thanks
Update requirement
Dear Nguyen Tien Dat (Mon),
Instead of masking personal information in the Booking Detail, I suggest a different approach.
Can you make it so that the Booking Code in the search result list is not clickable? When clicked, it should not open any popup or window.
**This change should only apply when logged in with the account hwanchulyoo@hanafn.com.
-> Close the feature open detail booking when Hana Account
- Status changed from 진행(Doing) to 완료(Done)
- % Done changed from 0 to 100
- Build env. set to Dev
Dear Lexi Kim
Please help me double check on DEV environment
And let me know if any problem
Thank you
I have confirmed that the Booking Code click has been disabled. This part is complete.
Here is an additional request:
For the "1st Traveler Name" field, please apply masking based on the following policy.
Policy:
Only the part excluding the surname is masked (*).
Exceptional Case:
If the surname has two characters, both characters are masked.
e.g.) (as-is) 하현식 / (to-be) 하 * *
Lexi Kim wrote in #note-11:
I have confirmed that the Booking Code click has been disabled. This part is complete.
Here is an additional request:
For the "1st Traveler Name" field, please apply masking based on the following policy.
Policy:
Only the part excluding the surname is masked (*).
Exceptional Case:
If the surname has two characters, both characters are masked.
e.g.) (as-is) 하현식 / (to-be) 하 * *
Dear Lexi Kim
Please help me double check again on dev env
Already applied new request
Thank you
- Assignee changed from Lexi Kim to Mon Nguyen
- Assignee changed from Mon Nguyen to Eric Quach
- Build env. changed from Dev to Staging
Dear Eric Quach
Please help me double check on STG env
Thank you
- Assignee changed from Eric Quach to Mon Nguyen
Đã test:
- Không hiện booking detail > okay
Che 1 phần tên traveler -> okay
Eric Quach wrote in #note-15:
Đã test:
- Không hiện booking detail > okay
Che 1 phần tên traveler -> okay
Thank you
- Assignee changed from Mon Nguyen to ziniy Kang
- Build env. changed from Staging to Prod
Dear ziniy Kang
Please help me double check on PRD env
Thank you
- Status changed from 완료(Done) to 완료성공(Resolve)
- Assignee changed from ziniy Kang to Mon Nguyen
- Target version set to v1.0.0
Also available in: Atom
PDF
