Bug 702251 - [Advanced search]Can not search new plan/case/run in Advance search
Summary: [Advanced search]Can not search new plan/case/run in Advance search
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Yang Ren
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks: 702254
TreeView+ depends on / blocked
 
Reported: 2011-05-05 07:07 UTC by Xin Gao
Modified: 2022-03-14 03:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Xin Gao 2011-05-05 07:07:35 UTC
Description of problem:
Can not search new plan/case/run in "Advance search". But they can be searched in the "Search Plans"/"Search Cases"/"Search Runs"/ of submenu.

Version-Release number of selected component (if applicable):
3.4

How reproducible:


Steps to Reproduce:
1.Click "Advance search"

2.Input or choose some options in plan/case/run's search field.

3.Click "search plan/search case/search run" button.
  
Actual results:
Can not search new plan/case/run in Advance search.

Expected results:
The plans/cases/runs can be searched.

Additional info:

Comment 1 Danqing Li 2011-05-05 08:14:08 UTC
the search result is not real-time.
tcms build data index for advanced search every four hours.

we have discussed this , we(pm team , dev team ) though it's acceptable now.

Keep this bug open ,we want get more requirement from users.

Comment 2 Jin Zhao 2011-05-05 15:40:07 UTC
Try to search after added more than four hours, the search result can not list the new one.

Comment 3 Xin Gao 2011-06-16 06:34:27 UTC
Hi Chaobin,
This problem seems to have been resolved. Please change this bug's status to "ON_QA", so as to verify it.

Comment 4 Xin Gao 2011-06-22 02:59:31 UTC
Verify version: 3.4 on stage (3.4-1)

Actual result:
Can search new plan/case/run in "Advance search".

Verify result:  PASS


Note You need to log in before you can comment on or make changes to this bug.