Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This looks interesting for me. I wonder, what is a typical usage of this link? We in BaseOS QA usually have a Beaker task per TCMS test case. When we are executing a test run, its associated task is ran on several architectures in Beaker. Therefore, we have bunch of logs associated with test case run. Eg: /CoreOS/sos/Sanity/plugins-basic -> i386 - TESTOUT.log - avc logs - attached logs... ... -> x86_64 - TESTOUT.log - avc logs - attached logs... ... ... So far all these logs can be identified using a single URL to Beaker log archive, if they are all from one Beaker job. In case e.g. one architecture is rerun in Beaker once more because of install failure, in separate job, all logs relevant to this test case run cannot be identified using single URL - we need one URL per Beaker job. Would it be possible to make this additional field a multiple url one?
we will add link in test case run, and multiple link and add/remove are supported. will be resolved on 3.7.0 release.
Created attachment 579797 [details] Test log Verify version 3.7.0-1 on stage - PASS Verify steps: 1. Click to any test run , Ex https://tcms-stage.englab.bne.redhat.com/run/25260/ 2. Expand one test run, Actual result : You can Add log or delete it by anybody.
This looks like a very useful feature. Will it be possible to add/remove log links using xmlrpc as well? Or shall I file a separate bug for this?
*** Bug 806786 has been marked as a duplicate of this bug. ***
Any idea about xmlrpc for this as questioned in Comment 4?
(In reply to comment #4) > This looks like a very useful feature. Will it be possible to > add/remove log links using xmlrpc as well? Or shall I file a > separate bug for this? Filed as bug 844731.