Bug 731931 - Attachment can't category as per case run in TCMS
Summary: Attachment can't category as per case run in TCMS
Status: NEW
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.5
Hardware: All
OS: Linux
Target Milestone: ---
: 4.0
Assignee: Yang Ren
QA Contact: tools-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-19 06:22 UTC by yanfu,wang
Modified: 2016-05-26 13:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description yanfu,wang 2011-08-19 06:22:51 UTC
Description of problem:
I copied from e-mail:
On 08/19/2011 12:01 PM, wang yanfu wrote:
> hi,
> I have one question for attachment problem in TCMS run.
> For example, I have three case run created for a testplan like below:
> https://tcms.engineering.redhat.com/case/87227/?from_plan=3739#case_run
> I opened one case run and found all Attachment shown in one case run:
> https://tcms.engineering.redhat.com/run/19442/
> But I uploaded specific log attachment to specific rhel distro before,
> so I want to review it like that way. For example, RHEL6.1 release run
> just shown RHEL6.1 log attachment since I uploaded it just for RHEL6.1,
> but seems all attachment jamed in
> https://tcms.engineering.redhat.com/case/87227/?from_plan=3739#attachment.
> So how do I category them as per case run? thanks
Hi , yanfu,
Now there is proper solution in TCMS about grouping case's attachments.
When you add attachment for a case-run , actually add to the case, so you
can see all attachments in one case-run.
I suggest continue specify attachment's name according to different 

If any other one encountered similar problems , welcome your suggestions 
and comments.


Danqing Li

Actual results:
typo in email: there is no proper solution about that issue ...

Expected results:
category attachment as per case run which will benefit for QE checking test logs.

Additional info:

Comment 1 yawei Li 2012-05-21 06:47:17 UTC
due to existing db schema, it is difficult to implement this requirement.
On TCMS 4.0 design phase, we will consider this issue.

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