Problem is I have 3 projects wih 3 different emails used to open tickets:
email notification sender is email@example.com
when ticket is created or any noification happens we recieve email from jira-admin for the opened tickets so how to reply to tickets ? the To field will be firstname.lastname@example.org
This is a requirment please help. is there any work arround or certian setup I need to considser?
Is your question about the from address you receive emails? That is a parameter which is configure in each of your project (project admin page) called "Mail Configuration: Mail notifications from this project will come from 'email@example.com' (Edit mail configuration) "
Albeit, not an answer to what you originally asked.
Also, bear in mind the scenario where you set up two separate outgoing email addresses:
Now, you set up 3 email handlers, so that
You will get
What you might not expect:
The documentation is at http://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email
It does state how the create/comment handler works - it will find the issue key in the email subject and use that to decide to comment instead of create, irrespective of the mail accounts used.
Im deploying JIRA as an enterprise or wide deployment scale, we have multi departmets then multi projects.
Default notification will come with the name of jira-admin as smtp. I'm I wrong please correct me if this is not proper thinking, if there is a special setup Im not understanding
we simply cannot put one of the emails(A,or B or C) in the From address in SMTP mail setup. this works if we have one project only. correct me if I'm wrong.
Is this has something to do with overriding it in the notificaion scheme on the project level, so JIRA knows to which project and to use which email when sending the noification first time?
Mr. Nic, Check my last comment, I have nothing to do with the handler or the SMTP and all my settings was ok The problem was best idenifying my question. and i don't know why you are sill angry when replying, I'm expecing the best answers, you can check the right answer above.
I am sorry, as I seemed angry, I didn't mean too. It's just that your question was answered in the documentation, and you didn't seem to be reading it or my responses at all. I was not able to grasp your follow-up questions, as they didn't seem to be related to what I'd said, or the documentation.
The answer you've accepted as correct was not mentioned in the original question at all, and was not very clear in your responses either. I applaud Renjith for untangling it (or reading your mind) so well!
I've commented on that to warn you of a possibly unexpected behaviour though, as it's caught a few people out. I think it's correct behaviour, but it might seem a little odd when you're testing.
No problem, but at least Renjith answer solved our issue in the customization. remaining things we will handle it, well every thing might be in documentation, but it seems you think I'm not reading. I do beleive my question is clear enoghh and I was asking about things else might affect or solve my case in my previous comments. Mr.Renjith is not reading my mind.
Your yes/no question has a clear answer of "No". The documentation makes no reference to notification schemes, so I don't know why you've even asked about them - you appear to be jumping around grasping at straws instead of reading and then explaining clearly what parts you don't understand.
The answer to your original question is covered in the documentation and answered in my original answer - the bit in bold.
My best guess is that you are not grasping the fact that there's no way Jira can guess what project you might want to create an issue in from a block of potentially random text, and hence the handlers have to have a "project" parameter to know where to create new issues. As it says in the documentation. If you want to create issues in separate projects, you need separate mail boxes, or to install an advanced handler (my standard trick here is the JEMH, which covers all sorts of advanced clever email tricks superbly)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs