Bug 873117

Summary:	Doc Type is not persisted after "Save Changes"
Product:	[Community] Bugzilla	Reporter:	Karel Piwko <kpiwko>
Component:	Creating/Changing Bugs	Assignee:	Simon Green <sgreen>
Status:	CLOSED NOTABUG	QA Contact:	tools-bugs <tools-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2	CC:	ebaak
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-05 19:27:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karel Piwko 2012-11-05 07:47:24 UTC

Description of problem:

When changing Doc Type of the issue, the change is not persisted.

Version-Release number of selected component (if applicable):


How reproducible:

Always.


Steps to Reproduce:
1. Open a bug (https://bugzilla.redhat.com/show_bug.cgi?id=868980)
2. Change Doc Type from "Bug Fix" to "Known Issue"
3. Save Changes
  
Actual results:

Page is reloaded, mail is sent and Doc Type remains "Known Issue"

Expected results:

Page is reloaded, mail is sent and Doc Type is "Known Issue"

Additional info:

Comment 1 Simon Green 2012-11-05 12:01:00 UTC

This is by design. You need to make a change to the doc text field for the change to the doc type to save. A tip mentioning this is part of bug 852325.

  -- simon

Comment 2 Karel Piwko 2012-11-05 14:56:10 UTC

Thanks Simon, but this approach does not make any sense to me. If I already have existing doc text and issue has moved from "Known Issue" into "Fixed bug", you want me to edit issue 2 times? E.g. Change doc text and change doc text back to original?

Or what workflow do you propose?

Comment 3 Simon Green 2012-11-05 19:27:34 UTC

(In reply to comment #2)
> Thanks Simon, but this approach does not make any sense to me. If I already
> have existing doc text and issue has moved from "Known Issue" into "Fixed
> bug", you want me to edit issue 2 times? E.g. Change doc text and change doc
> text back to original?

That wouldn't achieve what you want. When you change the doc text back to the original (white space excepted), the doc type will change back to what was before too.

> Or what workflow do you propose?

Please talk to the ECS team about this, since they have requested the doc type and doc text fields be set up this way. The original specification is in bug 798022.

  -- simon