Details
-
Suggestion
-
Resolution: Timed out
Description
Hi Everyone,
Thank you for previously raising this feature request and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each feature request but admit that not each one will be implemented. To continue the culture of being honest and open, we are closing this ticket to focus on our upcoming roadmap for all Jira Service Management Cloud users. You can visit Atlassian Cloud Roadmap to learn more about what was recently released and the upcoming roadmap.
Thank you again for providing valuable feedback to our team!
Arjun Ganapathy
Jira Service Management Cloud team
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
The issue collector allows only for the issue type to be chosen when setting up the collector.
If the issue collector is intended to be used with a Service Desk project, these issues will not show up in queues and under requests in the Service Desk itself due to the absence of a value for the request type field.
Adding the request type as a configuration option when setting up the issue collector allows for it to be used for Service Desk projects.
Additionally, if the issue collector is configured to Attempt to match user session of submitter or submitter email address, if the user does not have Application access (license) and Create issues permission for the project, the default issue reporter you specify in it will be used as the issue's reporter, and this means that all customers will have their issues created by the default reporter, so this restriction would also require being addressed to allow Customers using Issue collectors seamlessly for Service Desk.
Attachments
Issue Links
- is related to
-
- Gathering Interest