Bug 865329

Summary: "Running Date" info on WebUI shows .close_date displayed instead of .running_date
Product: [Other] TCMS Reporter: Chris Ward <cward>
Component: DatabaseAssignee: Zheng Liu <zheliu>
Status: CLOSED INSUFFICIENT_DATA QA Contact: tools-bugs <tools-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: DevelCC: dli, junzhang, ryang, vchen, zheliu
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-13 07:45:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 865334    

Description Chris Ward 2012-10-11 08:59:10 UTC
Description of problem:
I have a test plan run, for example:

https://tcms.engineering.redhat.com/run/47553/

Which has a case run, for example #1610912

When i change the status of the case run to any state, the date 
in the 'Run Date' field under 'Test Case Run Detail Information'
page gets updated.

The 'Run Date' field seems to incorrectly linked to the
'closed_date' in the DB. I found this:

<div>
   <span class="detail_title">
       {% comment %}Running Date:</span>{{ test_case_run.running_date }} {% endcomment %}

   <span class="detail_title">Run Date:</span>
       {{ test_case_run.close_date }}
</div>

Which confirms my suspicion that we're showing close_date NOT running_date, as
running_date is actually commented out. 

I believe it's a bug. 

Shouldn't running date show .running_date data, not .close_date?

Comment 1 Zheng Liu 2012-10-19 05:39:19 UTC
As discussed with pm:
running_date is for test case run changed into running status.
stop_date is for test case run completed
Field name 'running_date' will be changed to 'start_date', 'close_date' will be changed to 'stop_date'.
On web UI, both two date fields will be prompted.

Comment 2 Chris Ward 2016-06-13 07:45:09 UTC
Stale bug clean up; reopen if anyone else actually supports this.