Bug 197098

Summary: cannot attach file when creating a new BZ
Product: [Community] Bugzilla Reporter: Jeff Bastian <jmbastia>
Component: Bugzilla GeneralAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-11-07 16:04:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Bastian 2006-06-28 15:15:13 UTC 
Description of problem:
When creating a new BZ, I cannot attach a file to the BZ.  I fill in all the
fields in the "Create Attachment" section of the BZ but when I click "Commit"
and look at the new BZ, my attachment isn't there.  After the BZ is created, I
can attach a file.

This may be related to BZ 197096; I often have to re-login to Bugzilla and it's
possible that the attachment information is lost when I have to enter my name &
password again.  (Fortunately the rest of the BZ text isn't lost, but just in
case I've started to copy-and-paste the text to a local file before hitting Commit.)

Version-Release number of selected component (if applicable):
Bugzilla 2.18-rh

How reproducible:
Very often

Steps to Reproduce:
1. Create a new BZ
2. Try to attach a file
3. Click Commit button
  
Actual results:
The file was not attached to the BZ

Expected results:
The file should be attached to the BZ

Additional info:
This may be related to BZ 197096
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=197096
Comment 1 David Lawrence 2008-09-16 16:54:40 UTC 
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.