In the two projects I’m working on, I’ve been given the role of administrator in Atlassian JIRA, the application we use for tracking tasks and bugs. This has its pros and cons.
The reason I was given this role is that it’s required to move tasks and bugs through the workflows that our department has set up. In the past, I’ve had to pester project managers to move my items into the status where I could then resolve them to be tested. Usually, I didn’t remember to do this until I was ready to resolve the item. So the workflow wasn’t really work-flowing if you get my drift.
Now, as an administrator, I can usher my items through each step until I’ve resolved them. However, the problem with being a project administrator is that I get what I call JIRA spam. And lots of it.
Usually, when you want to see what’s going on with a JIRA item, you click a link to watch it. And then you get an email when its workflow status changes or someone adds a comment. But as an administrator, I get an email every time an item is created—doesn’t matter who creates it or to whom it’s assigned.
On the other hand, this can be a good thing. Because every team member is an administrator in JIRA for one of these projects (so they can also move items through the workflow themselves), I expect most of them have set up rules in Outlook to send the JIRA spam right on past their inboxes and into the trash or some other folder they ignore except when they empty it. But I’ve found that if I at least scan the title of the item as it sits in my inbox, I learn valuable information about changes that are proposed or planned in the project. And then I can go into JIRA and put a watch on items of interest to me.
So it’s an interesting catch. I get a lot of email out of JIRA, but it’s a way for me to keep abreast of changes. I just have to sift through the dirt to find the gold. Since the gold is there, I figure I’ll endure the dirt.
Related entries (auto-generated):
A Process for Developing Regular Release Notes
Suggestive Selling for a Tech Comm Storefront
How a Team Member Woke Me up to Snippets
Journals by Email











2 Comments to 'JIRA Notifications: A Helpful Nuisance'
June 29, 2009
You can completely customise what events generate emails and who to send them to via Notifications Schemes in the administration section.
http://www.atlassian.com/software/jira/docs/v3.13/notification_schemes.html
[Reply]
June 30, 2009
Bug tracker spam is a typical problem with many systems because of their over zealousness in default mode to keep “everyone notified”.
Some systems do provide a work-around by having to spend a lot of time configuring notifications but the control here is with the administrator and not with the individual.
A lot of this is down to design and the ethos of the system. IMHO making the notification process manual to a large extent (so people have to explicitly choose to notify others) and providing defaults that assume you want no notifications to start with until you subscribe to the ones you want.
[Reply]
Set Me Straight. Leave a Comment.