This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 86212 - "Return to Issue" page resends attachment unnecessarily
Summary: "Return to Issue" page resends attachment unnecessarily
Status: RESOLVED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: collabnet (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-29 18:56 UTC by ssoong
Modified: 2009-11-08 02:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ssoong 2006-09-29 18:56:21 UTC
Steps:

1. I entered issue and pressed [Submit issue].
2. NB bugzilla assigned me the issue number 86211 and 
3.  returns with page encouraging me with links either to
3.1 return to issue 86211
3.2 attach
4. I chose attach to attach a jpeg.
5. NB bugzilla assigns an attachment number.

6.  returns with page similar to step 3, as well as,
6.1 a link to view the attachment I had attached.

7. Succumbed to temptation to click to view attachment 34709 [details].

8. NB bugzilla showed me the attachment but
   does not show me a link "return to issue 86211"

9. So I had to licked [Back] button, but because the page is dynamic
   the response was "page is not viewable".

10. Therefore, I pressed [refresh] as I was encouraged by the browser.

11. Good, I felt, NB Bugzilla now shows me the page from step 6.

12. But wait a minute the attachment number is now 34710, not 34709.

13. So I succumbed to tempatation again to verify attachment.

14. Repeat steps 9 - 12.

15. Oops, its now attachment 34711 [details].

16. I felt, "better not muck around with this anymore".
    Clicked return to issue 86211 and made the discovery
    I [more precisely, bugzilla] had attached too many copies.

It's not my fault - bugzilla made me do it.
Comment 1 ssoong 2006-09-29 18:58:48 UTC
9. So I had to licked 

should be 

9. So I had to click
Comment 2 ssoong 2007-01-12 16:54:52 UTC
I believe the way y'all have rearranged the page presentation has circumvented 
this problem from happening.

Should I close this request as resolved myself, or should I leave it to the NB 
high priest/priestess of this issue to close it?  
Comment 3 jcatchpoole 2007-01-15 13:00:28 UTC
Thanks :)  For reference you're free to close your own issues if you want in
future, assuming nobody else seems to think it should stay open.
Comment 4 Marian Mirilovic 2009-11-08 02:36:30 UTC
We recently moved out from Collabnet's infrastructure