'jira issue list' always prints 'KEY'

[the-real-neil]

trafficstars

Describe the bug jira issue list always prints the KEY column, even when --columns is overridden.

Please provide following details

1. JiraCLI Version:

   (Version="v1.5.1", GitCommit="", CommitDate="", GoVersion="go1.22.5", Compiler="gc", Platform="linux/amd64")
   

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

   SERVER INFO
   -----------
   
   Version: 	 9.12.10
   Build Number: 	 9120010
   Deployment Type: Server
   Default Locale:  
   

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

   $ cat /etc/os-release
   PRETTY_NAME="Ubuntu 22.04.4 LTS"
   NAME="Ubuntu"
   VERSION_ID="22.04"
   VERSION="22.04.4 LTS (Jammy Jellyfish)"
   VERSION_CODENAME=jammy
   ID=ubuntu
   ID_LIKE=debian
   HOME_URL="https://www.ubuntu.com/"
   SUPPORT_URL="https://help.ubuntu.com/"
   BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
   PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
   UBUNTU_CODENAME=jammy
   

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

   st 0.9.2
   

To Reproduce

Steps to reproduce the behavior:

Only --columns=KEY prints a single column:

$ for column in KEY, TYPE, SUMMARY, STATUS, ASSIGNEE, REPORTER, PRIORITY, RESOLUTION, CREATED, UPDATED, LABELS, ; do jira issue list --plain --no-headers --no-truncate --paginate=1:1 --columns="${column}" | awk -F'\t' '{print NF}' ; done
1
2
2
2
2
2
2
2
2
2
2

Expected behavior

Each --columns="${column}" should print a single column:

$ for column in KEY, TYPE, SUMMARY, STATUS, ASSIGNEE, REPORTER, PRIORITY, RESOLUTION, CREATED, UPDATED, LABELS, ; do jira issue list --plain --no-headers --no-truncate --paginate=1:1 --columns="${column}" | awk -F'\t' '{print NF}' ; done
1
1
1
1
1
1
1
1
1
1
1

Screenshots Not applicable.

Additional context Not applicable.

[ankitpokhrel]

@the-real-neil This was initially by design since the TUI always need to have access to the issue key for other commands like view and move to work. I think we can remove this when using --plain flag tho.