Details
-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
After discussion within the JIRA development team, we have decided not to implement this feature. The majority of use cases described are covered by JIRA Service Desk, which is a major investment by Atlassian to offer a great experience for serving customer requests, particularly the type created by emails. JIRA Service Desk offers email handlers to make this even easier.
While I understand that JIRA Service Desk is a paid product and may not be viable for all customers, realistically this issue will not become a priority for core JIRA development for the foreseeable future.
Remember that JIRA has an advanced plugin system and your license includes full access to JIRA source code, so if this is critical for you, it may be possible for you to modify your instance via other avenues.
We appreciate your understanding.
Regards,
Dave Meyer
Product Manager, JIRA Platform
When configuring an email handler, it is possible for us to specify the Default Reporter for creating issues from emails coming from an unknown sender. And at the moment, it is intended that the Default Reporter option will not be applied for emails coming from email addresses that has been registered in JIRA.
However, it will be great if the mail handler is able to check if the email sender have the permission to create issue in JIRA, if the user has already existed in JIRA database. And if the sender do not have the Create Issue permission, then create an issue from the mail and use the specified Default Reporter as the issue reporter.
Sample use case: Sometimes JIRA is integrated with LDAP, and all LDAP users will be synchronized into JIRA. However, there may be a possibility that only half of the LDAP users is granted the permission to access JIRA, and the other half are not given the access to JIRA at all. And when the other half of the LDAP users is sending an email to create an issue, the emails will be rejected since the affected users do not have the appropriate permission in JIRA.
Current workaround: Create a group in JIRA, and group the LDAP users that do not have the ability to login to JIRA, and grant the users (or the created group) the permission to Create Issue in the Permission Scheme - Does not work Post JIRA 7.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-40975 User without permission to create an issue is not able to create via mail when a default reporter is set
-
- Closed
-
-
- Closed
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest