Closed GoogleCodeExporter closed 8 years ago
I'll take a look at why that is happening. In the mean time, you could just
remove the
svn property:
bugtraq:number = true
This will allow you to check-in without having to manually clear the input text.
Original comment by Grig...@gmail.com
on 17 Sep 2009 at 5:04
Two questions:
1. What version of TortoiseSVN are you using?
2. Can you copy/paste your svn properties or take a screen shot for me?
Original comment by Grig...@gmail.com
on 17 Sep 2009 at 5:34
I got it working (sort of); I found the number properties after I wrote the
error
report and thus managed to access several issues at once.
What I am havin troubles with, though, is getting the whole issue reference
clickable and not only the number. If I have a JIRA project named "TEST" and
hence
an issue "TEST-1", the clickable link to the JIRA issue is only the number "1",
not
the whole string which is a bit of a bother.
I enclose my properties for this particular project as a screen shot. My
TortoiseSVN
particulars are as follows:
TortoiseSVN 1.6.2, Build 16344 - 32 Bit , 2009/05/09 13:46:29
Subversion 1.6.2,
apr 1.3.3
apr-utils 1.3.4
neon 0.28.4
OpenSSL 0.9.8k 25 Mar 2009
zlib 1.2.3
Original comment by koenigs...@gmail.com
on 18 Sep 2009 at 11:12
Attachments:
I think the problem may be the regex. Try the following: "Test-\d+". My guess
is that TSVN is grabbing
the first match group instead.
Original comment by Grig...@gmail.com
on 18 Sep 2009 at 2:26
I tried that regexp and that made matters only worse :-)
There is no clickable link any more, and the issue reference was duplicated.
This is
what I ended up with in the checkin comment:
"TEST-TEST-1
Working TEST-1 : Skapa en CM-plan"
After selecting the "TEST-1" issue...
I agree though that the problem lies in the regexp; I tried some variations and
ended
up with different results but have so far not come up with anything that works.
Original comment by koenigs...@gmail.com
on 24 Sep 2009 at 11:19
Configuration issue with subversion.
Original comment by Grig...@gmail.com
on 16 Oct 2009 at 2:51
Original issue reported on code.google.com by
koenigs...@gmail.com
on 10 Sep 2009 at 10:53