<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>
<span>
<div style="-en-clipboard:true;"><span style="line-height:
100%;">Hi All,<br>
<br>
</span></div>
<div style="-en-clipboard:true;"><span style="line-height:
100%;">I have created quite an amount bug reports related to
object/image anchoring. They current value of those is 0, as
they basically demonstrate nothing new. It are simply
different expressions/ examples/ consternations/ showcases
of the same underlying problem (as far I’m able to tell).</span></div>
<div style="margin-top: 1em; margin-bottom:
1em;-en-paragraph:true;" lang="en-US"><span
style="line-height: 100%;">However the might become handy if
someone some day decides to work on this. It will give QA
and they developer a number of test cases for analysis and
testing. And easier to running into them, compared to
creating them on demand; so more documentation of test
cases.</span></div>
<div style="margin-top: 1em; margin-bottom:
1em;-en-paragraph:true;" lang="en-US"><span
style="line-height: 100%;">They other view is of course that
i’m repeating myself, bloating the bugtracker with useless
reports/ samples wasting QA time (as the currently got to
formal conformation process) and ruining they QA stats
(UNCONFIRMED bugs).</span></div>
<div style="margin-top: 1em; margin-bottom:
1em;-en-paragraph:true;"><span style="line-height: 100%;">As
bugtracker is</span> <span style="line-height: 100%;">servicing</span><span
style="line-height: 100%;">the needs of Developers, it more
or less based on the desires of the developers.<br>
A)</span> <span style="line-height: 100%;">A</span><span
style="line-height: 100%;">re</span> <span
style="line-height: 100%;">repeated reports (variants)</span>
<span style="line-height: 100%;">of any use from developer
point of view</span> <span style="line-height: 100%;">(for
specific this case)<br>
B) If so, how can those they best be processed.</span> <span
style="line-height: 100%;">I like them</span> <span
style="line-height: 100%;">separate</span><span
style="line-height: 100%;">instead of posting them in one
bug report (</span><span style="line-height: 100%;">unpractical</span><span
style="line-height: 100%;">mess) or stacking them up to a
bug as duplicate (risk of getting lost).</span> <span
style="line-height: 100%;">T</span><span style="line-height:
100%;">hey could be</span> <span style="line-height: 100%;">placed</span>
<span style="line-height: 100%;">under separate meta within
anchoring wrap meta. However the meta is still reasonable
sized, so that urgent from my point of view.<br>
C) Is there a new category needed for those examples, as
numbers of they bugtracker don’t represent they actual
number of problems.</span> <span style="line-height: 100%;">Bugs
being set to NEW without being NEW in the sense of reporting
anything new.<br>
</span></div>
<div style="margin-top: 1em; margin-bottom:
1em;-en-paragraph:true;"><span style="line-height: 100%;">Sidenote:
I’m don’t intend to add more; as I think I covered they
terrain a pretty good (maybe even one or to duplicates)<br>
<br>
Regards,<br>
Telesto<br>
</span></div>
</span>
</p>
</body>
</html>