History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-2167
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Vincent van Wichen
Votes: 53
Watchers: 27
Operations

If you were logged in you would be able to see more operations.
JIRA

CC email address list in issues (notify arbitrary emails)

Created: 13/Aug/03 04:11 AM   Updated: 28/Feb/08 10:08 PM
Component/s: Email integration
Affects Version/s: 2.3 Enterprise
Fix Version/s: None

Time Tracking:
Not Specified

Environment: n/a
Issue Links:
Blocker
 
Duplicate
 
Part
 
Reference

Participants: Bernard Durfee, David Josephs, Gunnar Wagenknecht, Jeff Turner [Atlassian], john burgos, Kevin James, Michael Corn, Nick Menere [Atlassian], sven niemetz and Vincent van Wichen
Since last comment: 38 weeks, 2 days ago
Support reference count: 10
Labels:


 Description  « Hide
Entries for a CC list in a issue. So that CC-ed persons get status updates. I know it is simulair to watches, however you cannot put another on a watchlist.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] - 26/Jan/04 05:38 PM
Rachael,

Would a 'Cc' field meet this need? The specified comment would then be mailed to the Cc'ed person as well as reporter/watches.


Vincent van Wichen - 18/Jun/04 03:18 AM
Is it normal that issue are open so long?
Please live up to your own slogan.

Jeff Turner [Atlassian] - 27/Sep/04 12:26 AM
Although with 3.0 it is possible to edit the watchers list, the need for notifying arbitrary email addresses still exists. We should extract the code that lists the potential recipients of a notification (reporter, assignee, single user, email etc) and reuse that list here.

Jeff Turner [Atlassian] - 19/Oct/04 10:38 PM
A note: the Cc field should be editable on the 'create issue' page, and the creation notification Cc'ed to the recipient.

sven niemetz - 01/Dec/04 11:50 AM
this is a feature that was very much sought after when I created our in-house tracker.

Our implementation is that anyone with bug-change rights can add any email to be CC:'d either on major events (open,close) or all events (comments, etc)

Users get informed that they were added (and by whom), and are free to take themselves off.


Kevin James - 15/Dec/04 11:26 AM
We have a slightly different take on the CC feature. Watchers work great if you or the Watchers you add to the issue need to be notified for various changes to an issues or kept up to date as the issue progresses through the system.

What we need, in addition to this, is the ability CC a few relevant users on a particular Update or Create. This feature wouldn't add them to the Watchers list, but just notify them of a particular once.


Bernard Durfee - 22/Jun/05 01:54 PM
This seems rather easy to implement, if I had the time.

1) Add a simple string field to issues, which will hold a comma seperated list of email addresses.
2) Create an issue listener that sends an email to the addresses in the list when the issue is updated.


john burgos - 10/Oct/05 11:55 AM
I need to add a different type of watcher. In custom fields, I have a text field that is passing in an email address. I need to add this email address to my notification scheme. Currently, you can only add dropdown custom fields to notification schemes but not text fields.

I think this is similar to what Bernard Durfee requested. Hopefully this can be released in an upcoming version.


Nick Menere [Atlassian] - 10/Oct/05 07:19 PM
In 3.4,
There is a multi-user custom field.
This way you can add a a list of users to an issue.

For example, you can add a custom field called "CC".
You can then add this field to the notifications, so that all people in the list are notified on issue events.

Though, notifiactions are not sent out to users if they do not have the security/permissions to see that issue. This is the main issue with adding email addresses to notifications (as opposed to emails). As the email address is not a user, it does not have any permissions and will not see an issue if it has permission restrictions.

One thing we are hoping to get in for 3.4 is to also add a permission/security type for the user custom fields, so that any user specified on in the custom field can be granted permission to see the issue. This should satidfy most use cases.

Cheers,
Nick


Michael Corn - 02/Nov/05 08:16 PM
Agreed with all the other comments - and glad to see this being fixed in 3.4. However it's important to ensure that the other item listed at the end of Nick's comment is addressed. That of allowing an authorized user to list an email address for notification that doesn't map to an individual account. Almost all of our issues in JIRA are submitted by individuals that work for a unit - however the issue really needs to be tracked by a group of his or her co-workers. With >500 users I don't really want to create accounts for all their individual distribution lists.

David Josephs - 17/Jan/06 01:50 PM
It would be nice if there was a specific event that I could wrap a notification around. In the course of investigating a bug, I want to be able to "ping" the CC list at any time. So, in my workflow, I could add a "Ping CC List" transition that:
  • Poped up a custom screen that allowed me to edit my CC list.
  • Fired a "Do Notifications" event
  • Returned to the calling state in my workflow.

Nick Menere [Atlassian] - 17/Jan/06 06:03 PM
David,

You could fire a Generic Event. This would trigger a notification. On your transition screen you can place your CC field (there will also be a comment field in which you place your email message).

Isn't this what you are after?

On a side note, we are looking revamping our Events mechanism in the very near future.

Cheers,
Nick


Gunnar Wagenknecht - 21/Aug/07 06:08 AM
Any updates on this one?

It should be also possible to make "private" comments which do not send mail notifications to the CC list.