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

@oselvar/connector-jira

v0.1.0

Published

Oselvar Connector for JIRA

Downloads

1

Readme

Oselvar JIRA Connector

Library and command line tool to generate Oselvar CSV from a JIRA project.

Get a JIRA token

Generate a new API Token and label it oselvar. Store this safely and assign it to a JIRA_TOKEN environment variable.

Usage

Start by running the connector once without specifying stages:

oselvar-jira --email $JIRA_EMAIL --token $JIRA_TOKEN --url $JIRA_URL --key $JIRA_KEY

The first line of the generated CSV will look something like this:

id,name,13257-Development,13269-Next,13258-Deployed,13261-Development Done
  • Open a text editor and paste the line in there
  • Remove the id and name columns
  • Reorder the values so they reflect the stages on your board (You may want to remove some stages that are not part of your workflow).

Now you'll have something like this:

13269-Next,13257-Development,13261-Development Done,13258-Deployed

The next thing to do is to map these values to something more readable, by adding a : followed by the name you want in the CSV.

13269-Next:Next,13257-Development:Development,13261-Development Done:Development Done,13258-Deployed:Deployed

Now you can run the connector again:

oselvar-jira --email $JIRA_EMAIL --token $JIRA_TOKEN --url $JIRA_URL --key $JIRA_KEY \
  --stages "13269-Next:Next,13257-Development:Development,13261-Development Done:Development Done,13258-Deployed:Deployed"

You should now get a CSV with the following headers

id,name,Next,Development,Development Done,Deployed

That's it!