Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-62601

Assignee field is not visible on 'Create Linked Issue' screen even if unassigned issues are disabled

XMLWordPrintable

      Atlassian Update – 30 Aug 2023

      Hi everyone,

      This bug was fixed and released in 9.10 JSW Data Center along with other improvements to the 'Create Linked Issue Screen'.

      The ‘Create Linked Issue Screen' will now have all fields pre-filled with data from the original issue. All the fields available on the create issue screen scheme of the destination project will be available.

      Kind Regards,

      Lucy Devine

      Jira Service Management, Data Center

      Summary

      Assignee field is not visible on 'Create Linked Issue' (functionality available for Business/Service Desk projects on JIRA 7 and above) screen even if unassigned issues are disabled on the instance. On the regular 'Create Issue' screen the field is show normally.

      Steps to Reproduce
      1. Go to General Configuration and turn off the option 'Allow Unassigned Issues'
      2. Create a issue on a Business or Service Desk project. Note that the assignee field appears, if it has already been added to the respective create issue screen.
      3. On the Issue View screen of the newly created issue, select More > Create Linked Issue
      4. Note that the assignee field does not appear, even though it is theoretically a required field. The linked issue will use the default assignee for the project, however.
      Work-around

      This is not possible to add the Assignee field to the 'Create Linked Issue' screen. To have issues assigned to users other than the default it is required to manually edit the linked issue and change the assignee.

              Unassigned Unassigned
              agoncalves Arthur Gonçalves (Inactive)
              Votes:
              113 Vote for this issue
              Watchers:
              75 Start watching this issue

                Created:
                Updated:
                Resolved: