Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"jira issue list" can't sort by duedate #780

Open
shadyabhi opened this issue Sep 26, 2024 · 0 comments
Open

"jira issue list" can't sort by duedate #780

shadyabhi opened this issue Sep 26, 2024 · 0 comments

Comments

@shadyabhi
Copy link

Describe the bug

I've confirmed that the JIRA issue has a field named duedate via command:- jira issue view TRAFFIC-23977 --raw | jq, however, I'm unable to sort my list of issues by due date.

jira issue list -s Open -a$(jira me) --order-by priority --order-by duedate --columns duedate

Proof that duedate is indeed a valid field name.

➤ jira issue view TRAFFIC-23977 --raw | jq '.fields | to_entries[] | select(.key | startswith("duedate"))'
{
  "key": "duedate",
  "value": "2024-09-30"
}

Please provide following details

  1. JiraCLI Version:
(Version="1.5.2", GitCommit="34221786aaa12d5bc66039d164b6d9587b0799c7", CommitDate="2024-09-20T08:29:56+00:00", GoVersion="go1.23.1", Compiler="gc", Platform="darwin/arm64")
  1. Are you using Jira cloud or on-premise jira server?
SERVER INFO
-----------

Version:         9.4.8
Build Number:    940008
Deployment Type: Server
Default Locale:
  1. What operating system are you using? Also mention version.
Mac, 14.7 (23H124)
  1. What terminal are you using? Also mention version.
iTerm Build 3.5.5

To Reproduce

Steps to reproduce the behavior:

  1. Execute jira issue list -s Open -a$(jira me) --order-by priority --order-by duedate --columns duedate
  2. Observe that issues are not sorted by duedate

Expected behavior

List should be sorted by duedate.

Screenshots

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant