When moving an issue to another project or issue type, if the originating project/issue type isn't part of the custom field's context, the CF is presented as a required field

XMLWordPrintable

    • 6
    • Severity 3 - Minor

      Issue Summary

      When trying to move an issue and its Sub-task from one project to another, it's requested to enter a value for a field that is NOT required in the target/origin project

      Steps to Reproduce

      1. Create an Issue for a Project A
      2. Remove Project A from a specific Custom Field Context
      3. Perform a move on the issue from Project A to the Project B

      Expected Results

      The Move process should NOT require the custom field and the process should be completed.

      Actual Results

      The Custom Field from which Project A was removed from its context starts being requested.

      Workaround

      Add the Originating project to the Custom Field's Context and the move works without requiring the field.

      You might also be able to complete the move operation without actually providing any values for the fields that are displayed as required.

            Assignee:
            Unassigned
            Reporter:
            Marcelo B
            Votes:
            5 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: