I have this behaviour how can I workarround this,
I have project A with key A
I have project B with key B
Users of project A forward a copy of thier ticket in thier project to project B having project A key in the subject the email will not create ticket in project B.
Can we write a script or listiner to replace any exsising project Key from the subject of email and foce the email to go to the intended recipient project ??
All the built-in handlers work on the same simple rule - if there's an existing issue key in the subject, then the email is a comment on that issue. If it can't find an existing key, it will create a new issue in the handler's defined project.
Your only option is to find or write a new handler for your email, because you need totally different rules (When I say "find", I'm actually hinting that you might want to look at the JEMH, although I don't know if it can do this)
I think you might have a logical problem though - if an email from a project A user arrives with an issue key in the subject, then how do you know whether it's a comment for that issue or a new issue for B?
If reciepient email in project B is defined for that project in subject (looking at project Key in subject) match then its a comment, if no match then it will be a new issue to be created in the reciepient email project, simply as that!
Please I have the source code , if we can re-code the class , where is that class?
That rule does not work. You'll match all incoming email to "new issue". In the cases where it contains a project key in the subject, then what does it comment on? You need to include the *full* issue key to get a comment. In other words, pretty much what the default email handlers do, although you probably want to remove the bit that matches other projects.
I can not give you the source code, it's private. If you have a commercial license for Jira, you can download it from your my.atlassian account.
However, whether you have the code or not, start at: https://developer.atlassian.com/display/JIRADEV/Adding+your+own+email+handling+classes
There should be a workarround for such case, keeping inmind that the subject contains full issue number and project key like ( A-1125 ), what is not logical is its looking at the subject and does not look at the To field as well. This way it will not open a new ticket in project B while the recipeint is B project.
Please our managers says why its not opening tickets in the requersted project B while the subject contains (FW: blabla A-1125)
Today we're off to Canary Wharf for our next event at Moody's Investors Service, so I hope you can all make it. Please RSVP here if you can: https://aug.atlassian.com/events/deta...
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