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

cli-jira

v3.0.2

Published

Jira cli tool with some features I like to lunch from a terminal

Downloads

4

Readme

cli-jira

The aim of this tool is performing some actions which are common to my daily work with Jira in a smother way, it's not my purpose to handle Jira form this tool neither to have actions I don't use in my developing workflow -there're better tools for that, for example ankitpokhrel/jira-cli-

I've created this tool mostly to speed up the Jira's workflow when I have the Scrum master rol, the scrum master needs to assignee created actions to developer or split tickets into Developing and Validation subtasks so the team can estimate both actions; I've check I'm more productive working from the terminal rather than performing those actions through Jira.

Even though, Jira is a powerful tool which I still learning to manage and 100% of the actions you can perform from this tool can be done through Jira.

⚠️ This tool saves your Jira password in plain text also when the configuration is printed, the password is visible

Commitizen friendly

cli-jira
Usage:
  cli-jira config set credentials <user> <password>
  cli-jira config set url <address>
  cli-jira config print
  cli-jira issue set sprint <board> <issue>
  cli-jira issue set estimation --original=<original_estimation> [--remaining=<remaining_estimation>] <issue>
  cli-jira issue set assignee <developer> <issue>
  cli-jira issue set ready <project> [<component>] <issue>
  cli-jira issue add subtask <project> <subtask> [<component>] <issue>
  cli-jira -h | --help
  cli-jira -v | --version

Install

To install the tool execute the next command

npm i -g cli-jira

And check the version of the tool

cli-jira -v

Actions

In order to list all the actions you can execute with this tool, execute the next command in your terminal

cli-jira

And a list with all the actions shows up

Parameters

  • issue: It's the issue's identifier
  • developer: User's Jira name
  • estimation: Issue's estimation, it can be added in any Jira supported format
  • user: Your Jira user name -you can see it at Jira's profile-
  • password: Your password Jira access
  • developer: Developer's name (it's the email without the email prefix)
  • --original: Jira ticket original estimation
  • --remaining: Jira ticket remaining estimation
  • issue: Jira ticket id
  • project: Jira project id
  • substask: Jira summary text
  • component: Jira type id (story, sub-task, etc) by default is sub-task
  • board: Jira board ID (it's rapidView url param)