"Relative index" field on "Add test result" admin form is not documented
Bug #740639 reported by
Alexander Sack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LAVA Dashboard (deprecated) |
Fix Released
|
Low
|
Zygmunt Krynicki | ||
Bug Description
"Relative index" field on "Add test result" deserves some docs in admin interface.
Related branches
lp://qastaging/~zyga/lava-dashboard/0.3c7
- Linaro Validation Team: Pending requested
-
Diff: 794 lines (+441/-63)19 files modifiedNEWS (+96/-4)
dashboard_app/__init__.py (+1/-1)
dashboard_app/admin.py (+2/-2)
dashboard_app/models.py (+55/-14)
dashboard_app/tests/models/sw_package.py (+8/-0)
dashboard_app/tests/models/test_result.py (+2/-3)
dashboard_app/urls.py (+5/-1)
dashboard_app/views.py (+22/-0)
dashboard_app/xmlrpc.py (+1/-1)
dashboard_server/settings/common.py (+4/-0)
dashboard_server/templates/dashboard_app/api.html (+18/-15)
dashboard_server/templates/dashboard_app/bundle_list.html (+68/-0)
dashboard_server/templates/dashboard_app/bundle_stream_list.html (+4/-2)
dashboard_server/templates/dashboard_app/reports/gcc_benchmark.html (+4/-4)
dashboard_server/templates/dashboard_app/test_result_detail.html (+25/-1)
dashboard_server/templates/dashboard_app/test_run_detail.html (+1/-1)
dashboard_server/templates/dashboard_app/test_run_hardware_context.html (+20/-1)
dashboard_server/templates/dashboard_app/test_run_list.html (+73/-12)
dashboard_server/templates/dashboard_app/test_run_software_context.html (+32/-1)
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in launch-control: | |
| assignee: | nobody → Zygmunt Krynicki (zkrynicki) |
| importance: | Undecided → Low |
| milestone: | none → 0.3c7 |
| status: | New → Confirmed |
| Changed in launch-control: | |
| status: | Confirmed → Fix Committed |
| Changed in launch-control: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is an implementation detail and I'm unsure how it should be presented in the admin panel (if at all) but we can document the semantics of this field. Again as with othe similar bugs it's not something you would create manually.