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 🙏

© 2025 – Pkg Stats / Ryan Hefner

jira-pull-tickets

v3.0.0

Published

Pull tickets from jira

Readme

CLI app to display jira issues

Note: Mac OS only

screen shot

1. Description:

Pull issues and display from jira using terminal.

2. Installation:

Need global installation to work correctly.

$ npm install -g jira-pull-tickets

3. Usage:

After installation run init:

$ jira init

You will be asked to prompt

  • server - ex. https://jira.servername.com

  • project name - ex. CCLC, CMHM or any other project name - it will be used as default (current) project to display issues (tickets)

  • [username] - jira's username, if left blank process.env.USER will be used

  • password - user's password for jira's server.

Password will be safely stored in Keychain under the service jiraCLIuser.

After init jiraCLI creates jiraCLI.json file at /Users/username/Library/JiraCLI that contains basic info required to form requests to Jira's server.

4. Commands

4.1 Get

Basic command that displays all issues with status different from "Complete" or "Done" for project. First it will search current directory for jiraCLI.json to get project information, else it will use default project data stored at /Users/username/Library/JiraCLI/jiraCLI.json (set during initialization)

$ jira get [project name] [flag]    

| Command | Description | |---|---| | jira get | Display open tickets for default project | | jira get -u | Open tickets for default project assigned to current user | | jira get -a | Display all tickets for default project | | jira get CCLC | Display open tickets for specified project, ex. CCLC |

Flags can be combined, ex. display all tickets for CCLC project assigned to current user:

$ jira get CCLC -ua    

4.2 Set

When in current project directory run

$ jira set

You'll be asked to promt new project name. It will create jiraCLI.json file in that directory, storing the project name. Since now whenever runnning $ jira get in this directory it will use project name from jiraCLI.json instead of default one.

4.3 Project

Used to change default project.

$ jira project

Another option to change default project(s) is to update it manually at /Users/username/Library/JiraCLI/jiraCLI.json.

To add multiple projects input its keys with space as separator

$ jira project
$ project: CNHM CDTR CMNM

4.4 test

Test notifications.

4.5 --help

Show available commands.

4.6 track

Used to track default project(s).

$ jira track

Outputs 2 tables in terminal: issues by project/status and issues by developers/project. Recursively send request every 30 seconds untill cancelled.

4.6 post

Used to sent object with data on current project(s) (created via track module) to http://localhost:7700/requests via post request.

$ jira post

Recursively send request every 5 seconds untill cancelled.