palashkulsh / jira-cmd Goto Github PK

How do I review comments, make a comment, and create a ticket to a given Epic?

couldn't find support for extending the commandset
So I fixed this for now using this bash-wrapper

#!/bin/bash
# bash wrapper with preset-support for https://www.npmjs.com/package/jira-cmd

if [[ ! -n $1 ]]; then 
  jira | while IFS='' read line; do 
    echo "$line"
    [[ "$line" =~ "Works with sprint boards" ]] && { grep ") #" $0 | sed 's/) #//g'; }
  done | grep -vF "[[" # why this last grep?
  exit 0 
fi
{
  case "$1" in

    last) #                   Shows issues since last week
          jira jql "created > $(date --date="last week" +"%Y-%m-%d" | tr "[:upper:]" "[:lower:]" ) and created < $(date --date="tomorrow" +"%Y-%m-%d" | tr "[:upper:]" "[:lower:]" )"
          ;;
    *)
          jira "$@"
          ;;
  esac
} | grep -v '─' | more -R

Example

  Usage: jira [options] [command]

  Commands:

    ls [options]           List my issues
    start <issue>          Start working on an issue.
    stop <issue>           Stop working on an issue.
    review <issue> [assignee] Mark issue as being reviewed [by assignee(optional)].
    done [options] <issue> Mark issue as finished.
    running                List issues in progress.
    jql <query>            Run JQL query
    search <term>          Find issues.
    assign <issue> [user]  Assign an issue to <user>. Provide only issue# to assign to me
    comment <issue> [text] Comment an issue.
    show [options] <issue> Show info about an issue
    open <issue>           Open an issue in a browser
    worklog <issue>        Show worklog about an issue
    worklogadd [options] <issue> <timeSpent> [comment] Log work for an issue
    create [project[-issue]] Create an issue or a sub-task
    config [options]       Change configuration
    sprint [options]       Works with sprint boards
--> last                   Shows issues since last week                                                 
    With no arguments, displays all rapid boards
    With -r argument, attempt to find a single rapid board and display its active sprints
    With both -r and -s arguments attempt to get a single rapidboard/ sprint and show its issues. If a single sprint board isnt found, show all matching sprint boards

  Options:

    -h, --help     output usage information
    -V, --version  output the version number

but would be nice as a native feature

Just installed jira cmd
and jira ls gives me no issues.
I'm using jira cloud (not hosted jira).
I guess that something is happening under the hood but no error is thrown so I can tell what is the cause.

jira -V
v0.5.4

Turns you that you expect that a status called "In Review" here we only have To Do, In Progress and Done. Would be interesting if those status could be in a config file stored along with our credentials.

The only way to work around this issue is by changing the line:
+ '+AND+status+in+(Open,"In+Progress",Reopened,"To+Do","In+Review")'

When I go through create flow...I don't receive the JIRA ticket back....I went through the whole flow but I don't know if it worked or not because I don't get back a ticket.

If I run "jira show -o duedate PRO-373" where PRO-373 has a due date, then this date is returned. If I then remove the due date from PRO-373 (or select another issue without due date), then jira-cmd crashes:

% jira show -o duedate PRO-373
2015-10-15
% jira show -o duedate PRO-373
/home/meme/bin/node.js/node-v0.12.0-linux-x64/lib/node_modules/jira-cmd/lib/jira/describe.js:31
              console.log(res.body.fields[field].name);
                                                ^
TypeError: Cannot read property 'name' of null
    at /home/meme/bin/node.js/node-v0.12.0-linux-x64/lib/node_modules/jira-cmd/lib/jira/describe.js:31:49
    at Request.callback (/home/meme/bin/node.js/node-v0.12.0-linux-x64/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:586:3)
    at Request.<anonymous> (/home/meme/bin/node.js/node-v0.12.0-linux-x64/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:133:10)
    at Request.emit (events.js:107:17)
    at IncomingMessage.<anonymous> (/home/meme/bin/node.js/node-v0.12.0-linux-x64/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:714:12)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)

I have jira-cmd 0.4.1 and JIRA 6.3.13

I believe status "Open" has been renamed to "To Do"?
The version of JIRA we are using is (v6.2.5#6262)

https://github.com/germanrcuriel/jira-cmd/blob/8353dfdd2ae86757135e9985aabd38d66810186f/lib/config.js#L6

I don't think this should be here at all. A better idea would be to enable TLS check by default and let people disable it manually in a config file of sorts or inform them they should add their CA for self-signed certificates using NODE_EXTRA_CA_CERTS variable.

I understand some are having issues with their self-hosted Jira instances and everything, but most of us would prefer to make security decisions ourselves. Disabling this security feature for everyone is a bad choice.

Running
jira comment STH-100 "Some comment" yields a Comment to issue [STH-100] was posted!. but the comment doesn't show on Jira, and the comment count on jira show [STH-100] doesn't doesn't change

Hi,

I get a 403 error if I use "jira "
How can I debug? :)

Thanks

Thanks for this tool. It is really handy and saved my time.

I've successfully logged my work and time.

I usually write my task in detail using line break and '-' character, but I found I can't use them.
Is there any solution for this?

One more question, what is date format for start date?

Thanks!

@germanrcuriel thanks for adding me as a contributor, can you please share your vision for this project, and things I should keep in mind in general.

the things on top of my head are

1. stable updates.
2. more functionalities

jira ls returns no issues, despite the fact that my user has issues assigned to me.

Hi @germanrcuriel I did a few improvements to jira done command but I'm going to wait for #33 to be ok to merge.

The feature that I'm going to introduce is the following:

Resolution

When -r is absent, the most relevant would be assumed as defined in:

https://confluence.atlassian.com/display/JIRA/Defining+Resolution+Field+Values

If an invalid resolution was informed the following will appear:

Time Spent

The -t flag is also optional and if present we will automatically add a worklog to that issue. If abscent, nothing about time management would be done.

What do you think?

jira -V
v0.5.4

node -v
v8.16.0

Then, config per steps:

Jira URL: https://co.atlassian.net/
Username: [email protected]
Password:
Information stored!

Then:

jira ls
No issues

$ jira config

TypeError: callback is not a function
    at Object.setConfig (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/lib/auth.js:62:24)
    at Command.<anonymous> (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/bin/jira.js:364:22)
    at Command.<anonymous> (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/node_modules/commander/index.js:254:8)
    at emitTwo (events.js:126:13)
    at Command.emit (events.js:214:7)
    at Command.parseArgs (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/node_modules/commander/index.js:471:12)
    at Command.parse (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/node_modules/commander/index.js:378:15)
    at /Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/bin/jira.js:402:13
    at Object.execCb (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/node_modules/requirejs/bin/r.js:1941:33)
    at Module.check (/Users/liftco/.nvm/versions/node/v8.16.0/lib/node_modules/jira-cmd/node_modules/requirejs/bin/r.js:1116:51)

Previously (yesterday), this was working fine. I even uninstalled via npm and rm -rf ~/.jira/config.json. Same results, No issues.

It appears the callback in setConfig is undefined at jira-cmd/lib/auth.js:63:24:

setConfig: function (callback) {
            var that = this;
            if (this.checkConfig()) {
                this.updateConfig();
                console.log('callback', callback); // callback undefined
                return callback(true);
            } else {
                if (!fs.existsSync(this.cfgPath)) {
                    fs.mkdirSync(this.cfgPath);
                }

I love this CLI tool, any tips on how to debug?

Hi @germanrcuriel
Do you think that a feature like "default board" for jira sprint command would be useful?

My main goal here it's to make possible to just type jira sprint with no arguments.

The board would be inherited from the default_board option when there is no -r flag passed. Also the -s, when absent, we will assume that it would be the current active sprint.

In my scenario we only use one board and it's really annoying having to carry that -r flag a all the time along with the -s.

What do you feel about that? Do you think that it is only me or usually people frequently switch between boards via command line?

Just tried out #28 locally and am getting:

C:\Projects\jira-cmd\lib\jira\ls.js:64
      var statuses = config.options.available_issues_statuses.join('", "')
                                   ^
TypeError: Cannot read property 'available_issues_statuses' of undefined
    at Object.ls.showAll (C:\Projects\jira-cmd\lib\jira\ls.js:64:36)
    at C:\Projects\jira-cmd\bin\jira.js:37:16
    at Object.Auth.setConfig (C:\Projects\jira-cmd\lib\auth.js:51:16)
    ...

Maybe provide a config upgrade path, @igorescobar?

hi @germanrcuriel can you please publish fresh on npm.
Thanks

When I run jira and try to input my username, I get back the error:

(node) tty.setRawMode is deprecated. Use process.stdin.setRawMode     instead.
    tty.js:20
    throw new Error('can\'t     set raw mode on non-tty');
        ^

Error: can't set raw mode on     non-tty
    at Object.<anonymous> (    tty.js:20:11)
at Object.deprecated (    internal/util.js:55:15)
at setRawMode (C:\Users\dgolant\AppData\Roaming\nvm\v4.4.5\node_modules\jira-cmd\node_modules\commander\    index.js:945:11)
at Command.password (C:\Users\dgolant\AppData\Roaming\nvm\v4.4.5\node_modules\jira-cmd\node_modules\comm    ander\index.js:948:3)
at Object.Auth.ask (C:\Users\dgolant\AppData\Roaming\nvm\v4.4.5\node_modules\j    ira-cmd\lib\auth.js:36:17)
at C:\Users\dgolant\AppData\Roaming\nvm\v4.4.5\node_modules\jira-cmd\lib\auth.    js:70:18
at C:\Users\dgolant\AppData\Roaming\nvm\v4.4.5\node_modules\jira-cmd\lib\auth.    js:46:13
at Socket.<anonymous> (C:\Users\dgolant\AppData\Roaming\nvm\v4.4.5\node_modules\jira-cmd\node_modules\co    mmander\index.js:830:5)
at Socket.g (    events.js:260:16)
at emitOne (    events.js:77:13)

Hi, I encountered this problem with worklog subcommand:

jira.js worklog APM-42231
/home/kokos/foo/jira-cmd/node_modules/cli-table/lib/cli-table/index.js:180
      var contents = item.toString().split("\n").reduce(function (memo, l) {
                          ^
TypeError: Cannot call method 'toString' of undefined
    at /home/kokos/foo/jira-cmd/node_modules/cli-table/lib/cli-table/index.js:180:27
    at Array.forEach (native)
    at generateRow (/home/kokos/foo/jira-cmd/node_modules/cli-table/lib/cli-table/index.js:179:11)
    at /home/kokos/foo/jira-cmd/node_modules/cli-table/lib/cli-table/index.js:273:16
    at Table.forEach (native)
    at Table.toString (/home/kokos/foo/jira-cmd/node_modules/cli-table/lib/cli-table/index.js:256:10)
    at /home/kokos/foo/jira-cmd/lib/jira/worklog.js:75:27
    at Request.callback (/home/kokos/foo/jira-cmd/node_modules/superagent/lib/node/index.js:586:3)
    at Request.<anonymous> (/home/kokos/foo/jira-cmd/node_modules/superagent/lib/node/index.js:133:10)
    at Request.emit (events.js:95:17)
    at IncomingMessage.<anonymous> (/home/kokos/foo/jira-cmd/node_modules/superagent/lib/node/index.js:714:12)
    at IncomingMessage.emit (events.js:117:20)
    at _stream_readable.js:944:16
    at process._tickCallback (node.js:442:13)

BTW, Did you plan further development of this package?

edit: adding to worklog works

Is there an option to output content as json rather than in an ascii table?

Document usability of api token in authentication instead of password

I was wondering if there is an alternative to storing a username and password on the filesystem. I'm a little hesitant to use this because of security concerns.

I do:

npm install -g jira-cmd
jira ls
[put pass/user/URL]
jira ls <- breaks because of "In Review" stage present in ~/.jira/config.json
[ edit ~/.jira/config.json and remove "In Review" stage]
jira ls <- starts to work fine.

Now I want to create a bug case:

$ jira create
Type the project name or key: CS
Type the parent task key (only the numbers) if exists, otherwise press enter:
(1) Bug
(2) New Feature
(3) Task
(4) Improvement
(10000) Epic
(10001) Story
Select issue type: 1
Type the issue title: "we"
Type ths issue description: "f"
(1) Highest
(2) High
(3) Medium
(4) Low
(5) Lowest
Select the priority: 2
/usr/local/lib/node_modules/jira-cmd/lib/jira/create.js:270
return console.log(res.body.errorMessages.join('\n'));
^
TypeError: Cannot read property 'join' of undefined
at /usr/local/lib/node_modules/jira-cmd/lib/jira/create.js:273:54
at Request.callback (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:586:3)
at Request. (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:133:10)
at Request.emit (events.js:107:17)
at IncomingMessage. (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:714:12)
at IncomingMessage.emit (events.js:129:20)
at _stream_readable.js:908:16
at process._tickCallback (node.js:355:11)

I added some printouts:

267 .end(function (res) {
268 //console.log("--res--\n");
269 //console.log(res);
270 if (!res.ok) {
271 //console.log(config.auth.token);
272 console.log(res.body.errorMessages);
273 return console.log(res.body.errorMessages.join('\n'));
274 }

271 shows good auth token. jira ls shows me JIRA issues etc.
272 shows undefined.
269 shows whole bunch of sensitive data.

Weird:

    _header: 'GET /rest/api/2/issue HTTP/1.1\r\nHost: tpjira.atlassian.net\r\naccept-encoding: gzip, deflate\r\nCookie: \r\nauthorization: ........<token is here>

And it's getting:

   text: '<!DOCTYPE html><html><head><title>Apache Tomcat/8.0.20 - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body><h1>HTTP Status 405 - Method Not Allowed</h1><div class="line"></div><p><b>type</b> Status report</p><p><b>message</b> <u>Method Not Allowed</u></p><p><b>description</b> <u>The specified HTTP method is not allowed for the requested resource.</u></p><hr class="line"><h3>Apache Tomcat/8.0.20</h3></body></html>'

Which is expected, since Apache says it supports either POST or OPTIONS.

I'd expect this code to be issuing POST request, not GET request.

If I visit foo.atlassian.net/issues/?filter=10062 I can write some JQL in the GUI. I can also select the columns which get displayed.

I would like to likewise set the output columns. Currently the output columns are:

Key
Priority
Summary
Status

Say I want to include Epic Link and Assignee here, how would I do this? If you point to a starting point in the codebase I can probably create PR to add this functionality if not already existing :D.

After each command it seems I need to ctrl+c to finish the process. I'm using oh-my-zsh on OSX 10.8.3

Hi, nice command.

The only thing I miss is an easy to parse output.

Git does it with porcelain option

Thank you

What is your jql for jira ls and jira running?
I have alot of issue in my projects but when I run jira ls or jira running in terminal it return

No issues 

Even when I run jira jql reported with the builtin reported jql query, it return No issues but if I copy&paste the reported jql to web and click search, it return many (2345 issues)
Here is my setting in config.json and my issues in server.
setting in config.json
issues in server

I run jira ls and I get an error message that there is no value 'In Review' for field 'status'. Apparently this is due to a specific set of statuses in our Jira.

I have a filter 'My Issues' in Jira where the list of issues is configured. I found a temporary solution by replacing the + '+AND+status+in+(Open,"In+Progress",Reopened,"To+Do","In+Review")'with + '+AND+filter=12308' in the lib/jira/js.js .

It would be useful to be able to choise the favorite filter at the configuration stage to list issues.

The #35 lists my setup. Once I made jira-cmd work, I created the issue from the Web GUI.

It's called CS-519.

Next I do:

jira worklogadd CS-519 3h something

I don't see these changes reflected in the Web GUI. It seems like nothing has been changed. Output on the console:

wkoszek|19:07:07|0|/Users/wkoszek/.jira$ jira worklogadd CS-519 3h something
Worklog to issue [CS-519] was added!.

Hi,

I'm not using a "cloud" version of Jira, here we have a hosted version and it's connected to Active Directory.

I've setup the correctly, answering all questions asked.

After running jira ls I got this error: UNABLE_TO_VERIFY_LEAF_SIGNATURE. I could work around this issue by setting an env variable:
export NODE_TLS_REJECT_UNAUTHORIZED=0

Now I'm getting the error: AUTHENTICATION_DENIED but my credentials are fine. The same used in the web interface.

Any ideas?

node version 0.10.26

When I run any command correctly, I'm getting the following error:

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED xxx.xxx.xxx.xxx:443
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)

Do I need to need to enable anything in Jira to allow secure requests?

We use the timetracking feature of jira a lot, would be awesome be able to do something like:

jira log-work <issue> 90m 'fixed some bugs' or something.

For Windows environments, the configuration file(s) should be stored in the user's profile directory, be it the local or roaming profile. These would be the APPDATA environment variable (roaming profile, can be "transported" across PCs) or the APPDATALOCAL, which is the user's machine-specific profile directory.

In Windows, the HOME* environment variables (home, homedrive, homepath, homeshare) are values which are set when the user is authenticated via AD, which means that any user who run the script on Windows from a non-AD connected system is likely to run into several issues, mostly that computing the .jira configuration directory will result in being the equivalent of ./.jira, or possibly also /.jira. The latter, for non-priviledged accounts, would fail catastrophically. For priviledged users on shared systems, that could lead to their credentials being used by other users, not to mention the credentials also being compromised for anyone savvy enough to figure out the the source of the data, and how to reverse it.

hey @germanrcuriel , I've bumped a major version, need your help in publishing on npm.

Seems like jira Agile doesn't have the transition "To Do". Te correct name for it would be "Stop Progress". So the command jira stop doesn't work...

Sounds good to have a config like this:

{
  "auth": {
    "url": "https://my.jira.net.br/",
    "user": "user",
    "token": "token"
  },
  "options": {
    "jira_stop": {
      "status": "Stop Progress"
    },
    "jira_start": {
      "status": "In Progress"
    },
    "jira_review": {
      "status": "In Review"
    },
    "jira_done": {
      "status": "Done"
    },
    "available_issues_statuses": [
      "Open",
      "In Progress",
      "Reopened",
      "To Do"
    ]
  }
}

What do you think?

Would it be easy to add the date of a worklog?

Mac-mini-seryh:~ seryh$ jira search 166

/usr/local/lib/node_modules/jira-cmd/lib/jira/ls.js:25
return console.log(res.body.errorMessages.join('\n'));
^
TypeError: Cannot call method 'join' of undefined
at /usr/local/lib/node_modules/jira-cmd/lib/jira/ls.js:25:55
at Request.callback (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:586:3)
at Request. (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:133:10)
at Request.EventEmitter.emit (events.js:95:17)
at Stream. (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/index.js:714:12)
at Stream.EventEmitter.emit (events.js:117:20)
at Unzip. (/usr/local/lib/node_modules/jira-cmd/node_modules/superagent/lib/node/utils.js:120:12)
at Unzip.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:919:16
at process._tickCallback (node.js:419:13)

I'm working with an older jira cloud project that tracks issues for an open-source project (so maybe isn't getting latest jira software because on a free plan?) Anyway, when I run jira show CORE-1110 I get an error:

/usr/lib/node_modules/cmd-jira/lib/jira/describe.js:75
            {'Subtasks': res.body.fields.subtasks.length},
                                                 ^

TypeError: Cannot read property 'length' of undefined
    at /usr/lib/node_modules/cmd-jira/lib/jira/describe.js:75:50
    at Request.callback (/usr/lib/node_modules/cmd-jira/node_modules/superagent/lib/node/index.js:586:3)
    at Request.<anonymous> (/usr/lib/node_modules/cmd-jira/node_modules/superagent/lib/node/index.js:133:10)
    at emitOne (events.js:77:13)
    at Request.emit (events.js:169:7)
    at Stream.<anonymous> (/usr/lib/node_modules/cmd-jira/node_modules/superagent/lib/node/index.js:714:12)
    at emitNone (events.js:72:20)
    at Stream.emit (events.js:166:7)
    at Unzip.<anonymous> (/usr/lib/node_modules/cmd-jira/node_modules/superagent/lib/node/utils.js:120:12)
    at emitNone (events.js:72:20)

I changed line 75 of cmd-jira/lib/jira/decsribe.js to this in my local install:

            {'Subtasks': (res.body.fields.subtasks ? res.body.fields.subtasks.length : "")},

and that fixed it. If I have time later today I'll submit a PR.

I am also getting the "no issues" bug when running

jira ls

I saw that there is another recent similar issue that was closed 8 days ago here https://github.com/germanrcuriel/jira-cmd/issues/75 however the fix won't work for me since we are using a hosted jira so the link on how to get the token is not relevant.

Any ideas how I can get this tool working?

Could consider using a helper library like: https://www.npmjs.com/package/keytar or I'm sure there are others, but please consider not store user's passwords in a plain txt file...

Tried logging in and it asked for a password which I gave. Never asked for a 2fa token. Fails with "Error: got 401 response" on attempt at ls cmd.

in describe.js: 69

if reporter is undefined an exception is thrown,
when displayName is readed.

update the documentation to use api token instead of password.

Happens on the first run.

TypeError: program.prompt is not a function
    at Object.ask (/Users/furkantunali/.config/yarn/global/node_modules/cmd-jira/lib/auth.js:48:25)
    at Object.setConfig (/Users/furkantunali/.config/yarn/global/node_modules/cmd-jira/lib/auth.js:68:22)
    at Command.<anonymous> (/Users/furkantunali/.config/yarn/global/node_modules/cmd-jira/bin/jira.js:48:18)
    at Command.listener (/Users/furkantunali/.config/yarn/global/node_modules/commander/index.js:315:8)
    at Command.emit (events.js:182:13)
    at Command.parseArgs (/Users/furkantunali/.config/yarn/global/node_modules/commander/index.js:651:12)
    at Command.parse (/Users/furkantunali/.config/yarn/global/node_modules/commander/index.js:474:21)
    at /Users/furkantunali/.config/yarn/global/node_modules/cmd-jira/bin/jira.js:404:13
    at Object.execCb (/Users/furkantunali/.config/yarn/global/node_modules/requirejs/bin/r.js:1941:33)
    at Module.check (/Users/furkantunali/.config/yarn/global/node_modules/requirejs/bin/r.js:1116:51)```

Hi,

When calling jira done <issue>, I get no output whatsoever.

A query made with jira jql confirms that the task is still In Progress.

I can use jira stop and jira start correctly though

Using almost any command results in blocking behavior after the display of the results. Tests on ls averaged 60 seconds time out after having displayed results immediately.

Hi all!

When I execute "jira ls", I only see "In Progress" issues. Is possible to see "New" and "Closed" issues?

We need to document customisable column support added by @mederel in this PR https://github.com/germanrcuriel/jira-cmd/pull/79 so that new and existing users find it easy to use this functionality.

@mederel would you like to help in this?