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

Mixed values in List View when Date Picker custom field is named Start Date

XMLWordPrintable

      Issue Summary

      Creating a Date Picker custom field with the name: Start Date (similar name to the locked Start date system field) results in problematic behavior with filters.

      As mentioned in JRACLOUD-85302 it's not possible to add the newly created custom field as a Column for a filter's List View. Nonetheless the List View in the filter already includes the  locked system field Start date the values displayed for the locked system field correspond to the values related to the Start Date custom field that was created.

      Steps to Reproduce

      1. Create a Date Picker custom field and name it Start Date (notice both capital letters).
      2. Edit an existing filter or create a new filter and click on the Configure Columns option for the List View of the filter and make sure that the Start date system field is added as a column.
      3. Notice that the values related to the Start date system field correspond to the values related to the newly created  Start Date custom field for each different issue.

      Expected Results

      The values displayed in the column related to the Start date system field in the filter's List View should not be mixed with the values related to the newly created  Start Date custom field for each different issue.

      Actual Results

      The values displayed in the column related to the Start date system field in the filter's List View correspond to the values related to the newly created  Start Date custom field for each different issue.

      Workaround

      Rename the Date picker custom field to something unique (e.g. New Starting Date) for it to show up in the Start date column in the filter appropriately.

              Unassigned Unassigned
              d74b08d0bd4c Daniel Ocando Espinoza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: