npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jira-node-cli

v1.2.1

Published

JIRA command line interface

Downloads

22

Readme

JIRA CLI   Build Status   Tweet

Usage: jira [options] [command]

Options:

  -h, --help                output usage information

Commands:

  create-issue              Create new issue
  issue-link [issueName]    Copy issue link to clipboard
  issue-status [issueName]  Show issue status
  issue [issueName]         Show issue details
  jql [jql]                 Show issues using JQL
  all                       Alias => jira jql ''
  my-issues                 Alias => jira jql 'assignee in (currentUser()) ORDER BY status ASC'
  my-not-released           Alias => jira jql 'status not in (Released) AND assignee in (currentUser()) ORDER BY status ASC'
  my-stage                  Alias => jira jql 'status in ('Deployed to Stage') AND assignee in (currentUser()) ORDER BY status ASC'
  sprint                    Alias => jira jql 'sprint in openSprints() ORDER BY status ASC'
  stage                     Alias => jira jql 'status in ('Deployed to Stage') ORDER BY status ASC'

jira-all

jira-issue

Tips

Commands like jira all, jira my-not-released are implemented as aliases. I'm planning to allow user to create his own aliases but currently there is a few hardcoded, so you may meet error like:

JIRA respond with '400 Bad Request' status.
ERROR MESSAGE:
The value 'Released' does not exist for the field 'status'.
Please try again later
                                                                                                                                                       	

As a workaround please use plain jira jql queries, for example:

jira jql 'project=ABC AND status in (New)'
jira jql 'assignee in (currentUser()) ORDER BY status ASC' 
jira jql 'project=XYZ AND assignee in (currentUser()) ORDER BY status ASC'                                                                                                                                                       	.

Install

npm install -g jira-node-cli

Usage

Type:

jira

and you will be asked about credentials to your JIRA account. Credentials will be saved in ~/.jirarc file.