Hello, We would like to know if we can configure more than one email channels for one service desk project.
This is because we would like to create three channels to attend issues in the same project.
You are only allowed to have a single email address (Channel) associated with a each service desk. You can however have use email aliases to point to the service desk email allowing you to have multiple email addresses.
For example you might have a service desk configured to use firstname.lastname@example.org and then point two aliases email@example.com and firstname.lastname@example.org to email@example.com. This is what we do and is the only work around at this time.
When the email requests come in via the alias, the alias is attached as a request participant. We then use automation rules to apply a component placing it in the proper queue. All emails go out through the same address but when the user responds the JIRA email handler is able to match them into the proper service desk.
Currently, I got realized that the only email that goes out is the main email.
Now I have another issue, I have set the alias and made the automation rules, the first day was OK, but now I see, that each time someone opens a case through the alias email, in the ticket there is no one on request participant, so it affect to the automation rule. is it any configuration do I have to check?
I talked to the person who made the alias and he told me the set is ok.
Then I made some tests and I have realized that everything is right if I create the ticket from my agent email (that email is registered as an agent administrator in ServiceDesk), the alias is put automatically as a request participant.
On the other hand, if I create a ticket through another email (my personal email in Hotmail for instance), the ticket is created but the alias is not added as a request participant.
Do you think it could be affected by a default rule on ServiceDesk?
In the administration portion of the Service Desk please navigate to customer permissions and let me know what "Who can customers share requests with?" is set to. I think that is the issue. It needs to be Any Customer..... or Any Customer or Organization....
We are just testing Jira and one important point is, that we have diffrent eMail-adresses (more than 10!) that need to be in defined queues.
Know I read this discussion and I will test it. But I can't find, where I must set the queue in the automation rules. Can you show me a example?
We setup out aliases so that they come in with the regular email address and are added to the issue as a request participant. We then use an automation that triggers on create. When a request participant of the specific email alias is found we then either apply a request type or on service desks with lots of email addresses we use components and update the issue to have the proper component. Our queues are written to filter on component so the issues go to the correct queue.
With cloud you can actually have two emails. Atlassian provides one firstname.lastname@example.org and you can define one of your own, e.g. email@example.com. While I have not done so you should be able to assign each email to a different request type.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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