-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
Minor
-
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
- Create a Date Picker custom field and name it Start Date (notice both capital letters).
- 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.
- 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.
- duplicates
-
JRACLOUD-79757 Filter columns in issue navigation(listview) are not retained for duplicate customfields, there is one occurrence for duplicate fields in dropdown
- Gathering Interest
Hi everyone,
I am closing this out as a duplicate of an existing request related to the way we combine fields with duplicate names: https://jira.atlassian.com/browse/JRACLOUD-79757
We intentionally combine fields in the issue search UI when they have the same name (case-insensitive). Because of this, when there are multiple combined fields with values we make sure to display both values in the search results so that data is not lost in this combining process.