|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Keith Brophy - 02/Feb/05 05:59 PM
Again - another good idea that we should investigate introducing to JIRA.
I guess I should add that you may want to have what attachments would be emailed out as the developer(s) may not want all/any sent everytime.
where is this feature at on the priority list? sure would be a good thing to have in v3.1.x
Kevin,
This will not be implemented in JIRA 3.1 or 3.2, as almost all the features have been finalised for those versions. At this stage I can't promise anything. We have not had any planning meetings regarding 3.3.
An additional piece of functionality which would be VERY nice is if you had the option to convert the whole issue to a 'pdf' that would be sent as an email attachment.
Speaking of attachments, it should be optional whether you include them in the email or not. The PDF conversion and mail feature would be very nice to have. Is this feature request on the "radar" for 3.3.1?
Kevin,
JIRA 3.3.1 is a bug fix release, and does not contain any new features. JIRA 3.4 has been fully specified, but JIRA 3.5 has not yet been set. Please note that some shops may not want attachments being automatically sent with the notification email. I would think that stating an attachment was made along with its name in the notification and directing the customer to go to the website to download it would be enough.
Allowing the developer to email a issue to a customer with the option of including the attachment(s) is desirable for closed shops such as ours that do not allow customers to enter/view jira issues. I support this issue as well. We have many clients that we would like to email issues to but not want to get them access to Jira.
Kevin,
Unfortunately 3.6 is quite full at the moment so I cannot promise to include it in 3.6. Anton The e-mail can be used as an invite for the person to become a watcher of the issue.
That will not work since you must be a valid jira user to be a watcher. Our jira instance is a private installation and there is no way customers will be given logins. Kevin,
Good point. JRA-5959 is better suited for the 'invite' feature. Thanks, We have recently expanded our use of Jira to our helpdesk, replacing a faster system that is made for helpdesk tickets (OTRS). While Jira offers many improvements, having an "Email Issue" or "Invite" feature, would make a big difference and is one of the key things missing for us. We use watchers liberally for internal users, but we have a lot of external users who have legitimate helpdesk needs. If they email issues in they get automagically entered into jira, but that doesn't cover all use cases. We desperately need the ability to whip out a quick email to someone and be able to capture their response.
Here at Linden Lab, our User Experience Designer, Ben Glenn, brought up that this would be a good idea. I agree, and it seems like such a basic feature that's common on many webpages to "share this with a friend".
Especially now that we've opened up JIRA to Second Life's Residents @ http://jira.secondlife.com votes and watches It should be also possible to hide "private" (internal) comments from the notification. However, we also do need this feature.
Matt and Gunnar's requests/suggestions cover our needs, too. Our move to JIRA was driven development and QA groups, but our help desk must be integrated into the issue management process. Many issues (data requests, bug reports, feature requests) come in from site users via email. When issues have been resolved, we must to respond to the originator. The simplest solution we can think of is to generate an email containing the contents of a comment/text field. The email address can be entered manually or, alternately, we've considered the used of a custom field. Obviously, we need to record the mail in the issue history. In most cases, we would not need (or want) to send the entire history.
I think it's an important feature. Consider the following scenario.
You have a setup which is mostly in-house. However once in a while you want to let people track a single specific issue. However you don't want to add them because most of the information is irrelevant to them. This functionality could make the gap between jira and other customer support systems smaller. Hi,
I am developing a plugin to address this feature request. Check out and keep an eye on the plugin home page Cheers, Hi,
I have uploaded the 1.0 version of the plugin to http://confluence.atlassian.com/display/JIRAEXT/Email+This+Issue Please add your questions or comments about the plugin to its homepage. Thanks, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Email issue to external person
