I've read this https://confluence.atlassian.com/jirakb/how-to-create-issues-in-multiple-projects-using-one-mail-server-in-jira-core-779160675.html but I don't understand it.
My company has a mail server in gmail (all company emails are @company.com).
In Method 1, what gmail is it referring to in step 2? Do I need to create a new account in the server for each project?
In Method 2, it says to configure filter and labels, but in which account? I don't understand where I need to configure these.
Hey Federico,
Welcome to the Community - I'd like to understand a little more about what you want to do here so I can help you! Can you tell us more about your use case?
So the configuration would depend on what you need - do you want everything to come through a single email address or are you going to use different email addresses for each project?
In addition, if you wanted to use a single email address - how would you tell which emails go to which projects? Would this be based on sender, email subject etc?
Cheers,
Keri
Hi, thanks for your response. I'll try to be more clear:
I want to be able to create issues in my Jira Software projects by sending an email to some address. The link I put on the question mentions two ways. I don't quite follow the instructions mentioned and I have some more doubts:
1. Do I need to create one email account for each project? (asking for both methods)
2. In method 2, the documentations says that labels and filters should be created. Where does this need to be configured? In which account? (is it one account per project or just one account?)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm still not sure what you need for your company, if you want to answer my questions then the information I can give you will be more specific for your needs. I'd also recommend reading this instead: Creating Issues and Comments from Email
To answer your questions specifically:
I believe this KB article may be over complicating what you actually want to do, but without the extra information about your use case, it's difficult to give a recommendation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.