You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are new to Jira.
We are setting things up and we trust that functional-wise it will be great.
I have 2 points that puzzle me a bit
1) From and administrative viewpoint, I find a bit weird the suggestion at :
"quote"
If you're already using SendGrid to send emails from your domain for another service, you will not be able to add that domain a second time. In this case, it is recommended that you use a subdomain for your 'Project Email Address' setting. For example, use Jira@notifications.company.com
instead of Jira@company.com
.
"unquote"
We are paying both Jira and SendGrid.
Jira obliges me to review my domains setup.
Jira should settle this with SendGrid.
I find it shameful to ask customers to arrange this at their expenses.
2) Jira mail router can only be configured with POP/IMAP, which means that if you are suing a cloud service you need a licensed user to send email, and on that user you have to arrange some more controls, if you wat to ensure that that account is not abused (at the end it is just a username/password).
Why not enabling some API key, with SendGrid for example.
Am I the only one worried with those concerns?
Nicola