Bob Scheifler wrote:
Mark Brouwer wrote:
2) some people fill in the fix versions field just when they resolve the
issue, others use it for scheduling purposes as well so all planned
issues show up in the roadmap and release notes reports.
Seems pretty poor that there aren't two distinct fields.
(Could another field be easily added?)
I'm of the
latter category and would love to do this, but it requires issue
scheduling.
If you use it for scheduling, how do you make sure in the end that
you know what was fixed in a given release?
Through the resolution field. This represents that state the issue is
in. So an issue with a fixed version/s field set to one or more versions
with a non-final resolution represents a schedule. A final resolution
of fixed e.g. indicates the versions where the issue was fixed.
I hope this answers your first remark too (another field can be created
but I haven't seen that before, which of course doesn't say anything).
--
Mark
