Environment: JIRA Core Server
Due to licensing, not all users will be able to have JIRA here. In efforts to allow them to get content into JIRA projects for others to work, we have set up mailboxes and mail handlers.
What we are running into is non-jira user's emails are stuck in the mailboxes while JIRA user's emails flow though fine.
Do non-JIRA users require a license even though the mail handler changes the reporter over to JIRA Admin?
Can someone confirm? Also, if so, is there a workaround I can do from my end?
Hi Jonathan, if reporter is being changed then emails should be working as expected. A workaround I can think is to use issue collectors instead of email. That might work as well
Yeah, I am using the JIRA service account as the reporter so users know stuff is coming in via email. I'll check out the issue collectors suggestion. If that doesn't work, we may be able to do some fancy mail routing from the LOTUS NOTES end.
I bold that because people can't believe we utilize it still :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let me know how it goes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Doubling down here. Issue collectors should do the trick for you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fernando Bordallo I think I need more info on the mail handler piece. If I am changing the mail handler so Reporter = JIRA Admin (nested in jira-administrators), shouldn't the emails import into the project regardless of who the "from" is in the mailbox?
In regards to the Issue Collector, I need to find out why I can't paste the code into a Confluence page. Currently am getting delimiter errors >-<
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For the mail handler, there is a restriction on who can send mails that will actually execute something. You wouldn't want ANYONE being able to create issues in your instance by default through a default mail handler.
You can see in the docs for the incoming mail that custom mail handlers can be configured with the Create Users parameter to create accounts for those users who send mails but are not recognized as Jira instance users, yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fernando Bordallo Perfect; that info confirmed our path to a work around.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.