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

@pietert/jira-cli

v1.0.0

Published

CLI tool that interacts with the JIRA REST API

Downloads

11

Readme

Jira CLI

Setup

Install (Unix & Windows compatible)

npm i -g @pietert/jira-api

Configure

Now run

jira setup

You will be asked for:

  • endpoint: this should be in the form of https://company_name.atlassian.net
  • username: your email that you use to login to Jira
  • apiToken: you can create your token here.
  • boardId: this is the id of the sprint board. You can find it by going to the backlog or sprint board. The integer after /boards/ is the boardId.

Commands

Worklogs (i.e. timetracking)

To start the timer. If no ISSUE_KEYis provided and you're currently in a git branch, the name of that branch will be used as issue key. Otherwise an error will be thrown. This is what issue keys look like

jira start [ISSUE_KEY]

To stop the timer and save the worklog. If you don't provide the issueKey, your current git branch name will be used. (very handy if git branches are linked to Jira issues). Otherwise, an error will be thrown.

jira stop [COMMENT] [ISSUE_KEY]

Logging recurring activities.

jira log ACTIVITY

You can define recurring activities in the cli-config.js file. For example:

export default {
  standup: {
    issueKey: "PROJECTNAME-XXXX",
    comment: "Standup",
    timeSpent: 900,
    startTime: "08:30",
  },
};

Note that timeSpent must be in seconds. startTime can be in any time format. (e.g. 12, 3 pm, 15:49, 11:49:34 a.m., etc) After defining standup as a recurring activity, you can run jira log standup. Look for more examples in cli-config.js. TIP: use cron-jobs to automate the logging of recurring events.

List issues

To get a table displaying the current issues in the sprint, run

jira issue|is list|ls [STATUS_CATEGORY]

Lookup issue information

To view information about a specific Jira issue

jira info|i [ISSUE_KEY]

Adding comments

jira comment|cm add ISSUE_KEY COMMENT [MENTION]

You can also include a mention (first name of person you want to mention). This will add a mention block at the front of your comment in Jira. Note: the COMMENT argument must be a quoted string.

Help

Whenever stuck or when you trying to find info or aliases for a command, run

jira [COMMAND ...] - h