How to make forum support and acronis communication more effective.

a) It seems that users start topic after topic regarding the same issues.
The end result is us users nash away without actually accomplishing much of anything.

b) It seems that we users "assume" that if we post an issue with detail descriptions of a problem and end with "Acronis needs to fix this" then Acronis has been "notified". We tend to feel this way despite the fact the forum has thousands of posts and Acronis does not read let alone respond to every last post.

c) It seems that if a posted issue is resolved in a particular build - NOone in user community is notified. So the issue re-surfaces all over again with those users still in an older build.

d) It seems that we users have no idea if an issue has been assessed/reproduced by Acronis (or not). So us users nash away un-aware that acronis has taken investigation of the issue.

e) It seems that we users have no idea if recognized/reproducible issues are being prioritized/worked on. (or not). So we nash away un-aware that acronis has the bug defined and has prioritized its resolution.

f-z) ???

It seems to me can use this forum to address all these issues and more:

It WILL take some dicipline from us users on where to post (and where not to post) in this forum.
It WILL take a collection of forum MODs to enforce the forum rules - not necessarily be techinical support for active posts but enforce the "rules" of where to post, deleting /moving posts when needed ect.

As forum users I suggest we create a "sticky" topic called "User reported issues/bugs"

In this topic we do NOT discuss the actual issue.
Instead we insist that this topic only be post of after post of "User Incident REPORTS"
Each report MUST have one or more links into our forum where the messy details can be hashed out.

When the original issue poster knows of an update, or the forum mod is informed of some progress they can modify the original report or even close it.

ALL reports would follow the exact same template.
This topic would end up and post of nothing other what the template allows.

We would ask the forum mod to enforce this rule Deleting (or moving) whatever they see violates this rule.

The linked topic is fair game. Any user can post whatever they want into the linked topic.
Of course we can revise the template as needs occur but the point Is all postings will follow a standard format.
There are many advantages to this setup, one of which is any Acronis employee can get a handle on the reported bugs simply by reviewing a single Acronis topic. The Acronis employee can then post into the linked issue to ask questions/offer suggestions.
If the Acronis employee knows disposition detail then they, (or the forum mod), can enter that detail into the original report posting.

The standard sequece of events for us users would be:
step 0) if we are smart users then we do a search of the forum for our issue. when we do we may find that others have it too. If so we would get a hit either on the detail posting or the sticky/summary. Either of which points us into the correct topic to research and/or continue the discussion.
or
step 1) Start a new topic/post question.
step 2-n) Discussion within this detail topic ensues
step 3) Discussion spins itself toward this is a new bug and needs an incident report.
step 4) Posting of template is made into sticky.
step 5-n) Discussion continues - with possible inclusion of acronis support
Step 6) As the disposition of the issue progresses with time the sticky is update either by acronis support, original topic create or forum mod.

Here is my suggestion for a user report template:

SHORT 1 sentence title .....:
TI_Version..................:
TI_Build (use alt key)......:
Report Date.................:
Discussion_link(s)..........:
One paragraph description...:

remainder to be filled in by Acronis employees, or forum mod, or reporting author if they know these answers.

[] This report duplicates another closing this one.
Master/Original report reply number is ....:

Acronis disposition:
[] known issue (see tracking number below)
[] not an issue / intentional design closing report
[] Issue being reviewed/assessed: [assessment start date]
[] Issue Not reproducible topic closed: [closed date]
[] Issue resolved by user (see comment/feedback)
[] User is non-responsive to requests for information-Topic closed: [closed date]
[] Workaround to issue exists (see comment/feedback)
[] Closing this report with comment (see comment/feedback)
[] Misc (see comment/feedback)

Acronis tracking number........:
Resolved in TI_version/build...:

Acronis/Forum Mod feedback to users on this topic:
==================================================
date
Feedback
---------------------
date
Feedback
---------------------
date
Feedback
---------------------