Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-36167

Required fields are not set when issue type is changed by inline edit.

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Summary

      Required fields are not set when Issue Type is changed by an Inline Edit

      Steps to Reproduce

      1. Take a standard JIRA installation and add a field, e.g. "Detection Phase", to Bug issue type. Make the field required in the field configuration.
      2. Create an issue of some other type.
      3. Change the type to Bug via inline edit.
      4. Result: The required field has no value.

      Expected Results

      Required fields are propmted to be updated

      Actual Results

      Issue type can be changed via inline edit and required fields are not populated.
      Another example: Changing an issue type to Epic via inline edit does not require an "Epic Name" to be set

      Workaround

      • Use the More > Move Function to change the issue type

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-63804 Epic Name can be saved as empty when changing issue type

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-39849 Leaving required field empty when changing task type from "New Feature" to "Epic"

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-36167 Required fields are not set when issue type is changed by inline edit.

          • Medium - Medium priority issues
          • Gathering Impact
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-36946 Edit Screen not updated when Issue Type changed

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-16334 Converting issues to Epics leaves the Epic Name field without a value

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              rtandon@atlassian.com Ruchi Tandon
              Votes:
              22 Vote for this issue
              Watchers:
              26 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: