How does a forum topic become a bug report?

[Paolo F Cantoni]

Hi,

I notice that sometimes the Sparxians monitor the forum and interject the statement that they are going to fix something mentioned in an item.

Is there anything formalised for this?  Or do we have to formally submit a bug report for every forum item where we identify an anomaly or defect?

Paolo

[KP]

There's a few of us that informally scan the forums when we have a spare moment, and if we notice a thread about a bug on a piece of code that we're familiar with, we will probably have a go at fixing it.

However, some of us never look at the forum so will never know about the problems being reported unless a bug report  appears in the support inbox.

[Paolo F Cantoni]

So would the best approach be to submit a bug report referencing the link to the forum item?  There's often a lot of useful discussion in the item that may have a bearing on the anomaly.

Paolo

[Bruno.Cossi]

Hi Paolo,

on occasion we have had a good communal action, when someone would bring up a bug or a new requirements, a discussion would start, and once everyone agreed on what solution would we like, one of the users would submit the bug report/feature request to Sparx. It seemed to work to everyone's satisfaction.

Thanks,
Bruno

So would the best approach be to submit a bug report referencing the link to the forum item?  There's often a lot of useful discussion in the item that may have a bearing on the anomaly.

Paolo

[thomaskilian]

I have sent bugs to the support address whenever I was (quite) sure that  the bug was not me I have an average of about 1 bug per month (many of them tiny or of minor priority). Sparx usually fixed these bugs with the next release. This is outstanding! And so far I did not have the impression that quality has decreased

[mikewhit]

Same here - I have reported functional and user interface defects, and hiccups/typos in the Help documentation, and they have all been rectified within one or two releases (except one, to do with package test cases, they said they had fixed and was still present, a release schedule problem I think !)

Also, clear-cut deficiencies in functionality reported for 'improvements' have had a response from someone saying if it would be incorporated, or if not, why not.

Some things do take a little longer - some problems in the code generation areas, or DDL for a specific DB, but these are usually not major, just would be nice to get them dealt with !

One person's "must-have" is another person's "nice-to-have", so I guess they must be forever adjusting priorities of new features, rationalisations and bug fixes ...