Bug 1317358 - When chang product of a bug, it can't refresh the assosiate version, target release and milestone
Summary: When chang product of a bug, it can't refresh the assosiate version, target r...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-14 05:32 UTC by Hui Wang
Modified: 2018-12-09 06:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-04 01:34:11 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1323915 0 medium CLOSED target_release web service needs reimplimenting 2021-02-22 00:41:40 UTC

Description Hui Wang 2016-03-14 05:32:17 UTC 
Description of problem:
When change the product of a bug, it can't refresh the associated version, target milestone, target release. E.g, change a bug from product rhel 6 to rhel7, the version selector still contains 6.0, 6.1,.... That should be refreshed to rhel7 version (7.0, 7.1,...)

Version-Release number of selected component (if applicable):
version 5.0.2.rh2

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

It should be refresh the associated version, target release and milestone.

Additional info:
Comment 1 Hui Wang 2016-04-18 14:46:41 UTC 
Verified this issue.
Version 5.0.2.rh4

Version, milestone and target release will trigger an ajax call. Version and milestone fields will return the associated data, but the target release filed can't return the associated data due to bug 1323915.

In this case, qe will change the status to VERIFIED. After 1323915 is resolved, if the target release still can't return data, qe will file a new bug for that.
Note You need to log in before you can comment on or make changes to this bug.