| Summary: | Make the test plans/runs readable by all | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | brian avery <brian.avery> | ||||||
| Component: | bugzilla | Assignee: | Michael Halstead <mhalstead> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Undecided | CC: | infras.bug.watcher, Infras.watcher, jose.perez.carranza, mhalstead | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
Created attachment 3217 [details]
permissions NOT set to readable by all.
All test plans are now world readable. I updated the database directly to save time. The following test plans are also world writable. Shall I remove global write access from plans not labeled sandbox? Is there potential for abuse with global write access? ADT Docs: Community Sandbox ADT: Community Sandbox Anjuta Plugin: Community Sandbox Autobuilder: Community Sandbox Automated Build Testing: Community Sandbox Automated Runtime Testing: Community Sandbox BitBake: Community Sandbox BSP Docs: Community Sandbox BSP/QEMU: Community Sandbox Bugzilla: Community Sandbox Build Appliance: Community Sandbox Community Cross-prelink: Community Sandbox Development: Community Sandbox DHCP Test Eclipse Plugin: Community Sandbox Hob: Community Sandbox Installation: Community Sandbox Kernel Development: Community Sandbox Kernel: Community Sandbox Matchbox: Community Sandbox Meta-yocto: Community Sandbox OE-Core: Community Sandbox Package Management Issues: Community Sandbox Pseudo: Community Sandbox Quick Start: Community Sandbox References: Community Sandbox Runtime: Community Sandbox Sato: Community Sandbox Security - Recipe Upgrade: Community Sandbox Security: Community Sandbox Swabbeer: Community Sandbox System Startup: Community Sandbox Test plans of BI Toaster: Community Sandbox Website: Community Sandbox Wiki: Community Sandbox Yes, I think is better to remove the global write access to the test plans/ runs that are not labeled as sandbox to keep the integrity of the test plans and avoid losing information as in the past. Yes, I think is better to remove the global write access to the test plans/ runs that are not labeled as sandbox to keep the integrity of the test plans and avoid losing information as in the past. Michael please proceed with the updates I've updated the following to remove global write access. Community DHCP Test Test plans of BI Test Plans are now public readable on Testopia |
Created attachment 3216 [details] permissions set to readable by all. Currently most of our test runs are not readable by people outside the tester group. To fix this we need to 1) add a default for new test plans test plan that sets user expression '.*' and read box selected. 2) go through the existing test plans and set user expression '.*' and read box selected. Note, the permissions for the test RUNS are derived from the 'ANDing' of the permissions of the (sometimes multiple) test PLANS they are tied to.