basic questions about issue tracker integration

[Sascha Herpers <he...@wiso.uni-koeln.de>]

Hi,

I read some pages about issue tracker integration, but it's not exactly
clear to me, how it works. Maybe somebody could comment on the following:

I would like to document known bugs directly in the source code. The
issue tracker should read through the commited files and update it's
list of known bugs. Once a bug is resolved, the line with the bug
information should be removed. The issue tracker should figure out, that
if the lines with the bugs are gone, that the bug is resolved.
That's kind of like writing documentation directly into the source code
and extracting it with javadoc (or whatever).

Are issue trackers capable of this?

Are there good tutorials on how to integrate the issue trackers and on
how to use them?

Thanks,

	Sascha

-- 
_____________________________________________________________

    Sascha Herpers
    Universität zu Köln
    Seminar für Supply Chain Management und Produktion
    Albertus-Magnus-Platz
    50923 Köln

    E-Mail: herpers@wiso.uni-koeln.de
    Tel.:   (0221) 4 70 - 37 40
    Fax:    (0221) 4 70 - 51 40
    WWW:    http://www.scmp.uni-koeln.de
_____________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: basic questions about issue tracker integration

[Lutz Frommberger <Lu...@gmx.de>]

Sascha Herpers <he...@wiso.uni-koeln.de> wrote:
> I would like to document known bugs directly in the source code. The
> issue tracker should read through the commited files and update it's
> list of known bugs. Once a bug is resolved, the line with the bug
> information should be removed. The issue tracker should figure out, that
> if the lines with the bugs are gone, that the bug is resolved.
> That's kind of like writing documentation directly into the source code
> and extracting it with javadoc (or whatever).
> 
> Are issue trackers capable of this?

It's unclear to me what you mean with "issue tracker" - what do you expect
the issue tracker to do?

Compiling a list of bugs and todos from source code comments is exactly what
documentation tools like doxygen do. What additional functionality do you
search for?

regards,
-- 
Lutz Frommberger                   |  "Wenn ist das Nunstück git und
                                   |   Slotermeyer? Ja! ... Beiherhund
http://www.aussagekraft.de         |   das Oder die Flipperwaldt
pgp key on request                 |   gersput."    - Ernest Scribbler


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org