Re: Issue 38 in gurtle: Help with the new issue tracker integration

[gur...@googlecode.com]

Comment #7 on issue 38 by futnucks: Help with the new issue tracker
integration
http://code.google.com/p/gurtle/issues/detail?id=38

The script is broken as far as I can tell right now.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[gur...@googlecode.com]

Comment #8 on issue 38 by tortoise...@gmail.com: Help with the new issue
tracker integration
http://code.google.com/p/gurtle/issues/detail?id=38

here's a library which could be used:
http://www.codeproject.com/KB/library/google-code-issue-tracker.aspx

[gur...@googlecode.com]

Comment #9 on issue 38 by azizatif: Help with the new issue tracker
integration
http://code.google.com/p/gurtle/issues/detail?id=38

Thanks for the article reference, @tortoisesvn! I'll check it out and
hopefully it will
certainly help with some of the time constraints I have in terms of putting
this issue
to rest especially now that there is an API.

[gur...@googlecode.com]

Comment #10 on issue 38 by azizatif: Help with the new issue tracker
integration
http://code.google.com/p/gurtle/issues/detail?id=38

If we re-open issue 16 and solve it over the official API, does this one
still make
sense or needed? It seems more like a nice-to-have.

[gur...@googlecode.com]

Comment #11 on issue 38 by tortoise...@gmail.com: Help with the new issue
tracker integration
http://code.google.com/p/gurtle/issues/detail?id=38

I like to close issues without an additional dialog popping up after a
commit. So
having the issue closed by using the correct sentence in the log message is
something
I'd like to keep.

And on another note: there should be an option to disable the dialog after
a commit,
at least if the log message already contained a "special reference" to an
issue.
Because right now, I always have to just cancel that dialog since I don't
use it.

[gur...@googlecode.com]

Comment #12 on issue 38 by austin_h...@yahoo.com: Help with the new issue
tracker integration
http://code.google.com/p/gurtle/issues/detail?id=38

FWIW, one of my projects uses Google for problem tracking and Gitorious for
hosting.
I definitely want Gurtle to manage the tickets, since non of the comments
are visible
to Google.

[gur...@googlecode.com]

Comment #13 on issue 38 by MALfunct...@gmail.com: Help with the new issue
tracker integration
http://code.google.com/p/gurtle/issues/detail?id=38

I've had great success getting bidirectional linkage working with the
following SVN
properties:

bugtraq:append = false
bugtraq:label = Issue ID
bugtraq:message = Update issue %BUGID%
bugtraq:number = true
bugtraq:url = http://code.google.com/p/REPLACE-ME/issues/detail?id=%BUGID%
bugtraq:warnifnoissue = true

I have to type out the issue changes manually before my commit message
("Status: Fixed", etc.), but it would be nice if Gurtle provided a UI for
this.

See http://code.google.com/p/support/issues/detail?id=797#c14 for more
details.

[gur...@googlecode.com]

Comment #14 on issue 38 by tortoise...@gmail.com: Help with the new issue
tracker integration
http://code.google.com/p/gurtle/issues/detail?id=38

You can use the following string for bugtraq:logregex

(([Ii]ssues?:?(\s*(,|and)?\s*#\d+)+)|(\((Fixes|Closes|Resolves) issue
#?\d+\))|((Fixes|Closes|Resolves) issue #?\d+\.)|(([\r\n]|^)(Fixes|Closes|
Resolves) issue #?\d+([\r\n]|$))|(^Update issue #?\d+:?([\r\n]|$)))

(all on one line of course).