-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
None
-
3
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Problem definition
Request type is always No match if
- the issue has been created directly in JIRA
- the issue type has changed by editing this field (same workflow)
- the issue type has changed by moving the ticket (same project but different workflows)
- the ticket has been moved between different Service Desk projects
Suggested solution
Automatically update the request type corresponding to its issue type
Workaround
If the Move operation involves status changing, you can use the workaround below:
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Charlie
Jira Service Management, Server & Data Center