I have a customer where "Default Notification Scheme" is on a project, and he has relayed these observations:
1. Default Notification Scheme applied to a project
2. Mailing into the project (catching a mail) with any attachment (this can be a real attachment or just some image from the auto-signature): this triggers "Issued Updated" and NOT "Issue Commented" (expected: both triggers). The mail does appear as a comment afterwards.
3. Mailing into the project (catching a mail) without an attachment: this triggers "Issued Commented" as expected
The customer has tested with different types of attachments and tested with their one Notification scheme also - same behavior."
I would assume that on point 1 - both triggers should fire?
Well Closed. Atlassian has comfirmed that only one trigger fires; and that a picked up mail with an attachment fires "Issue Updated", and not "Issue Commented", although the mail is added as a comment.
Notice, this also affects Listners from the toolkit (Auto Transition Listener)
I hope Atlassian fixes this. Jira is chatty by nature sending emails for every little thing and depending on how the issue was updated could send multiple emails. In an effort to make Jira less chatty I made a custom scheme that only notified users when the issue was commented. Works great if all you do is add comments. If you change a field and also add comments no notification.
Come on Atlassian, help us help you, please provide better (more granular) notification controls.
I totally agree, JIRA is a great tool, but as You say "chatty by nature" ....
I for sure would like the "Issue commented" / "Issue updated" woking more correct regarding to mail - and the possibility to have a choice to send or not send email.
A "bypass" can be making 2 transitions, where one of them are restricted to group/roles and sends out no notification when updating an issue.
Ah, no, Jira only fires one event per change to an issue.
When you're attaching a file, that's an issue update. If you just make a comment, then that comes out as a comment. Generally, comments are relegated/ignored because the other activity is more important (transition, edit, resolve etc - comments can often be made during them, but are not as important as the main change, so Jira prefers the change entry)
I can see the confusion on this one, I've never noticed it myself. My usual complaint about the "several changes, one event fired" problem is when the assignee is edited in an edit screen or transition - comes out as an "update"/"transtition X", when it's pretty clear that we need both that and "assigned"
This is actually getting a bit more interesting as Atlassian has confirmed, that catching a mail with an attachment fires "Issue Updated", but not "Issue Commented" - although a comment is created.
As my customer points out, what is the effect on the AutoTransition Listner from the Toolkit...
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs