Community
Participate
Working Groups
Bugzilla does send email notifications which could be used in theory for task synchronization retiring pulling regular queries and reducing load on servers to the necessary minimum. I heard there is an email connector to Mylyn, could it be used for this purpose?
Let's explore options for this in the next release cycle.
This would definitely be interesting.
Hmm, wasn't the idea to turn off email notifications in repository prefs to reduce email load?
I think the idea is that Bugzilla ( and other task trackers ) send email notifications which are a 'push' mechanism and _might_ be exploitable by Mylyn to get a list of changed tasks, rather than polling servers repeatedly. These emails do not necessarily have to end up in the user's inbox ( although I for one am not sure where they should end up ).
assume mail is POP(S): - mylyn should retrieve messages based on subject or sender headers - preferably also remove from POP box after retrieval to prevent normal mailbox overload (1)(2) assume mail is IMAP(S): - mylyn should retrieve messages based on subject or sender headers - preferably also remove from IMAP, mark as read or move to special folder after retrieval to prevent normal mailbox overload: (1)(2) (1) this will fail in single-user, multi-device scenario (like mine: fast desktop/30" monitor + small laptop to move around, both sharing query content) one of the queries will miss an update. (2) how to prevent the regular mail client to retrieve stuff first? Example code to retrieve mail using java is here: http://www.builderau.com.au/program/java/soa/Getting-the-mail-in-receiving-in-JavaMail/0,339024620,339228060,00.htm To configure for each repository Mylyn would at least need: user name, password, protocol, sender signature to recognize, maybe also configure last retrieved timestamp. Conclusion: even if we get it to work technically it requires too much configuration. Better solution see my comment 24 in bug 281894. repository defines it accepted retrieval policy in robots.txt like file, Mylyn will parse and behave properly out of the box in framework. All connectors follow automagic, leaving manual refresh for anxious user.
I never said that I know how this can work properly :-) Just saying that there is a way of pushing notifications from the bug tracker. While we're in fantasy land, what about XMPP? One can envision Bugzilla et al pushing bug change notifications using XMPP and Mylyn receiving those notifications and then retrieving only that changed bug(s) .
(In reply to comment #5) > > Better solution see my comment 24 in bug 281894. repository defines it accepted > retrieval policy in robots.txt like file, Mylyn will parse and behave properly > out of the box in framework. > All connectors follow automagic, leaving manual refresh for anxious user. I don't see any comments from you in that issue, are you sure you got the number right?
Oops bug 281893
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
