RefStack should allow associating specific capabilities targets
Bug #1477392 reported by
Catherine Diep
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| refstack |
Fix Released
|
High
|
David Liu | ||
Bug Description
Since a user may have tested against a specific capabilities version and target program, we should allow users to associate these specifics to their test results
Then on the results-report page for their test run, the selected capabilities version and target program can default to what was selected.
Revision history for this message
| Paul Van Eck (pvaneck-z) wrote | #1 |
Revision history for this message
| Catherine Diep (cdiep) wrote | #2 |
| Changed in refstack: | |
| importance: | Undecided → Medium |
| Changed in refstack: | |
| status: | New → Confirmed |
| summary: |
- refstack-client should require cloud OpenStack release name + RefStack should allow associating specific capabilities targets |
| description: | updated |
| Changed in refstack: | |
| importance: | Medium → High |
| Changed in refstack: | |
| assignee: | nobody → David Liu (lzbj) |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to refstack (master) | #3 |
| Changed in refstack: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Perhaps allow users to pin a spec to an uploaded signed test result. For example, on the "My Results" page, a user can select what spec to associate their test results to, and this associating can be stored in the meta table. Then on the results-report page for their test run, the selected capabilities version can default to what was selected.