Skip to content
Back to the index

tempo-plan-fact

PyPIInfrastructure

No liveness check has reached it yet; it is registered on GitHub and PyPI and has been in the index since 9 Oct 2026. How this is checked

tempo-plan-fact is an open-source command-line tool that compares cumulative Tempo worklogs with a monthly hours target. It is intended for Jira and Tempo users who need to review planned versus actual work time.

Inferred · not functionally tested

Open SourceMITCLISelf-hosted
Visit PyPI
1star
5features
2026since

Overview

5 features

Purpose: Comparing Jira Tempo worklogs against monthly planned hours to identify time-tracking variances.

Inferred · not functionally tested

Audience: Jira and Tempo users tracking monthly work hours

Inferred · not functionally tested

Functions: analytics

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

tempo-plan-fact is a CLI tools & terminal project. Inferred · not functionally tested: It focuses on comparing Jira Tempo worklogs against monthly planned hours to identify time-tracking variances. Inferred · not functionally tested: tempo-plan-fact is an open-source project aimed at jira and Tempo users tracking monthly work hours. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the command line, and it can be self-hosted.

It is developed by obrizan, and it first shipped in 2026. Development happens publicly on GitHub with 3 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are worklog comparison, monthly targets, and cumulative totals.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Worklog comparison
  • Monthly targets
  • Cumulative totals
  • Tempo integration
  • CLI reporting

Topics: Inferred · not functionally tested

Tags
jira-tempoworklog-analysistimesheetsmonthly-targets

JSON profile · Text profile · Access guide

Built with & integrations

Written with
Unspecified agent
Runs on
CLISelf-hosted
Written with — evidence
Unspecified agent
AGENTS.md

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceFree tierGitHub · ★ 1Active maintenance

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed9 Oct · 10:21 UTC
    tempo-plan-fact seen via PyPI Bulk Enumerator
    Source: PyPI Bulk Enumerator · Open

Frequently asked questions about tempo-plan-fact

What is tempo-plan-fact?
Inferred · not functionally tested: Tempo-plan-fact focuses on comparing Jira Tempo worklogs against monthly planned hours to identify time-tracking variances. It is catalogued under CLI tools & terminal on PulseGate.
Who is tempo-plan-fact for?
Inferred · not functionally tested: tempo-plan-fact is an open-source project built for jira and Tempo users tracking monthly work hours.
Does tempo-plan-fact have a free plan?
Basis unknown · not verified: Yes — tempo-plan-fact is open source under the MIT license and free to use.
What platforms does tempo-plan-fact run on?
Basis unknown · not verified: tempo-plan-fact runs on the command line. It can also be self-hosted.
Is tempo-plan-fact still maintained?
The GitHub repository shows 3 commits in the last 90 days.
What are alternatives to tempo-plan-fact?
Similar projects tracked by PulseGate include edupage-cli, sessioncost, and pyfx-terminal.edupage-clisessioncostpyfx-terminal
Who makes tempo-plan-fact?
tempo-plan-fact is developed by obrizan.
How long has tempo-plan-fact been around?
tempo-plan-fact first shipped in 2026.

Also in CLI tools & terminal

Same category — not a similarity match