-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
2.2
-
1
-
Severity 3 - Minor
-
1
-
Currently, it is not possible to create issues in JSD enabled projects through the IssueManager because it does not take account of the new Service Desk Customer - Portal Access security type, the same is true for all other security checks like comment, add attachments etc. The createIssueObject method below fails with a CreateException, indicating (for create) that the user does not have the CREATE_ISSUE permission:
ComponentAccessor.getIssueManager().createIssueObject(anIssueObject.getReporterUser(), anIssueObject);
The workaround I have applied is to modify the Projects Permission Scheme to add the Role Service Desk Customers for each related JIRA Permission thats required, and this works. The user involved does not start counting toward the JIRA user count (primary attribute of a JSD Portal User), and issues can be created and updated. But, there is then a scary error warning on the Service Desk admin screen:
Two things:
1. API issue creation with portal users as the issue reporter should just work, it doesn't.
2. I'm not sure what ill effects there would be over the workaround of adding Service Desk Customers role in the permission scheme, comments regarding scary warning above?
- relates to
-
JSDSERVER-107 Create a public REST API for JIRA Service Desk
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-1473] Unable to create API issues with Portal Access users as the reporter
Brian Poleykett
added a comment - Is it possible to get a status update on this Bug? Is it likely to be fixed any time soon?
We've encountered the same issue using Jira Service Desk Cloud.
Brian Poleykett
added a comment - Is it possible to get a status update on this Bug? Is it likely to be fixed any time soon?
We've encountered the same issue using Jira Service Desk Cloud. 
MASI Mégalis Bretagne
added a comment - This is one of the things that lead us to give up on using JSD. We use the wonderful JEMH plugin to map different email aliases (same mail box) onto different issue types, assignees, ...etc
We tried to integrate JSD with JEMH but this issue prevents us from fast/easy customer account. Our support team often creates tickets while on the phone with the customer and we still want these tickets to behave just the same as for mail created ones when notifications are sent to the customer.
So that's why we won't use JSD (and because of template editing as well).
MASI Mégalis Bretagne
added a comment - This is one of the things that lead us to give up on using JSD. We use the wonderful JEMH plugin to map different email aliases (same mail box) onto different issue types, assignees, ...etc
We tried to integrate JSD with JEMH but this issue prevents us from fast/easy customer account. Our support team often creates tickets while on the phone with the customer and we still want these tickets to behave just the same as for mail created ones when notifications are sent to the customer.
So that's why we won't use JSD (and because of template editing as well). There are at least 3 side-effect when adding Service Desk Customers role to create/comment issue permissions in the permissions scheme:
- It disables the possibility to change the settings related to Customer Portal access (from People > Customers tab):
- It does not allow to invite new customers (from People > Customers tab):
- Even if you have enabled the "Anyone can sign up for a customer account on my Customer Portal" option before making changes to the permission scheme (compared to what JSD expects), the Sign Up section and button will disappear from the Log In window for new users trying to sign up for the Customer Portal access.
Not sure what other harm can those changes in permission scheme do in the background (PS if there are any, it would be helpful to list them in your documentation so people will be aware of what they are risking with: https://confluence.atlassian.com/display/Cloud/JIRA+Service+Desk+permissions#JIRAServiceDeskpermissions-PortalAccessSecurityTypeAbouttheServiceDeskCustomer-PortalAccesssecuritytype).
I'm hoping for a quick fix as this issue is preventing plugin vendors to properly interact with JSD, meaning potentially lots of unhappy customers.
Priit Parmann
added a comment - - edited There are at least 3 side-effect when adding Service Desk Customers role to create/comment issue permissions in the permissions scheme:
It disables the possibility to change the settings related to Customer Portal access (from People > Customers tab):
It does not allow to invite new customers (from People > Customers tab):
Even if you have enabled the "Anyone can sign up for a customer account on my Customer Portal" option before making changes to the permission scheme (compared to what JSD expects), the Sign Up section and button will disappear from the Log In window for new users trying to sign up for the Customer Portal access.
Not sure what other harm can those changes in permission scheme do in the background (PS if there are any, it would be helpful to list them in your documentation so people will be aware of what they are risking with: https://confluence.atlassian.com/display/Cloud/JIRA+Service+Desk+permissions#JIRAServiceDeskpermissions-PortalAccessSecurityTypeAbouttheServiceDeskCustomer-PortalAccesssecuritytype ).
I'm hoping for a quick fix as this issue is preventing plugin vendors to properly interact with JSD, meaning potentially lots of unhappy customers.
This seems to have been resolved for some time.
If anyone is still having problems, please raise a new help ticket.