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 🙏

© 2026 – Pkg Stats / Ryan Hefner

jira-add-worklog

v0.0.4

Published

a utility tool for jira users to log work hour against an issue

Readme

jira-add-worklog

jira-add-worklog is a utility tool for jira users to log work hour against an issue. The best use case of this tool can be hooked it into git pre-commit / post-commit. So that, developer can log work against every commit without leaving the terminal.

Installation

It's advised to install the jira-add-worklog module as a devDependencies in your package.json as you only need this for development purposes. To install the module simply run:
npm install --save-dev jira-add-worklog

Example

$ logwork -C $HOME/workspace/logwork.config.js
issueIdOrKey: Issue-101
timeSpent:[1h 30m] 2h
comment: 'description for the work done'
startDate:[2018-07-19] 2018-07-19 // default is current date
startTime:[20:24:11.000] 20:24:11.000 // default is current time

Configuration (option -C)

It takes the a file path for configuration (.js). For example:

module.exports = {
  'username': <user name to jira>,
  'apiToken': <api token [create your API token for the basic authentication]>,
  'email': <email id>,
  'domain': <domain name for jira>,
  'timeZone': <time zone offset>
  /**
    'timeSpent': <value>,
    'issueIdOrKey': <value>,
    'comment': <value>,
    'startDate': <value>,
    'startTime': <value>
  */
};

Those options which do not ocassionally get changed can be stored in the configuration file.

help:

$ logwork -h

  Usage: logwork [options]

  Options:

    -v, --version                    output the version number
    -C, --config           [string]  Path to the config file. [default: logwork.config.js] (default: ./logwork.config.js)
    -u, --username         [string]  Username of jira account.
    -a, --api-token        [string]  API token for basic authentication. Generate an API token in jira.
    -e, --email            [string]  Registered email address
    -t, --time-spent       [string]  Time for log work hour. For example: ['30m', '1h', '1h 30m', '1d 1h 30m']
    -i, --issue-id-or-key  [string]  Issue id or key for the issue where work hour will be logged
    -d, --domain           [string]  Domain name
    -c, --comment          [string]  Description of the work
    -D, --start-date       [string]  Start date of current work [optional]. For example: 2018-12-31
    -T, --start-time       [string]  Start time of current work [optional]. For example: 22:10:00
    -z, --time-zone        [string]  current time zone [optional]. For example: +0530
    -h, --help                       output usage information