[JIRA] (JENKINS-15257) delay before joining channel no longer working

2012-10-31 Thread ku...@gmx.de (JIRA)















































kutzi
 resolved  JENKINS-15257 as Incomplete


delay before joining channel no longer working
















Closing because of missing feedback from reporter. 





Change By:


kutzi
(31/Oct/12 1:18 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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-15257) delay before joining channel no longer working

2012-10-13 Thread ku...@gmx.de (JIRA)














































kutzi
 updated  JENKINS-15257


delay before joining channel no longer working
















Change By:


kutzi
(13/Oct/12 1:31 PM)




Due Date:


31/Oct/12



























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-15257) delay before joining channel no longer working

2012-09-30 Thread ku...@gmx.de (JIRA)












































  
kutzi
 edited a comment on  JENKINS-15257


delay before joining channel no longer working
















I'm not quite sure that I understand what the issue at hand is:
you say that the delay is not working anymore - how does this manifest? And what do you exactly mean with your last sentence:
"I'd love to see a way to delay executing joins after auth or similar, such as its possible to have the proper auth before joining resolving issues surrounding the lack of other "perform" or configurables in the bot in general."
?



























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-15257) delay before joining channel no longer working

2012-09-30 Thread ku...@gmx.de (JIRA)














































kutzi
 commented on  JENKINS-15257


delay before joining channel no longer working















I'm not quite sure that I understand what the issue at hand is:
you say that the delay is not working anymore - how does this manifest? And what do you exactly mean with your last sentence 'I'd love to see a way to delay executing joins after auth or similar, such as its possible to have the proper auth before joining resolving issues surrounding the lack of other "perform" or configurables in the bot in general.'?



























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-15257) delay before joining channel no longer working

2012-09-20 Thread theflyingcor...@gmail.com (JIRA)














































Rune Darrud
 created  JENKINS-15257


delay before joining channel no longer working















Issue Type:


Bug



Affects Versions:


current



Assignee:


kutzi



Components:


ircbot



Created:


20/Sep/12 4:12 PM



Description:


There are older tickets regarding issues around ircbot and the issue that it authenticates "too late" with NickServ for the cloak to be added upon joining select channels. This is an issue when there's need for cloak or authorization to enter channels, such as on Freenode.

I'd love to see a way to delay executing joins after auth or similar, such as its possible to have the proper auth before joining resolving issues surrounding the lack of other "perform" or configurables in the bot in general.




Project:


Jenkins



Labels:


jenkins
irc
plugn




Priority:


Major



Reporter:


Rune Darrud

























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