Default value isn't set to custom field when create linked issue

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Medium
    • None
    • Affects Version/s: 9.12.15, 10.3.2
    • Component/s: Custom fields
    • 9.12
    • 3
    • Severity 3 - Minor
    • 1

      Issue Summary

      If the Custom field with a default value set is enabled for Project A, when creating a linked issue from Project B, the default value isn’t set to the Custom Field.
      This is reproducible on the Jira Data Center.

      Steps to Reproduce

      1. In Jira Administration > Issues > Custom fields, click Add custom field
      2. Select Select List(single choice) and click Next
      3. Give a name to the custom field, add two options to it and click Next
      4. Select Project A and click Create
      5. Assign the screens of Project A to the custom field and click Update
      6. Click ... next to the newly created custom field and click Configure contexts
      7. Click Edit Default value and set one option as the default value
      8. Create a new ticket in Project A
      9. The default value is automatically populated to the custom field
      10. In the issue ticket of Project B, click More > Create linked issue
      11. Change the Project from Project B to Project A in the pop-out window

      Please refer to the record for the steps to reproduce the issue:
      https://www.loom.com/share/d32dcf0f55e3414b8eaeb25d882fe307?sid=8f3e7bb8-b6f9-4d5f-a489-95c18fd95899

      Expected Results

      The default value is automatically populated to the custom field

      Actual Results

      The default value isn't automatically populated to the custom field

      Workaround

      Update the custom field manually

            Assignee:
            Unassigned
            Reporter:
            Cynthia Wang
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: