Set a validator on the create issue transition in the workflow to perform additional checks (e.g. we added a check on a different role from 'customer-users' via a scriptrunner script)
However, this approach merely generates an error on the final step in the request creation on the portal, which isn't veryt nice to the end-user who just spent time entering all the fields presented to him.
Also, you would't want the read-only users to change the sharing on the request (add/remove participants / organizations / )
So, while technically possible to prevent the create, it's not a very nice way to do it + it comes with a bucket of limitations when considering the full lifecycle of a request.
Hope this helps,
Currently, any Service Desk Customers without the Create Issues permission are also not able to view past requests:
Incidentally, they also cannot be added as participants:
Finally, there is a feature request asking for that ability:
So, at this time, it is not currently possible. I encourage you to vote on the above links, the first two in order to show you are affected by this bug, and the final one to show your support for implementing such a feature. On that link please also provide your use case since it helps us to best understand your requirements.
Thank you for understanding!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG