[JIRA] (JENKINS-14542) Issue ID Pattern no longer working

2013-03-14 Thread s.sog...@gmail.com (JIRA)















































sogabe
 resolved  JENKINS-14542 as Fixed


Issue ID Pattern no longer working
















Change By:


sogabe
(14/Mar/13 7:23 AM)




Status:


InProgress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14542) Issue ID Pattern no longer working

2013-03-07 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 commented on  JENKINS-14542


Issue ID Pattern no longer working















See JENKINS-14827; may be fixed in Jenkins trunk.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14542) Issue ID Pattern no longer working

2012-08-03 Thread s.sog...@gmail.com (JIRA)














































sogabe
 started work on  JENKINS-14542


Issue ID Pattern no longer working
















Change By:


sogabe
(30/Jul/12 5:00 AM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14542) Issue ID Pattern no longer working

2012-08-03 Thread s.sog...@gmail.com (JIRA)












































 
sogabe
 edited a comment on  JENKINS-14542


Issue ID Pattern no longer working
















It seems that JSONlib library has a bug. I'll patch to it.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14542) Issue ID Pattern no longer working

2012-07-23 Thread jimnz...@gmail.com (JIRA)














































James Bushell
 created  JENKINS-14542


Issue ID Pattern no longer working















Issue Type:


Bug



Affects Versions:


current



Assignee:


sogabe



Components:


mantis



Created:


24/Jul/12 4:35 AM



Description:


Our commit messages starts with 12345 . and I used to use Issue id pattern %ID%, however this is no longer working.

Reading through hudson.plugins.mantis.MantisProjectProperty.java, method createRegexp(..) should generate the regular _expression_ (?=[)(\d+)(?=]) which will happily find the regex, so doesn't look like its a problem there. 

What appears to be occuring is that the Issue ID pattern is being saved with quotes around it eg "%ID%", because if I commit svn messages with quotes around the square brackets it all works, and looking in the job xml it is saving the field as pattern%ID%/pattern


I can get around the problem by using a Regexp pattern of [(\d+)] and leave the Issue id pattern blank, but it would be ideal if this could be fixed




Project:


Jenkins



Priority:


Minor



Reporter:


James Bushell

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira