Red Hat Bugzilla – Bug 433500
Bugzilla 3.2 missing "Private in Issue Tracker" option
Last modified: 2013-06-23 22:17:58 EDT
Description of problem: When adding a comment to a BZ, there's a check-box for "Private in Issue Tracker" in addition to "Private" and "Add Me to Cc List". The "Private in Issue Tracker" option is missing when adding an attachment to the BZ. To make an attachment private in Issue Tracker, one can either make the attachment private and later remove the private flag, or one can leave it public and later click the lock icon in Issue Tracker to make it private (however, with the 2nd option, the customer gets an email). Both of these options are a bit clumsy. Can the "Private in Issue Tracker" option be added to the attachment screen? Version-Release number of selected component (if applicable): Bugzilla 2.18 How reproducible: Every time Steps to Reproduce: 1. Link an Issue Tracker to a BZ 2. Create an attachment to the BZ Actual results: "Private in Issue Tracker" check-box is missing. Expected results: "Private in Issue Tracker" check-box should be available. Additional info:
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2.
Actually, with BZ 3.2, the "Private in Issue Tracker" option is completely gone -- both for comments and attachments -- so now if I want a private comment in Issue Tracker but public in BZ, I have to a) click the private check-box b) commit the comment/attachment c) undo the private check-box for the just-submitted-comment/attachment d) commit again
We decided that Issue Tracker would handle this logic on it's end. Bugzilla sends the comment and all other information that Issue Tracker needs to make the decision on whether the comment is public/private. That is why the checkbox is no longer available. https://engineering.redhat.com/rt3/index.html?q=13896 Please comment/reopen the RT ticket if you have feedback on this issue.