Project

General

Profile

Actions

개선(improvement) #455

closed

개선(improvement) #389: OMT 개선/버그 v1.0.0

개선(improvement) #507: OMT 개선

[PC] Search within Results > Price Range (상세검색 > 가격대) (15)

Added by ziniy Kang 9 months ago. Updated 3 months ago.

Status:
완료성공(Resolve)
Priority:
보통(Normal)
Assignee:
Start date:
11/11/2025
Due date:
11/12/2025
% Done:

100%

Estimated time:
6.00 h
Part:
Build env.:
Prod


Files

picture291-1.png (55.2 KB) picture291-1.png ziniy Kang, 06/17/2025 03:57 AM
image.png (15.7 KB) image.png Lexi Kim, 06/20/2025 05:00 AM
#455.png (250 KB) #455.png Lexi Kim, 06/24/2025 04:45 AM
price_range_digits.png (104 KB) price_range_digits.png Lexi Kim, 06/25/2025 12:36 AM
455_devtest.mp4 (559 KB) 455_devtest.mp4 Lexi Kim, 07/14/2025 04:11 AM
23July_additional_request.png (90 KB) 23July_additional_request.png Lexi Kim, 07/23/2025 02:31 AM

Related issues

Related to Ellis improvement - QA #666: Develop manual test cases for Search within Results > Price Range feature in OMH & OMT완료(Done)

Actions
Copied to OMT KR - 개선(improvement) #674: [MO] Search within Results > Price Range (상세검색 > 가격대) (15)완료성공(Resolve)Dante Le12/05/202512/08/2025

Actions
Actions #1

Updated by ziniy Kang 9 months ago

  • Parent task set to #389
Actions #2

Updated by ziniy Kang 9 months ago

  • Parent task changed from #389 to #507
Actions #3

Updated by ziniy Kang 9 months ago

  • Assignee changed from ziniy Kang to Joseph Vo
Actions #4

Updated by Joseph Vo 9 months ago

ziniy Kang chi tiết task này là gì?

Actions #5

Updated by ziniy Kang 9 months ago

Actions #6

Updated by ziniy Kang 9 months ago

  • Description updated (diff)
Actions #7

Updated by ziniy Kang 9 months ago

Joseph Vo wrote in #note-4:

ziniy Kang chi tiết task này là gì?

đã add thêm nội dung.

Actions #8

Updated by Joseph Vo 9 months ago

  • Assignee changed from Joseph Vo to John Lee
Actions #9

Updated by John Lee 9 months ago

  • Start date set to 06/19/2025
Actions #10

Updated by ziniy Kang 9 months ago

  • Assignee changed from John Lee to Joo dev
Actions #11

Updated by Joo dev 9 months ago

  • Due date set to 06/19/2025
  • % Done changed from 0 to 100
  • Estimated time set to 6.00 h
  • Build env. set to Dev
Actions #12

Updated by Joo dev 9 months ago

  • Status changed from 신규(New) to 완료(Done)
Actions #13

Updated by Lexi Kim 9 months ago

(on Dev) Please change ' ₩ ' to '원'.

Actions #14

Updated by ziniy Kang 9 months ago

  • Status changed from 완료(Done) to 피드백(Feedback)
Actions #15

Updated by Anonymous 9 months ago

  • Related to QA #666: Develop manual test cases for Search within Results > Price Range feature in OMH & OMT added
Actions #16

Updated by Lexi Kim 9 months ago

SB has changed. Please check the #455.png file.

Actions #17

Updated by ziniy Kang 9 months ago

  • Subject changed from [PC/MO] Search within Results > Price Range (상세검색 > 가격대) (15) to [PC] Search within Results > Price Range (상세검색 > 가격대) (15)
Actions #18

Updated by ziniy Kang 9 months ago

Actions #20

Updated by Lexi Kim 9 months ago

https://www.figma.com/design/9GqC7ejQy7R9OyFkIPBtdd/OMT?node-id=23-127&t=vfCxAQk1uRyd5fCA-1
SB has changed. Please check the red-colored text in the Figma link or the attached file(price_range_digits.png). Thank you.

Actions #21

Updated by ziniy Kang 8 months ago

  • Assignee changed from Joo dev to harry harry
Actions #22

Updated by harry harry 8 months ago

  • Assignee changed from harry harry to Dante Le
Actions #23

Updated by Dante Le 8 months ago

  • Status changed from 피드백(Feedback) to 진행(Doing)
Actions #24

Updated by Dante Le 8 months ago

  • Status changed from 진행(Doing) to 완료(Done)
Actions #25

Updated by Dante Le 8 months ago

  • Build env. deleted (Dev)
Actions #26

Updated by Dante Le 8 months ago

  • Build env. set to Dev
Actions #27

Updated by Lexi Kim 8 months ago

(dev)
1. When the user clicks the ‘Apply’ button without entering values, the default values should be auto-filled. Currently, lowestprice is correctly auto-filled, but there’s a bug where the highestprice field displays the lowestprice value instead. (Please refer to Exceptional Case 4 in the storyboard.)
2. After entering values, clicking the Reset button should automatically change the input box values back to their default. Currently, the entered values remain in the fields instead of resetting.
3. When no number is entered, the default value is displayed in gray text.
4. Please make sure all Exceptional Cases in the storyboard are properly applied.

Actions #28

Updated by Dante Le 8 months ago

  • Status changed from 완료(Done) to 진행(Doing)
Actions #29

Updated by Dante Le 8 months ago

  • Status changed from 진행(Doing) to 완료(Done)
Actions #30

Updated by Dante Le 8 months ago

  • Due date changed from 06/19/2025 to 07/17/2025
Actions #31

Updated by Lexi Kim 8 months ago

dev test 18 July Common

1. When no number is entered, the default value should be displayed in gray text. On the initial screen and when the “Reset” button is clicked, the numbers should appear in gray. (However, if the default value is automatically filled based on user actions, the text color should be black.)

Actions #32

Updated by Lexi Kim 8 months ago

dev test done.

Actions #33

Updated by Dante Le 8 months ago

  • Due date changed from 07/17/2025 to 07/18/2025
Actions #34

Updated by Dante Le 8 months ago

  • Build env. changed from Dev to Staging
Actions #35

Updated by Lexi Kim 8 months ago

23 July Additional Request
(as-is) When the user clicks the input box, the default value overlaps with the user’s input. To enter a new number, the user must first delete all of the default value. (Please check the video I sent.)
(to-be) When the user clicks the input box, the default value should disappear, and the user’s input should be entered directly. The default values {lowestprice} and {highestprice} should only serve as placeholders and appear in gray text. I attached reference video.

Actions #37

Updated by Dante Le 7 months ago

  • Build env. deleted (Staging)
Actions #38

Updated by ziniy Kang 6 months ago

  • % Done changed from 100 to 90
Actions #39

Updated by ziniy Kang 5 months ago

  • Status changed from 완료(Done) to 완료실패(Failed)
Actions #40

Updated by Dante Le 4 months ago

  • Due date deleted (07/18/2025)
  • Status changed from 완료실패(Failed) to 진행(Doing)
  • Start date changed from 06/19/2025 to 11/11/2025
Actions #41

Updated by Dante Le 4 months ago

  • Due date set to 11/12/2025
  • Status changed from 진행(Doing) to QA test
  • Assignee changed from Dante Le to Lexi Kim
  • Build env. set to Dev
Actions #42

Updated by Lexi Kim 4 months ago

455, 674 should be tested together

Actions #43

Updated by Lexi Kim 3 months ago

  • Status changed from QA test to 확인(Confirmed)
  • Assignee changed from Lexi Kim to Dante Le

dev test done. thank you.

Actions #44

Updated by Dante Le 3 months ago

  • Status changed from 확인(Confirmed) to QA test
  • Assignee changed from Dante Le to Lexi Kim
  • Build env. changed from Dev to Staging
Actions #45

Updated by Lexi Kim 3 months ago

  • Status changed from QA test to 확인(Confirmed)
  • Assignee changed from Lexi Kim to Dante Le

stg test done. thank you.

Actions #46

Updated by ziniy Kang 3 months ago

  • Status changed from 확인(Confirmed) to QA test
  • Assignee changed from Dante Le to Lexi Kim
  • Build env. changed from Staging to Prod
Actions #47

Updated by Lexi Kim 3 months ago

  • Status changed from QA test to 완료성공(Resolve)
  • Assignee changed from Lexi Kim to Dante Le
  • % Done changed from 90 to 100

prod test done. thank you.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 50 MB)