Use JIRA_API_TOKEN from 1password CLI helper

[rsanheim]

1. Setup 1password desktop app integration and verify it in your terminal
2. Add your JIRA token to your 1password vault
3. Add an export for JIRA_API_TOKEN to your shell profile using the secret reference syntax - below is an example, your vault will differ.

export JIRA_API_TOKEN="op://my-vault/jira-item/credentials/api-token"

1. Now, run all jira commands via op run - you can create a wrapper script for this, just make sure its first in your PATH ahead of the real jira command. You'll want to update the path to actual jira binary for your system, below is homebrew on apple silicon macs.

#!/usr/bin/env bash

# Wrapper around the jira command that sets the JIRA_API_TOKEN environment variable.
# It uses the op command to get the JIRA_API_TOKEN from the 1Password CLI and then runs the jira command.

op run -- /opt/homebrew/bin/jira "$@"

1. You should be all set, you can run jira me to verify

[rsanheim]

Looks like op run will prevent interactive mode by default, as sets things to no-tty: https://www.1password.community/discussions/developers/op-run-changes-stdout-and-stderr-to-not-be-ttys-when-masking/26040

I haven't used the TUI much for jira-cli and tend to use it for scripting or plaint text views, so not a big deal breaker for my use case, but YMMV.

edit Adding --no-masking to the op run call does fix things and re-enable the TUI by default. Even w/o masking, grabbing the token from 1password feels much safer than keeping it in a persistent env var in your shell.