Bug 1317461

Summary: [RFE] Rename "Edit" button in Storage Domains tab to "Manage Domain"
Product: [oVirt] ovirt-engine Reporter: Yaniv Lavi <ylavi>
Component: RFEsAssignee: Allon Mureinik <amureini>
Status: CLOSED CURRENTRELEASE QA Contact: Natalie Gavrielov <ngavrilo>
Severity: low Docs Contact:
Priority: low    
Version: 3.6.0CC: acanan, agkesos, amureini, bugs, dcadzow, ebenahar, ederevea, ehildesh, gklein, iheim, lsurette, ngavrilo, rbalakri, Rhev-m-bugs, rmcswain, scohen, sherold, srevivo, tnisan, trichard, ykaul, ylavi
Target Milestone: ovirt-4.0.0-alphaKeywords: FutureFeature, UserExperience
Target Release: 4.0.0Flags: rule-engine: ovirt-4.0.0+
gklein: testing_plan_complete-
ylavi: planning_ack+
rule-engine: devel_ack+
acanan: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt 4.0.0 alpha1 Doc Type: Enhancement
Doc Text:
With this release, the "Edit" button under the Storage tab has been renamed "Manage Domain" to comply to the product's standard.
Story Points: ---
Clone Of: 1176217 Environment:
Last Closed: 2016-07-05 07:55:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1176217, 1393597    
Attachments:
Description Flags
Screenshot of the new button none

Description Yaniv Lavi 2016-03-14 10:15:20 UTC
Rename to "Manage Domain" and not "Manage Storage Domain" in order to comply with existing buttons named "New Domain" and "Import Domain".

Comment 1 Natalie Gavrielov 2016-04-10 15:47:46 UTC
Verified, ovirt-engine-4.0.0-0.0.master.20160406161747.gita4ecba2.el7.centos.noarch

Comment 3 Allon Mureinik 2016-05-23 08:05:34 UTC
Derek - needinfoing you as I'm not sure who's the right POC for this question, feel free to reassign it.

This RFE is about changing the label of the button in the Storage tab's menu (see attachment). I don't think this needs to be documented directly ("RHEV 4.0 changes the label of the button"), but if we have screenshots/references in the doc, it should be addressed.

Comment 4 Allon Mureinik 2016-05-23 08:06:59 UTC
Created attachment 1160474 [details]
Screenshot of the new button

Attached screenshot referenced in comment 3

Comment 5 Derek 2016-06-06 12:10:00 UTC
Ack. Assessing doc impacts now.

Comment 6 Tahlia Richardson 2016-06-22 05:51:01 UTC
Hi,
The requires_doc_text flag was set to '?' but no draft text was provided. Does this bug require doc text for release notes?
If so, please provide draft text.
If not, please change the flag to '-'.

Comment 7 Allon Mureinik 2016-06-22 06:30:30 UTC
(In reply to Tahlia Richardson from comment #6)
> Hi,
> The requires_doc_text flag was set to '?' but no draft text was provided.
> Does this bug require doc text for release notes?
> If so, please provide draft text.
> If not, please change the flag to '-'.

Hi Tahila,

Comment 3 raised a question (needinfoed on Derek) about the documentation requirements for this BZ. I'd be happy to supply any required information, but we need to decide what/how this is going to be documented first.

Comment 8 Sandro Bonazzola 2016-07-05 07:55:34 UTC
oVirt 4.0.0 has been released, closing current release.

Comment 9 Derek 2016-07-05 10:44:32 UTC
Allon, the documentation impact of the bug was addressed in the RHEV 4.0 doc content plan.  However, having doc text for release notes is another matter and should be provided without needing input from me.

Comment 10 Allon Mureinik 2016-07-18 13:33:07 UTC
(In reply to Derek from comment #9)
> Allon, the documentation impact of the bug was addressed in the RHEV 4.0 doc
> content plan.  However, having doc text for release notes is another matter
> and should be provided without needing input from me.
Understood, thanks. Doctext provided as per the normal process.

Comment 11 Derek 2016-07-18 13:47:52 UTC
(In reply to Allon Mureinik from comment #10)
> (In reply to Derek from comment #9)
> > Allon, the documentation impact of the bug was addressed in the RHEV 4.0 doc
> > content plan.  However, having doc text for release notes is another matter
> > and should be provided without needing input from me.
> Understood, thanks. Doctext provided as per the normal process.

Thanks Allon!