“Assign to me” Jetpack
Just recently, my colleague oremj published a bookmarklet making “assign this bug to me” a one-click operation in bugzilla.
Obviously, bookmarklets are fun and games, but Jetpacks are even more awesome, so I went ahead and wrote one that adds an “assign to me” button next to the assignee field:
You can find and install the jetpack through my jetpacks page on github.
Can you make an “Assign to wenzel” button? Thx!
Oh, you’d love that.
How can you be so hacky? If you’re going to spend more than 1 second in solving this issue, what’s stopping you about fixing bugzilla itself? Perl is not that hard.
For starters, the fact that I think something needs to be addressed does not mean the bugzilla devs agree. Much like with every Firefox add-on, not everything has to be part of the core app code. If people like my jetpack, it might become it at one time, but we don’t know.
Also, the little code it uses wasn’t exactly “hacky” or hard to write.
Hi,
I’ve been using this Jetpack for some time now, and it’s great!
I encounter a bug occasionally though which I can’t figure out. Sometimes I make an unrelated change to a bug and commit my change, and I suddenly find out that the bug has been assigned to me, and I have to undo that manually.
I’ve looked at the code and I can’t see anything wrong with it at a glance. I’m on trunk, which unfortunately means that about:jetpack is broken and I can’t change anything in the jetpack to try to debug this. Have you seen this problem before? Do you have an idea what might be causing it?
Thanks!
Hey, Ehsan! I am glad the Jetpack is useful for you! This is the first time I’ve heard about this particular bug, but I am experiencing another problem on occasion where *two* buttons show up. There seem to be some events getting fired that shouldn’t. In your case, maybe the click event is triggered on the button for some reason?
I just filed a bug on it, but if you have any more information about how to reproduce it, that’d be very much appreciated!
Oh, I just found out how to reproduce the “two buttons” problem and came here to comment that saw your reply!
Open a bug, make sure the first button shows up, and then go to the keyword field and type something so that the iframe autocomplete box shows up, now the second button is added.
I think this is because pageMods are loaded on each iframe load, see https://bugzilla.mozilla.org/show_bug.cgi?id=535001. In the meantime, I guess you can fix things by switching to jetpack.tabs.onReady.
Ehsan
Thanks, Ehsan! I fixed it by avoiding adding a second button if one exists already! You can update the jetpack now!
Ah, I wish about:jetpack worked on trunk…
I guess I’ll have to wait for Jetpack to update it behind the scenes on its own…