Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Create Issue from E-mail

Dominik Suszter January 4, 2025

Hello,

I have a problem with creating issues from emails. I'm using the Email This Issue plugin, and if the Request Type field is not filled in (not used), the issue is created successfully.

However, if I want to use the Request Type field, the issue is not created.

Névtelen.png


The error message:

INFO: Found user for xyz, executing as Xyz (JIRAUSER10101)

INFO: #1734186720102 Creating issue in (KT) xyz with type Request

ERROR: com.atlassian.servicedesk.api.ForbiddenException: You don't have permission to access this service project. ERROR: Exception occurred while processing mail handler:

ERROR: com.metainf.jira.plugin.emailissue.handler.ExecutionFailedException: com.metainf.jira.plugin.emailissue.desk.api.ServiceDeskAPIException: com.atlassian.servicedesk.api.ForbiddenException: You don't have permission to access this service project.

 


 

I granted administrative permissions to the user for the project, but this didn’t help either. The permission scheme is as follows:

Névtelen.png

 

 

Thank you in advance for your response!

3 answers

1 accepted

1 vote
Answer accepted
Dominik Suszter February 12, 2025

The solution:

 

The issue was caused by setting the default reporter in the mail handlers to the sender's (reporter) account instead of a user with the Service Management role. As a result, the issue could not be created with the request type since the submitter didn't have a proper license (not servicedesk portal license).

To simplify, I set the System Administrator as the default reporter, ensuring no role-related issues occur during creation. The system then updates the reporter afterward.

 

Here are some screenshots of the implementation:

 

IMG_8535.jpegIMG_8534.jpeg

 

6 votes
Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 4, 2025

Hi @Dominik Suszter ,

Welcome to the Community!

While I haven't used this plugin, what I can make out from it's error logs is the lack of permissions of the user trying to perform the action.

Since you've already updated the permissions scheme, have you tried using the "Permissions Helper" to check if the "Create Issue" or "Edit Issue" permission is correctly set of the user being used by the email handler?

Since this is a paid Add-on, I would highly recommend raising a support ticket here https://metainf.atlassian.net/servicedesk/customer/portal/1, so that someone from their team can help out to solve this error sooner.

Dominik Suszter January 5, 2025

Hi @Jehan Bhathena

Thanks for your response. I tested the permission helper, and everything is green. The "Email Channels" ("Email Request") works well and creates the issue, but this plugin doesn’t work. I’ll try contacting the plugin developer as you suggested.

Thanks!

Jehan Bhathena
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 5, 2025

Do let us know how it goes 😊

In the mean while if you find this thread helpful please can you mark the Answer as Accepted.

Like Dominik Suszter likes this
0 votes
Katarzyna Sutor
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 11, 2025

Hello Dominik!

Did you found what was the issue? 
I have the same problem and massive amount of tasks waiting, please share with me the solution

Dominik Suszter February 11, 2025

Hello @Katarzyna Sutor

Yes of course.

The issue was caused by setting the default reporter in the mail handlers to the sender's (reporter) account instead of a user with the Service Management role. As a result, the issue could not be created with the request type since the submitter didn't have a proper license (not servicedesk portal license).

To simplify, I set the System Administrator as the default reporter, ensuring no role-related issues occur during creation. The system then updates the reporter afterward.

Here are some images of the implementation:

 

1.jpg

2.jpg

If you have any question please let me know!

 

Best,

Dominik

Katarzyna Sutor
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 12, 2025

Hello @Dominik Suszter 

Thank you so much for your very fast reply, you saved me!

Wish you a great day :)

Like Dominik Suszter likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
10.0.1
AUG Leaders

Atlassian Community Events