Bug 721227 - [Quick Search][Simple Search][Advanced Search]Can't search plan
Summary: [Quick Search][Simple Search][Advanced Search]Can't search plan
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Yuguang Wang
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-14 05:53 UTC by Xin Gao
Modified: 2022-03-14 03:25 UTC (History)
4 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Xin Gao 2011-07-14 05:53:00 UTC 
Description of problem:
Searching plan via Quick Search/Simple Search/Advanced Search will come out error page. Please refer to attachment.

Version-Release number of selected component (if applicable):
3.5 on stage

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Turn to error page. Please refer to attachment.

Expected results:
Search plan successfully

Additional info:
Comment 1 Xin Gao 2011-07-14 09:02:21 UTC 
Additional info,
When searched plan(s) are created after 3.5(stage) on-line, this bug could be reproduced.
Otherwise, the feature of searching plan is normal.
Comment 2 Chaobin Tang 2011-07-18 05:22:42 UTC 
commit 37826b9cff03775fa63384594cd3c7c84974097e

Initialized the plan.owner with its author.
Comment 3 Guoping Feng 2011-07-20 07:16:31 UTC 
Verify 3.5.0-1 on stage -->PASS

Verify steps:
1.Selete Test Plan in top right.
2.Type plan name/ID (accurate/fuzzy / no existing).
3.Click the "go" button.
4.Create a new plan and search it in the [quick search] through the name/ID.

Actual result:
The search can be executed correctly.The plan(s) that meets the conditions can be searched out.
Comment 4 Guoping Feng 2011-07-20 07:45:43 UTC 
Sorry, this bug is verified on Build: 3.5.0-3 on stage.
Note You need to log in before you can comment on or make changes to this bug.