nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filter sorting by DateTime Picker CustomField not sorting properly

andrea.rodifalanga

Hi all,

I've defined a Custom Field in my project, of DateTime Picker type. Accordingly, the search template is Date Time Range Picker (the only other option would be "none", which is no good).

That Custom Field is used in a Filter like this:

Not sure what I'm doing wrong, but the resulting sorting in the Dashboard where that filter is used is wrong. (see screenshot)

Nevermind the differences in datetime formats, the real issue is that the sorting order is quite wrong and doesn't seem to follow any particular logic, and it's the same if I reverse the sorting.
Any suggestions?
Many thanks in advance for any assistance.

Accepted answers

Fazila Ashraf

Hi @andrea.rodifalanga

I tried to reproduce the issue but the sort order works ok to me.

Do you know what could be different in your environment?

Screenshot 2024-06-21 at 14.52.05.png

All comments

Fazila Ashraf

Hi @andrea.rodifalanga

I tried to reproduce the issue but the sort order works ok to me.

Do you know what could be different in your environment?

Screenshot 2024-06-21 at 14.52.05.png

andrea.rodifalanga

Hi @Fazila Ashraf thanks for the quick reply.
Sadly, no. The project and all the resources used in it are new and dedicated. (ie, not shared with other projects etc).

I also tried to strip the JQL query of all the extra conditions, like yours, but the result is the same.

Fazila Ashraf

Interesting! Could you create a new Date time custom field and try to reproduce the issue?

That is to verify whether it is a strange behaviour just for the 'Issue deadline' or any date time field in your site.

Recommend you this as it is not reproducible in my site.

andrea.rodifalanga

This is interesting indeed; so, after your suggestion I created a new "deadline test" field, added it to the relevant screens and used it in the filter alongside with the buggy "issue deadline" one.
It worked perfectly.
Then I removed the test field from the project, and reverted to the initial conditioin where only "issue deadline" was deployed... and it worked

Don't know what it was; probably a reindexing or something like that.

Thanks for your assistance

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud