Hide Forgot
Description of problem: Clone action doesn't copy the target relese value of the cloned bug Version-Release number of selected component (if applicable): 5.0.2.rh2 How reproducible: 100% Steps to Reproduce: 1.Create a bug with target release set 2.Clone this bug with same product 3.Check the target reelse field value Actual results: Not same as the cloned bug Expected results: Same as the cloned bug Additional info:
IMO this is not a bug, the bug should have to be triage before getting assigned to a target release.
Hi Rony, can you find out what happens when a non-redhat account tries to clone a RHEL bug that has all acks set and a target release set?
1. Create a RHEL7 bug, with target release set and all view-able flags set as '+' 2. Login by non-redhat account, then clone this bug, checking in the clone bug page: ==> target release is null ==> All flags value is null
QA environment(5.0.2-rh5) Result: Pass Steps: 1.It could copy the original target release and milestone value to the new bug.