Support for managing fixVersions in jira-cli

[rcoleman-hivewatch]

I'd like to be able to list, add, and delete fixVersions in a given jira project from this tool. does anyone know if this is currently support or planned in future work?

[JonathanHuot]

Support of "Jira Releases" is a great idea.
Proposal:

$ jira release -h
Interactive manage releases in a given project. See available commands below.

USAGE
  jira release [flags]

MAIN COMMANDS
  archive 
  unarchive
  release 
  unrelease 
  create      
  delete      
  edit        
  view       

FLAGS
  -h, --help   help for issue

INHERITED FLAGS
  -c, --config string    Config file (default is ../.config/.jira/.config.yml)
      --debug            Turn on debug output
  -p, --project string   Jira project to look into (defaults to ../.config/.jira/.config.yml)

ALIASES
  releases

LEARN MORE
  Use 'jira <command> <subcommand> --help' for more information about a command.
  Read the doc or get help at https://github.com/ankitpokhrel/jira-cli

[rcoleman-hivewatch]

i'd add a list subcommand to that, but yes - spot on.

[ankitpokhrel]

The release list command will be included in the upcoming release. Other commands still needs to be worked on. Contributions are welcome :)

[wfife-nsg]

I have partially implemented this, though not the exact same commands as in the discussion above. So far in my local fork I've implemented this command line structure.

Example command line usage for the create functionality.

# Create a version with minimal info
$ jira release create --name "Version 1.0"

# Create a version with full details
$ jira release create --name "v2.0" --description "Major release" --released --release-date "2024-12-31"

# Create in a specific project
$ jira release create -p PROJECT --name "v1.5"`

Example command line usage for the edit functionality.

# Edit version by ID
$ jira release edit 10000 --name "Version 1.0 Updated"

# Edit version by name
$ jira release edit "v1.0" --name "v1.1" --description "Updated version"

# Mark version as released
$ jira release edit 10000 --released

# Update release date
$ jira release edit "v1.0" --release-date "2024-12-31"

# Use --no-input to skip prompts
$ jira release edit 10000 --name "v2.0" --no-input`

Some follow up questions, would it be better to break each release subcommand out into it's own PR, or would you prefer one consolidated PR?

I'd be happy to also implement delete and view functionality if wanted.