When creating an issue via email, the sender's email address is not being added as a watcher.

[fvillalba_LL]

Self-explanatory.

This makes it impossible for whoever sent the issue to get notifications related to it, which effectively makes it impossible to either follow-up on the issue's progress nor add comments / provide additional info.

This is on v7.11.2, btw.

[Andy Nguyen]

Hey Freddy,

Some questions:

1. Upon sending email, does the sender become the reporter of the created issue?
2. Is the sender able to log in JIRA and view the issue?

This is because, reporter should receive all notifications by default, without having to be a watcher. If the sender is not a JIRA user (a default reporter is configured) and/or not able to log in and view the issue, it's expected that he/she doesn't receive notifications.

In case the sender is a JIRA user that is able to log in and view the issue, and for some reason reporter is not configured to receive notifications, you may want to check:

• Autowatch preference from the user's User Profile
• "Autowatch own issues" from Administration -> System -> Default user preferences

I hope this helps.

Best,

Andy

[fvillalba_LL]

1. No. I've created a "dummy" user called emailed-reporter as per JIRA's suggestion. The issue gets assigned to that JIRA user. The whole point is, precisely, that people that will NEVER get a JIRA account can still report issues and follow up on them.

2. No, as per the above (and JIRA docs)

"If the sender is not a JIRA user (a default reporter is configured) and/or not able to log in and view the issue, it's expected that he/she doesn't receive notifications." <-- I believe this is not true, as per JIRA's doc

[Andy Nguyen]

Hey Freddy,

Would you share the doc you referred to and highlight what you think contradicts this statement:

If the sender is not a JIRA user (a default reporter is configured) and/or not able to log in and view the issue, it's expected that he/she doesn't receive notifications.

[fvillalba_LL]

Hi Andy!

My apologies.

I reviewed my post on Monday and noticed that it was in fact not the Atlassian docs but an add-on's stating that it should be otherwise.

In other words, you were right (I haven't found anything in the Atlassian docs that state otherwise), I was wrong.

Sorry I didn't fix this any sooner, go-live week around here...

Just FYI, we have discarded using this (unexpectedly poor) feature altogether, for the time being. For our initial rollout we will rely exclusively on the UI for creating issues.

We might still use this (same) mechanism for allowing people commenting on existing issues, though... but we are not there yet.

[Andy Nguyen]

No worries Freddy,

Notifications and permissions should be aligned with each other.

I believe these docs will be useful to you:

• Creating a notification scheme
• Configuring permissions

All the best,

Andy