Bug 1336179 - [RFE] - Add feature documentation to oVirt
Summary: [RFE] - Add feature documentation to oVirt
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Documentation
Version: 3.6.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-15 09:31 UTC by Fabrice Bacchella
Modified: 2023-08-03 07:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-03 07:09:07 UTC
oVirt Team: Docs
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-37604 0 None None None 2023-01-16 10:12:58 UTC

Description Fabrice Bacchella 2016-05-15 09:31:38 UTC
A lot of pages of features are still the page that where using during preparation of this feature.

It's hard to now for the user if this feature is really implemented, if the implementation is really what is documented, and it add noise when trying to read it.

Look for example at :
http://www.ovirt.org/develop/release-management/features/storage/importstoragedomain/

It starts with:
Today, oVirt supports importing ISO and Export Storage Domains, however, there is no support for importing an existing Data Storage Domain.

So one might stop reading at this line, thinking it's a missing feature. Even if he continues, there is a lof of mockup, that confort him in the idea that's a work in progress.

He as to check the 'current status' to know that is really implemented. But were the mockup updated ? They should be replaced with real screen shots.

Comment 1 Casper (RHV QE bot) 2023-01-16 10:31:03 UTC
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).

Comment 2 Sandro Bonazzola 2023-08-03 07:09:07 UTC
No updates since the bug was opened 7 years ago, closing as won't fix.
If still relevant please open an issue on https://github.com/oVirt/ovirt-site/issues


Note You need to log in before you can comment on or make changes to this bug.