Jira Performance Tests

Jira Performance Tests is an automated performance benchmarking tool for Jira Server and Jira Data Center.

  • Development
  • Tools & Utilities
Jira Performance Tests is an automated performance benchmarking tool for Jira Server and Jira Data Center. It provisions a test Jira instance, drives realistic browser-based user activity, and produces reports so you can measure how well your setup handles heavy workloads before slowness reaches your team.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

25/100 Low

Maintained
0last commit 2279 days ago
Popular
2517 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
108 GB minimum RAM
Security check
85no serious findings, tests
GitHub stars
17
Open issues
2
Last commit
2020-08-25
Activity
stale

Checked 3 days ago - source: GitHub (atlassian/jira-performance-tests)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create a virtual Python environment Create a virtual environment (an isolated Python setup) and activate it before installing. This keeps the app's packages from mixing with system Python and causing broken or conflicting installs. source
  • Save Jira login details in config.ini Put your Jira URL and optional credentials in the settings file called config.ini. The tool reads that file to find your server, so missing or wrong details mean it can't connect; keep the file private because it may contain login information. source
  • Add [cli] for command-line tools Install with 'jira[cli]' if you want jirashell or other command-line extras. Omitting [cli] installs the library only, so you may be missing tools you need for testing. source
  • Active development location The GitHub repository is mid-migration; active development has moved to Bitbucket (bitbucket.org/atlassian/jira-performance-tests). source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can JPT handle provisioning, test execution, and reporting as one workflow?

Yes, it can manage provisioning a new Jira instance, running performance tests, and generating a report.

Does JPT support Jira Server and Data Center performance use cases?

Yes, it is an API-driven framework for performance testing Jira Server and Data Center use cases.

Is JPT generally available or still beta?

The announcement describes JPT as beta tooling open for early access.

What Python setup step helps avoid broken or conflicting installs?

Create and activate a virtual Python environment before installing so its packages stay isolated from system Python.

Where does the tool store Jira connection details?

It puts the Jira URL and optional credentials in config.ini, which should be kept private because it may contain login information.

Answers sourced from community.atlassian.com, community.developer.atlassian.com, github.com, jira.readthedocs.io, jira.readthedocs.io

Community

Collected 48 days ago - public community threads