Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Using user's email address as the sender address

web-app

Hi, we are currently using gemini 2.x in our company. Before we update to version 3, I'd like to know if it is now possible to use the user's email address as the sender address for email notifications.

For example, if a developer updates an issue, the notification mail should be sent with his email address as the sender (instead of the static/configured sender address).

In versions 1.x/2.x I had to customize the mail plugin to achieve this (required) functionality.

Is this supported out-of-the-box in V3 (either with the mail plugin or the scheduler service)?
If not, do you see a possiblity to add such a feature in the (near) future?

Thanks a lot.

--
Martin

mbischoff
· 1
mbischoff
Replies (7)
helpful
0
not helpful

Martin,

This can be customised via the Gemini Scheduler.

Add it to the list (gemini.countersoft.com) and we will make it an option.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

I have created the issue:
http://gemini.countersoft.com/Default.aspx?p=2&i=1934

When you say: "This can be customised via the Gemini Scheduler", do you mean this is already available in the current version or that this will be available in a future version?
 
Thanks a lot.


mbischoff
· 1
mbischoff
helpful
0
not helpful

It means that you can amend the source code of the scheduler. The feature is not available yet.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Has this change request been considered for an upcoming version?
There was no activity in the issue (http://gemini.countersoft.com/issue/ViewIssue.aspx?id=1934&PROJID=2).

This seems to be a very small change, but I think some people might find it quite useful.

In the past I was able to change the mail plugin accordingly, but I don't like to do this for every new version of gemini. It would be great if this option could be added to gemini.



mbischoff
· 1
mbischoff
helpful
0
not helpful

Agreed, it is a small change, but here is a potential issue we need to think about.

The Gemini Scheduler will batch up email alerts and send one per issue.  Let's assume that 2 people update the same issue.  The Scheduler will send out just one issue - so who's the sender?  Person 1 or Person 2?  Both udpated the issue since the last time the Scheduler processed email alerts!

Thoughts?


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Good point! There are several possible solutions:

- send one email per user (containing only the changes made by that user)
- use the email address of the user who last modified the issue (since the last check)

I think the first solution would be the "correct" one, but is probably not that easily implemented? Also it would increase the number of emails being sent (which is not what I would want).

When implementing the second solution, maybe it would be possible to add some additional information to the email, e.g. a "Issue was modified by Person1, Person2, ..."


mbischoff
· 1
mbischoff
helpful
0
not helpful

I too am very interested in this feature.  I am currently watching this on the public Gemini instance and I've voted to get it included in version 3.5.  My company would like to use Gemini as our customer support mailbox.  Customers who have issues would send in their questions or problems and issues would automatically get created. 

This process currently works except for the feedback mechanism - how do I know who to get back to once the issue has been resolved?  Today in Gemini when an issue is logged, Gemini doesn't keep track of who logged it.  I'd like to see the "Reported By" field be filled with this user's email address. If the user doesn't exist in the system, one would be created.

To fully flesh out this feature, I'd like to see the user entity enhanced too.  There should be some contact information stored as part of this (address, phone number).  Finally some customer service reports would be outstanding - issues opened and closed a day, length of time issues open, number of issues closed by user.


rcoleman
· 1
rcoleman