|
|
|
Is it normal that issue are open so long?
Please live up to your own slogan. 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.
A note: the Cc field should be editable on the 'create issue' page, and the creation notification Cc'ed to the recipient.
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. 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. 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. 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. 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". 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, 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.
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:
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, Any updates on this one?
It should be also possible to make "private" comments which do not send mail notifications to the CC list. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Would a 'Cc' field meet this need? The specified comment would then be mailed to the Cc'ed person as well as reporter/watches.