|
We will try to look at this for 3.2.2. Thanks for the patch.
Moving to 3.3, as changes like this should not occur on a bug-fix branch.
Thanks a ton chris, cool stuff here. I have added this to 3.3 with a few modifications.
Thanks, Dylan I see where this has been added in the docs - but I can't find any info on how to use it. No matter how I create a custom field, JIRA never displays the custom fields in the user custom field value picker in version 3.3 (enterprise). I'm sure I'm doing something simple wrong. Any pointers?
thanks Ah - I see - it only works if the custom field type is user picker. However, while all of our users will have accounts, they'd often like to have a group email address notified in addition to or in place of themselves. So I'd like to be able to have them enter an email address in the CC field and have that get notified. Any thoughts on how to make that happen?
thanks Hi Michael,
There is a "Single E-mail Address" notification type in JIRA. Please see: If your issues are not viewable by non logged in users, you can always create a dummy user with the e-mail adress of the 'group'. At the moment there is no CC field functionality in JIRA. Please vote for: Currently the only option is to customise JIRA to do this, by writing a new Notification Type. Also, JIRA sends notifications only to users that have pemission to see the issue. I guess if you need true cc functionality, this behaviour would have to be changed. Thanks, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Resolved
Major
Allow cCustom user field as notification target
Title: Allow custom user field as notification target
Description:
It would be nice if a user custom field could be used as the target for notification messages.
I've attached a zip file containing the required changes to the codebase to allow this to occour, the root of the modifications are the 3.2 enterprise codebase. The zip file contains all the modified and added files, including:
src/etc/notifications/notification-event-types.xml
src/webapp/secure/admin/views/notifications/addnotification.jsp
src/java/com/atlassian/jira/notification/type/UserCFValue.java
src/java/com/atlassian/jira/notification/NotificationType.java
src/java/com/atlassian/jira/notification/type/AbstractNotificationType.java
src/webapp/secure/admin/views/notifications/editnotifications.jsp
The first three files are the notif type itself, and the other three are modified to allow the notif type's parameter to be formatted by the notif type itself in the admin menus, so that the field name appears as it's name rather than it's field ID.
Line 44 of UserCFValue is the only thing I'm unsure about, is this the best way to decide if a custom field is actualy configured for the issue?