Where to submit bug reports

This forum is currently in read-only mode.
  • Please submit all bug reports to the Sourceforge so I can keep track of them:

    SourceForge bug tracker

    If you wish to discuss a bug, you can still use the forums, but make sure you first submit the bug to the tracker.

  • I have now submitted a bunch of bug reports to the bug tracker. However, I still have a lot of UI improvement suggestions and things like that. Should I send them to bug tracker or here?

  • I think we should keep bug reports on the tracker and discuss suggestions and changes on the forum here.

  • I really think you should just open a dedicated area here on the forum for bug reports. I find that sourceforge is pretty bad to use, unless there are features your end that make it easier. <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />

  • Well, sourceforge keeps things organized better than any forum could. But I agree, while the project is still small and young, and while these forums are significantly more active than the forge, I've been attempting to confirm bugs here in Tech/Help before making a report on the forge.

  • Well, Sourceforge keeps track of open/closed bugs, closed bugs which are commented on are reopened, tracks bug resolutions, keeps statistics, etc. A forum would be adequate, but I think could get confusing after a while... I think the current tracker is fine.

  • Just a note about bug reports: please make sure every bug you find goes on the tracker (link above). Even if you post it to the forum and I say I'll take a look, it would be useful if you also submit a tracker item. Forum posts get drowned out by the general discussion, and the tracker is an organised place to deal with all reports. Cheers! <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />

  • Oh, i didn't think about that! I very often post threads where i check if things really is a bug, or just me doing something wrong. But when i get the answer it is a bug i almost never submit it to the bug tracker... Will do that from now on.

  • For some bug reports, it might be useful to require uploads of .cap files demonstrating said bugs.

  • We have a message asking users do put up a .cap, as it is very important for most bugs to quickly reproduce it <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />.

  • Also, the last bug report I submitted the .cap was above the size limit so I had to upload it via a third party site and just link to it. Maybe that's a good enough reason not to require the upload.

  • If Sourceforge gets overloaded with bug-reports, it might be an idea to first post the bug-finding in a bug-topic on this forum, to let the community, if possible, verify if it is a bug.

    More experienced Construct users might recognize "false bug-reports" this way.

  • No, please don't make forum threads for bugs. They only need to be in one place, on the bug tracker. It wont get "overloaded" - it can handle thousands of reports just fine - and us devs regularly go through and administer things like whether it's really a bug, who it's assigned to, the open/closed status, pending queries, email updates and statistics. There are some fairly old reports on there, but with an average of 3 bugs opened a day through January, it's hard to keep on top of everything at once - and we know they're still there and marked open, so we do eventually come back and fix them.

  • ..however, if you have posted a bug on the tracker which you aren't sure about 100% or want feedback from other users on, then it's fine to create a thread <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • No, please don't make forum threads for bugs. They only need to be in one place, on the bug tracker. It wont get "overloaded" - it can handle thousands of reports just fine - and us devs regularly go through and administer things like whether it's really a bug, who it's assigned to, the open/closed status, pending queries, email updates and statistics. There are some fairly old reports on there, but with an average of 3 bugs opened a day through January, it's hard to keep on top of everything at once - and we know they're still there and marked open, so we do eventually come back and fix them.

    I understand Sourceforge works better with tracking bugs than a forum post.

    The purpose of my proposal was only to shift workload from the developers to the community users, so that devs have less bug-checking to do and only receive more "real" bugs.

    If in the future I am not sure if I have found a bug, I will post it -as with all bugs- on the tracker and on the forum. Thanks.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)