Details
-
Suggestion
-
Resolution: Duplicate
-
1
-
6
-
Description
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Having to manually choose a project when raising a service desk request, issue can easily end up in wrong projects or with wrong issue types.
This particularly happens in environments where high numbers of projects are using service desk and/or the reporters are external users or users who do not frequently use that instance of JIRA.
When using a multi-level select or a (sub-)component field in the create issue screen, you can automate which project the request ends up in, and which issue-type it receives.
Hi everyone,
Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later.
Cheers,
The JIRA Service Desk team
Attachments
Issue Links
- duplicates
-
- Gathering Interest
- incorporates
-
- Closed
- is related to
-
- Gathering Interest
-
- Gathering Interest