Mylyn: Indispensable
I have been using Mylyn heavily for about a year now. I hadn't realized how much it has embedded itself into my work habits. It was just how I did my job and I never paid attention to how much I was using it. Then my laptop crapped out. The machine was fine but the screen was dead and so it had to go to the repair shop. That turned into a month long ordeal. The catch was that it was supposed to take about a week so I didn't bother to set Mylyn back up on the interim machine, thinking it would just take too long to rebuild all of my queries (I have a lot because I work on so many internal and external projects). After the saga of laptop repair (non-repair really) had passed its second week I started to really feel the pain of Mylyn withdrawal. I was jonesing. What was going on with all those open bugs?! I was reduced to reading emails to see what had been updated, I couldn't easily follow whole threads... The horror.
My laptop is back now. I was able to catch up on all the stuff I missed. Nice little arrows and triangles showing me what had changed since I last reviewed my bugs. Notifications popping up in the lower corner of my screen when a change occurs. Ah.
The bugs interface would be great if that's all there were to the tool. But with the change sets management, file hiding, etc, I don't think I can live without it any more. It's the first thing I install on any
Thanks Mylyn team!
My laptop is back now. I was able to catch up on all the stuff I missed. Nice little arrows and triangles showing me what had changed since I last reviewed my bugs. Notifications popping up in the lower corner of my screen when a change occurs. Ah.
The bugs interface would be great if that's all there were to the tool. But with the change sets management, file hiding, etc, I don't think I can live without it any more. It's the first thing I install on any
Thanks Mylyn team!


4 Comments:
If you haven't backed up your Task List (right-click > Import and Export > Export Query...) lately, you should. Then, when you're forced to set up a new workspace, you can easily import 'em back in.
If I'm not mistaken, Mylyn also saves snapshots of your history which you can import too.
BTW, if you're Hooked On Mylyn Fonics*, you might want to try Tasktop. It's Mylyn++.
Hey, thanks for the tips Nick! I had missed that you can save off the queries. Never had the need before. I'll be doing that now. :)
I was kind of wishing that I could tell Mylyn to upload my query information to a CVS repo, or at worst as an attachment to a particular bug. Feature request?!
Anne uses TaskTop.
BTW, my previous solution, early on, before I got lazy, was to implement all the queris in BZ and save them there. Then just make the Mylyn ones a front end. But with like 10 queries it's still a pain to set them up.
Yes, storing your queries in your Bugzilla or JIRA repo makes them much more portable -- and in the case of JIRA, shareable w/ your team, too.
You could also simplify w/ a couple of big queries -- "everything I've opened" and "everything assigned to me", then use Categories and Working Sets to manage them into smaller groups. I have categories for "Work" "Watching" and "Done", and working sets that let me hide queries/tasks and associate related projects too.
(In unrelated news, today's captcha expresses exactly how many people feel about paying property taxes: "hatimpac".)
Post a Comment
<< Home