How to add a Due Date with `issue create` or `issue edit`

[bemeyert]

Describe the bug

Please provide following details

1. JiraCLI Version:

   1.4.0-1 (Arch AUR)
   

2. Are you using Jira cloud or on-premise jira server?

   Using Jira Server (v8.20.24#820024-sha1:e6f6b79)
   

3. What operating system are you using? Also mention version.

   Archlinux
   

4. What terminal are you using? Also mention version.

   rxvt-unicode (urxvt) v9.31
   

To Reproduce

Steps to reproduce the behavior: I want to add a due date to a ticket but don't know how. I already tried to use custom like jira issue create --type Task --summary "$summary" --custom "duedate=2023-01-11" but I get this warning:

Using config file: /home/shorty/.config/.jira/.config.yml                                                                                                   
                                                                                                                                                            
Some custom fields are not configured and will be ignored. This will fail with error in the future release.
Please make sure that the passed custom fields are valid and configured accordingly in the config file.                                                     
Invalid custom fields used in the command: duedate                                                                                                          
⠏ Creating an issue...

Any help would be much appreciated.

[ankitpokhrel]

Hi @bemeyert, is this field configured in your config? You can find some details here

[squatched]

I'm having this same issue so I'll give some details. No, the field is not listed in .config.yml, and when I look at my issue's API output, the value of an issue with this already set does not have a key of the form customfield_###, the key for the value is simply duedate.

[da0ist]

I'm having the same issue. Anyone find an alternative or workaround?

[stevommmm]

I'm having the same issue. Anyone find an alternative or workaround?

Adding it to the .config.yml allows for it to be edited via CLI with --custom "duedate=1970-01-01"

issue:
    fields:
        custom:
            - name: duedate
              key: duedate
              schema:
                datatype: date

[4SH-gaupee]

Hi, is there an "easy" way to integrate the due date as a metadata ?