Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-17837

Default Assignee at Request Type level is not Reflected on Jira Create Issue Screen

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • Issue View
    • None

      Issue Summary

      • When we Set Default Assignee in the Jira Service management > Request Type > Assignee Field under the Parameter "Use Preset Value and Hide from Portal" 
      • We notice that this setting is not acknowledged in the Jira Create Issue Screen , and the Assignee Field Shows "Automatic" , instead of the Assignee set

      Steps to Reproduce

      1. Naviate to any JSM Project > Settings > Any Request Type 
      2. Add Assignee Field to the Request Form , and select "Use Preset value and hide from Portal"
      3. Add any Agent as the Default Assignee 
      4. Then on same screen, click on Create on top right, and create issue with this Request Type
      5. Ensure to check box : "Use Request Type Fields"
      6. We see that the Assignee Field shows "Automatic" instead of the Assignee set on Request Type.
      7. We also notice that after we create the setting of Default Assignee is not adhered to.

      Expected Results

      Show the Default Assignee configured on the Request Type Level

      Actual Results

      Shows the term "Automatic"

      Workaround

      • Can look to use Automation for Jira or Workflow PostFunction to add the Assignee after the ticket has been created. 

              Unassigned Unassigned
              b84bdacbe3bf Aslam K M
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: