Bug 1321527 - Clone action doesn't copy the target release value of the original bug
Summary: Clone action doesn't copy the target release value of the original bug
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 5.0
Hardware: Unspecified
OS: Unspecified
high
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-28 08:06 UTC by Rony Gong 🔥
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-16 06:06:54 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1332795 0 medium CLOSED Clone action doesn't copy the component value of the cloned bug 2021-02-22 00:41:40 UTC

Internal Links: 1332795

Description Rony Gong 🔥 2016-03-28 08:06:15 UTC
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:

Comment 1 Jeff Fearn 🐞 2016-04-17 23:51:40 UTC
IMO this is not a bug, the bug should have to be triage before getting assigned to a target release.

Comment 4 Jeff Fearn 🐞 2016-04-18 06:15:39 UTC
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?

Comment 6 Rony Gong 🔥 2016-04-18 08:20:08 UTC
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

Comment 7 Rony Gong 🔥 2016-05-04 06:48:58 UTC
QA environment(5.0.2-rh5)
Result: Pass
Steps:
1.It could copy the original target release and milestone value to the new bug.


Note You need to log in before you can comment on or make changes to this bug.