| Summary: | Clone action doesn't copy the target release value of the original bug | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Rony Gong 🔥 <qgong> |
| Component: | Creating/Changing Bugs | Assignee: | Jeff Fearn 🐞 <jfearn> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 | CC: | huiwang, jmcdonal, mtahir, qgong |
| Target Milestone: | 5.0 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-16 06:06:54 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: | |
|
Description
Rony Gong 🔥
2016-03-28 08:06:15 UTC
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. |