View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003759||mantisbt||attachments||public||2004-04-22 10:19||2019-03-05 16:47|
|Target Version||Fixed in Version|
|Summary||0003759: Duplicate bug is created when resubmitting after file upload failure|
If you try to upload a file type that is not allowed, you get an error message that indicates the failure and says click the back button to correct the failure. When creating a new bug, clicking back, correcting the problem, and resubmitting creates a duplicate bug.
|Tags||No tags attached.|
|related to||0014113||new||Poor error handling when attaching multiple files and at least one upload fails|
|has duplicate||0006623||closed||dregad||error message when uploading a.png, followed instructions = double post|
|has duplicate||0006961||closed||atrol||Duplicate entry of reports, if an error appears with an attachment|
|has duplicate||0013296||closed||dregad||bug tracking system - if submit file, can never get out of bug you are in, submits dupes|
|has duplicate||0012860||closed||dregad||issues with document attachment|
|has duplicate||0013764||closed||dregad||Missing error notification when creating new issue and uploading file larger, than is mantis limit|
|has duplicate||0019519||closed||atrol||Upload file too large, going back causes dupe issue|
|has duplicate||0019822||closed||atrol||On uploading an image of size greater than the allowed size, multiple copies of the bug are created|
|has duplicate||0021104||closed||atrol||Création automatique de doublon si erreur sur taille PJ|
|related to||0005228||closed||dregad||Attaching multiple files in one go.|
|related to||0016952||new||When reporting issue receive error on custom field, but issue is still created|
|related to||0021801||closed||cproensa||File attachment GUI allows larger files than permitted|
|related to||0022588||closed||cproensa||Oversize upload is now skipped with no Message prompted|
Hello, is there a solution for this issue?
I want to point out that when uploading an unsupported attachment, the falsely created issue won't cause any emails to be sent, even if you have enabled email notifications for new issues.
Attachment upload problems are by far the most common errors to be encountered on my issue tracker, so I often get these duplicate issues, so it would be great to see this being addressed.
What is the desired behaviour, when a file upload fails?
Create the issue, but skipping the failed attachment, and possibly, showing a warning?
I would personally prefer a complete failure (just like when a mandatory field is not populated), but the other option would be fine too - and a warning would definitely be required in this case..
There is a problem though.
If file storage were independent of bug ids, and "temp" files could be uploaded, at that point you could easily fail before creating the issue, or manage the errors more gracefully.
Without drastic changes in file api, at the moment seems easier to manage the error, show a warning to the user, and skip the file.
another (complex) solution would be implementing drafts. As part of other functions that may provide, a draft would serve as a preliminary bug report, and a holder for temporary uploaded files.
Exactly the reason why I haven't fixed this yet ;-)
But if you want to go ahead and implement the warning option, that's fine with me.
As a user, I would also very much prefer to solve it this way, since form input data can easily be lost depending on server configurations and the like when using the back button.
|2004-04-22 10:19||nauman||New Issue|
|2011-01-19 02:25||atrol||Relationship added||related to 0006623|
|2011-01-19 02:42||atrol||Relationship added||has duplicate 0006961|
|2011-11-26 14:11||dregad||Category||bugtracker => attachments|
|2011-11-26 14:11||dregad||Summary||file upload failure message misleading => Duplicate bug is created when resubmitting after file upload failure|
|2011-11-26 14:12||dregad||Relationship replaced||has duplicate 0006623|
|2011-11-26 14:13||dregad||Relationship added||has duplicate 0013296|
|2011-11-26 14:23||dregad||Relationship added||related to 0005228|
|2011-11-26 14:24||dregad||Relationship added||has duplicate 0012860|
|2011-11-26 14:24||dregad||Status||new => confirmed|
|2012-01-17 13:02||dregad||Relationship added||has duplicate 0013764|
|2012-01-17 13:06||dregad||Note Added: 0030931|
|2012-12-19 19:24||dregad||Relationship added||related to 0014113|
|2013-02-05 14:01||juliexn||Note Added: 0035035|
|2014-01-12 17:27||j_schultz||Note Added: 0039027|
|2014-01-12 17:27||j_schultz||Note Edited: 0039027||View Revisions|
|2014-02-12 03:22||dregad||Relationship added||related to 0016952|
|2015-03-18 12:36||atrol||Relationship added||has duplicate 0019519|
|2015-06-09 07:33||atrol||Relationship added||has duplicate 0019822|
|2016-02-08 07:24||cproensa||Note Added: 0052486|
|2016-02-08 08:10||dregad||Note Added: 0052487|
|2016-02-08 11:21||cproensa||Note Added: 0052488|
|2016-02-08 12:35||dregad||Note Added: 0052489|
|2016-02-08 13:27||j_schultz||Note Added: 0052490|
|2016-06-13 10:18||atrol||Relationship added||has duplicate 0021104|
|2019-03-05 16:46||cproensa||Relationship added||related to 0021801|
|2019-03-05 16:47||cproensa||Relationship added||related to 0022588|