Bug 92694 - Need way to track irreproducable bugs, rather than declaring them "resolved" invalid.
Summary: Need way to track irreproducable bugs, rather than declaring them "resolved" ...
Status: RESOLVED MOVED
Alias: None
Product: QA Tools
Classification: Unclassified
Component: General (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-12 17:25 UTC by MarjaE
Modified: 2016-10-15 05:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MarjaE 2015-07-12 17:25:44 UTC
As of now, bugs which can't easily be documented and reproduced are declared invalid. Some of these are severe bugs, and may destroy people's work.

One of these that I encountered meant that files which showed fine on one computer would lose embedded images, resize the images, or replace them with other images on another computer. I couldn't document this because the files were too large to submit, and because it would be hard to compare how it displayed properly on one computer, and improperly on another, using a third. I give that as an example.

I am not sure where to file bugs with the bug report procedures.
Comment 1 Aron Budea 2016-10-15 05:18:34 UTC
Bug statuses aren't final, if you feel like contesting status with a compelling argument, you're welcome to. For example, big files can be uploaded to other file sharing services.

On the other hand, having reports open for bugs that have no chance of being reproduced serves little purpose, developers can't work on the issue because of the lack of details. If for such a bug the reporter or someone else hopes they would be able to provide additional details in the future, or need guidance, the bug report should stay open, otherwise there's no point.

If you think it's a severe bug (or a valid bug), please don't give up on it, and work with others on having it reproduced.
I'm closing this report as MOVED, as such issues belong on Redmine [1], but I hope this reply provides guidance for the future.

[1] https://redmine.documentfoundation.org/