[#JRA-6310] Send notification / comment to specific user

JIRA

Send notification / comment to specific user

Created: 31/Mar/05 10:02 AM Updated: 01/May/08 08:02 AM

Component/s:

Email integration

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

JRA-5813 Email issue to external person

Reference

This issue relates to:

JRA-11699 Comments Visibility - Possibility to specify a user instead of a group

JRA-5959 E-mail this issue operation

Participants:	Brian Nguyen, Neal Applebaum, Randy Chitwood, Shirley Keddy and Trevor Freeman
Since last comment:	12 weeks ago
Labels:

Description

« Hide

In a previous issue management application we had a piece of functionality that we miss in Jira. Namely, the ability to send an issue notification email to one or more users.

For example, if I want to get input on an issue from someone other than the reporter or assignee I have to either send them an email to them and reference the Jira issue, put the person on as a watcher, or assign the issue to the person.

What would be preferrable would be the ability to send an inquiry / comment to a specific user such that the assignee does not change and that person does not now have to remove themselve from a watch.

Another motivation for this functionality is the use case where an assignee needs input from multiple other users. Currently in our organization, people tend to use assignment as a way of getting input to an issue.

The problem with this approach is that it turns what could be a parallel process in to a serial process. For example, if I need to get input from three people and use assignment as the way of getting their input in to the issue the input requires assigning the issue 6 times along with the latency for each step.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Brian Nguyen - 04/Apr/05 12:49 AM

Do you mean that you would like the user to have the ability to send notification emails to arbitrary users?

[ Permlink | « Hide ]

Randy Chitwood - 04/Apr/05 07:26 AM

Yes. A use case is I want to get input into requirements for an issue and perhaps some UI work needs to be completed. Instead of assigning first to one person and then the other. I keep the issue but send a comment to a specific user other than the assignee or the reporter, much like you just asked me this question. This keeps the thread in the issue but does not take the assignment around the horn.

A work around would be to make those persons watchers but that is klugie since I only want their participation for a one shot input. Adding watchers would also be a multi-step process which is undesirable.

Maybe one implementation approach would be to use the Viewable By approach you have here in the comment section and instead have a Copy To: multi-select drop down that contains the user list.

[ Permlink | « Hide ]

Neal Applebaum - 04/Apr/05 07:30 AM

See also JRA-5959

[ Permlink | « Hide ]

Randy Chitwood - 04/Apr/05 07:42 AM

Two similar issues

[ Permlink | « Hide ]

Neal Applebaum - 04/Apr/05 07:49 AM

For me, I don't necessarily want to have to make a comment or perform ANY operation on an issue to instigate an e-mail. I just want to advise a user or group about an issue's existence. As a best of both worlds, I suppose, the Email this issue option could launch a form which allowed a user(s)/group picker and a comment box, so the comment would be part of the email, but not the issue. For example, I may want to advise a manager that an issue is behind schedule, but I don't want that email or the comment recorded within JIRA.

[ Permlink | « Hide ]

Randy Chitwood - 04/Apr/05 08:17 AM

I see your point.

I would be happy with either approach; just as long as you can send
email on an issue. On balance, I would prefer to see the thread in the
Jira issue but I know there are people on both sides of that.

Thanks,
Randy

----~~Original Message~~----
From: Neal Applebaum (JIRA) jira@atlassian.com
Sent: Monday, April 04, 2005 8:51 AM
To: Randy Chitwood
Subject: [JIRA] Commented: (JRA-6310) Send notification / comment to
specific user

[
http://jira.atlassian.com/browse/JRA-6310?page=comments#action_33815 ]

Neal Applebaum commented on JRA-6310:
-------------------------------------

For me, I don't necessarily want to have to make a comment or perform
ANY operation on an issue to instigate an e-mail. I just want to advise
a user or group about an issue's existence. As a best of both worlds, I
suppose, the Email this issue option could launch a form which allowed a
user(s)/group picker and a comment box, so the comment would be part of
the email, but not the issue. For example, I may want to advise a
manager that an issue is behind schedule, but I don't want that email or
the comment recorded within JIRA.

functionality that we miss in Jira. Namely, the ability to send an issue
notification email to one or more users.
than the reporter or assignee I have to either send them an email to
them and reference the Jira issue, put the person on as a watcher, or
assign the issue to the person.
comment to a specific user such that the assignee does not change and
that person does not now have to remove themselve from a watch.
assignee needs input from multiple other users. Currently in our
organization, people tend to use assignment as a way of getting input to
an issue.
parallel process in to a serial process. For example, if I need to get
input from three people and use assignment as the way of getting their
input in to the issue the input requires assigning the issue 6 times
along with the latency for each step.

–
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.atlassian.com/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

****************************************************************************************
BENEFITFOCUS.COM CONFIDENTIALITY NOTICE: This electronic message is intended only for the individual or entity to which it is addressed and may contain information that is confidential and protected by law. Unauthorized review, use, disclosure, or dissemination of this communication or its contents in any way is prohibited and may be unlawful. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please notify the original sender immediately by e-mail or telephone, return the original message to the original sender or to bfpostmaster@benefitfocus.com, and destroy all copies or derivations of the original message. Thank you. (BFeComNote Rev. 07/29/2003)
***************************************************************************************

[ Show » ]

Randy Chitwood - 04/Apr/05 08:17 AM I see your point. I would be happy with either approach; just as long as you can send email on an issue. On balance, I would prefer to see the thread in the Jira issue but I know there are people on both sides of that. Thanks, Randy ----~~Original Message~~---- From: Neal Applebaum (JIRA) jira@atlassian.com Sent: Monday, April 04, 2005 8:51 AM To: Randy Chitwood Subject: [JIRA] Commented: (JRA-6310) Send notification / comment to specific user [ http://jira.atlassian.com/browse/JRA-6310?page=comments#action_33815 ] Neal Applebaum commented on JRA-6310: ------------------------------------- For me, I don't necessarily want to have to make a comment or perform ANY operation on an issue to instigate an e-mail. I just want to advise a user or group about an issue's existence. As a best of both worlds, I suppose, the Email this issue option could launch a form which allowed a user(s)/group picker and a comment box, so the comment would be part of the email, but not the issue. For example, I may want to advise a manager that an issue is behind schedule, but I don't want that email or the comment recorded within JIRA. functionality that we miss in Jira. Namely, the ability to send an issue notification email to one or more users. than the reporter or assignee I have to either send them an email to them and reference the Jira issue, put the person on as a watcher, or assign the issue to the person. comment to a specific user such that the assignee does not change and that person does not now have to remove themselve from a watch. assignee needs input from multiple other users. Currently in our organization, people tend to use assignment as a way of getting input to an issue. parallel process in to a serial process. For example, if I need to get input from three people and use assignment as the way of getting their input in to the issue the input requires assigning the issue 6 times along with the latency for each step. – This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.atlassian.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira **************************************************************************************** BENEFITFOCUS.COM CONFIDENTIALITY NOTICE: This electronic message is intended only for the individual or entity to which it is addressed and may contain information that is confidential and protected by law. Unauthorized review, use, disclosure, or dissemination of this communication or its contents in any way is prohibited and may be unlawful. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please notify the original sender immediately by e-mail or telephone, return the original message to the original sender or to bfpostmaster@benefitfocus.com, and destroy all copies or derivations of the original message. Thank you. (BFeComNote Rev. 07/29/2003) ***************************************************************************************

[ Permlink | « Hide ]

Brian Nguyen - 05/Apr/05 02:54 AM

Thank you for clarify this for us and watch this issue for further updates.

[ Permlink | « Hide ]

Trevor Freeman - 24/May/05 08:48 PM

If someone has been notified about an issue it would be nice to keep the history of it (since you won't have the sent e-mail history in your e-mail client since you sent the e-mail through Jira). If not in the main comment thread then perhaps in the change history tab or a new tab just for notifications.

[ Permlink | « Hide ]

Shirley Keddy - 01/May/08 08:02 AM

I agree with Trevor that a history of an email being sent to a user is needed within the JIRA issue.

I agree with Neal's idea of launching "a form which allowed a user(s)/group picker and a comment box, so the comment would be part of the email" however in my role as a Support person, I have found it necessary to know all the follow-up correspondence that has been sent out regarding particular issues. So I would advocate for that information being stored along with the issue.