Bug 1153422 - The version,release,milestone is always in refresh status when change the product of bug whose original product only contain 1 component
Summary: The version,release,milestone is always in refresh status when change the pro...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 03:37 UTC by Rony Gong 🔥
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version: rh-bugzilla-5.0.3-rh2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 07:49:27 UTC
Embargoed:

Attachments (Terms of Use)

Description Rony Gong 🔥 2014-10-16 03:37:29 UTC 
Description of problem:
The version,release,milestone is always in refresh status when change the product of bug whose original product only contain 1 component

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

How reproducible:
Always

Steps to Reproduce:
1.Create a new product product_1 with only 1 component, but with some versions, milestones and releases.
2.Create a bug bug_1 of product product_1, save
3.Open the bug bug_1, select other product like "Beaker"

Actual results:
The version,release,milestone is always in refresh status after select other product for this bug.

Expected results:
The version,release,milestone value should be reset as the new product's setting after select other product for this bug.

Additional info:
Comment 1 Rony Gong 🔥 2015-05-20 07:58:16 UTC 
This bug still could be reproduced in build 4.4.9033-5
Comment 2 Jeff Fearn 🐞 2015-07-23 00:52:09 UTC 
Bumping this out of the sprints and decreasing severity as this will never affect us in production.
Comment 3 Jeff Fearn 🐞 2016-05-31 22:25:41 UTC 
Rony, does this happen in 5.0?
Comment 4 Rony Gong 🔥 2016-06-01 01:34:15 UTC 
(In reply to Jeff Fearn from comment #3)
> Rony, does this happen in 5.0?

This bug could not reproduce in 5.0 now.
Note You need to log in before you can comment on or make changes to this bug.