Hi,
an issue is a good issue if it has only one issue ID. Usually the first
issue describes the problem and gives itself an ID. Other duplicate
issues to this ID need to be closed as duplicates.
But there are exceptions:
Sometimes it's needed to have issues to be fixed on several codelines.
In this case for each codeline there's an issue (with a target).
Sometimes there are multiple cloned issues that represent a task for
several people within an 'i-team' (integration team of a new feature
that contains development, QA, documentation, user experience and maybe
others).
Sometimes there's an issue that has the better description than the
first issue that has been written for this problem. In such a case
please do not close the issue if a developer is already working on it...
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
