Hide Forgot
Custom text area to store details how to run automated jobs is highly desirable also for Test Run and Test Case Run. This text area has to be xml friendly, inserted xml data should not break page layout.
In fact, this bug includes two issues: 1. a custom field is needed. In fact, the Notes field is for user custom field. We can provide a XML-RPC API to get Notes. Is it Ok for you? 2. store link for test log link. It is reasonable, we will implement it in 3.7.0.
(In reply to comment #2) > In fact, this bug includes two issues: > 1. a custom field is needed. In fact, the Notes field is for user custom field. > We can provide a XML-RPC API to get Notes. Is it Ok for you? Note is already available via xml-rpc. However this field is supposed to contain user-related information and other data looks really confusing on a web interface. It would be much better to have a new text area (with xml-rpc access) which can differentiate from Note in web interface > > 2. store link for test log link. > It is reasonable, we will implement it in 3.7.0. Just a note this is for TestRun as well as TestCaseRun.
The Note field is a general field for anything, so adding new text field is not necessary. The link will be added in test case run. will be resolved on 3.7.0 release.
(In reply to comment #4) > The Note field is a general field for anything, so adding new text field is not > necessary. This won't satisfy requirements, new text field is necessary. New text field is supposed to hold information which has to be processed by program, it has to have defined a structure. The Note is supposed to hold free text (that's called notes) without any structure. Note field is not useless at the moment, it can contain important information related to testing. Mixture of user and machine-oriented data on one place is highly undesirable.
Created attachment 581571 [details] 3.7.0-1 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.
Hi Marian , Could you help to confirm whether satisfied with the solution ?
(In reply to comment #7) > Hi Marian , > > Could you help to confirm whether satisfied with the solution ? This doesn't meet requirements. - I requested text field, because "Data supposed to be in these fields can be actually much more complex. Text field is suitable just for basic support." as written in Description. This implementation is usable just for links, thus it is very limited. - Note shared in Comment 5 doesn't seem to be considered. - Neither description nor url is accessible via TestCase.get XML-RPC call, there are just some numbers, probably id list.
(In reply to comment #8) > (In reply to comment #7) > > Hi Marian , > > > > Could you help to confirm whether satisfied with the solution ? > > This doesn't meet requirements. > > - I requested text field, because "Data supposed to be in these fields can be > actually much more complex. Text field is suitable just for basic support." as > written in Description. This implementation is usable just for links, thus it > is very limited. > > - Note shared in Comment 5 doesn't seem to be considered. > Can u give more details, like an example u desired. > - Neither description nor url is accessible via TestCase.get XML-RPC call, > there are just some numbers, probably id list.
I've updated the spec to address your comments: Spec URL: https://casey.byu.edu/dnsviz/dnsviz.spec https://www.targetedwebtraffic.com/buy/buy-mobile-traffic https://www.seo25.com/product/buy-mobile-traffic-and-get-cheap-targeted-mobile-traffic Please let me know what you think. Cheers, Caseeey