Topic attributes "Solved" and "Won't Fix"

[Dave Rabelink]

FYI

When creating a topic, the topic owner is able to set/change the Topic attribute.
Also the topic owner can change the attribute afterwards.

At this moment there are two attributes to choose from:

• Solved
• Won't Fix

For instance, when a topic question or issue was solved, the one who created the topic can set the attribute to "Solved" afterwards.
The topic will show the Solved icon in the forum.

When the question or issue can not be solved, for instance OpenText responded that the defect will not be fixed, set the attribute to "Won't Fix".
The topic will show the WontFix icon in the forum.

To change the attribute afterwards: Click the edit button (having the pen icon at the right top location of the topic start post) and change/remove the attribute with the attribute combobox and save the post.

The forum admins are able to change any topic and set the attribute when needed.

[RainerE]

Hi Dave,

I will try to do this in the future.
But -as told in another thread- we will not test and use TD 7.4.5, but TD 7.5 (or TD 7.5.x) instead.
So it may take a while (some month) until I can say, that a bug is fixed (Solved).
For me, a bug is fixed (Solved) not a the time, OpenText released a version containing a fix for this bug.
For me, a bug is fixed after I have successfully tested the fix.

And because it makes a lot effort to use a new TD version (even if it is only a bugfix version like 7.4.5), we do not use each version provided.
We have to upgrade our development PCs, our deployment PC (which must be able to deploy all versions of our software still in use which means the need of building the software with different TD versions), our PCs for automated tests, our customer like test environment. And we have to tell our customer how to update their test environment, their prelive environment and their production environment (each two servers with a network installation of our software). We will change this to include the TD deployment files in our software instead of having a separate installation of the TD runtime module.

Regards,
Rainer

[Dave Rabelink]

So it may take a while (some month) until I can say, that a bug is fixed (Solved).
For me, a bug is fixed (Solved) not a the time, OpenText released a version containing a fix for this bug.
For me, a bug is fixed after I have successfully tested the fix.

I understand that. Here also, new (patch) versions have to be tested and evaluated which takes time.
Indeed, sometimes a fix by OpenText after testing reveals it not being fixed or only partly and sometimes even break other stuff.

As for the indicators on this forum (solved attribute) it is hard to keep track which ones are actually part of a new release and also have been tested to be really fixed.
To avoid that reported defects on the forum do not get attention, it is best to set the forum topic to solved at the moment OpenText indicates it is fixed as part of a release.
(based on the releasenotes fix list)

When the defect is actually fixed and tested ok, when no "Solved" indicator was set on the topic, this topic will most probably not get the "Solved" attribute afterwards.
Others just reading the topic assume OpenText did not handle the defect in a release yet when no "Solved" indicator is set on the topic and no post was added to indicate in which version the defect was fixed by OpenText.

So when a topic has been set to "Solved" and sometime later someone finds that this defect was not solved, this can be reported in that topic and the solved indicator removed.
(probably the defect will be reopened or a new defect registered).

As default, at the moment a new version or patch is released, I adapt the fixlist and skim through the list and set the topic attribute to "Solved" and post in the topic which version in was supposedly solved.
But any topic owner can do this when they see their topic being solved or remove the attribute when the defect was not solved after testing.