Greenrun help

Everything you need to start testing in Jira. Can't find something? Get support.

On this page
  1. Getting started
  2. Writing test cases
  3. Running tests in a cycle
  4. Raising bugs
  5. Linking tests to stories
  6. Reports and the dashboard gadget
  7. Importing tests (CSV, Excel, Zephyr)
  8. Who can see and change what
  9. Pricing and licences
  10. Limits
  11. Support

1. Getting started

Install Greenrun from the Atlassian Marketplace (a Jira admin does this once). Then open Apps > Greenrun in Jira.

Pick a Jira project at the top. Tests, cycles and reports belong to that project. Greenrun has four tabs:

2. Writing test cases

On Test cases, click + New test case. Give it a title, and optionally an objective, a precondition, a priority and a status (Draft, Ready or Deprecated).

Write the test as either:

Ctrl+S saves. Each test gets a key like DEMO-T12.

Folders

Use + New in the Folders panel. Drag folders to reorganise them, and drag ticked test cases onto a folder to move them. A folder can only be deleted when it's empty.

Shared steps

Create a set on the Shared steps tab, then use Insert shared steps… in any test. Edit the set once and every test using it changes. A set can't be deleted while a test uses it.

Changing many tests at once

Tick tests in the list to move them, set their status or priority, or delete them together.

If two people edit the same test, the second save is refused with a message, so nobody's work is overwritten. Copy your changes, reopen the test and try again.

Drafting tests with AI

Greenrun can suggest tests from a Jira story. It is off until a Jira admin of the project turns it on in Settings > AI test writing.

3. Running tests in a cycle

On Test cycles, click + New cycle. Optionally group cycles into a test plan, for example every cycle for one release.

Open the cycle and add tests: pick them, or add a whole folder. Greenrun takes a copy of each test's steps at that moment, so editing a test later never changes results you've already recorded. If a test changes, its run shows "This test has been edited", with Use latest version.

Open a test in the cycle and, for each step, choose Passed, Failed, Blocked or Skipped. Type what actually happened, and paste screenshots with Ctrl+V or use Add file (up to 100 MB each, so screen recordings fit). The overall result is worked out from the steps: any failed step means Failed, any blocked step means Blocked, and all done means Passed. You can also set it by hand.

4. Raising bugs

On a failed step, click Raise bug. Greenrun creates a Jira bug as you, with the steps to reproduce, the expected and actual results and your screenshots, then links it to the run. You can also link an existing issue by its key. Linked bugs show their live Jira status.

5. Linking tests to stories

A test can cover any Jira issue except bugs and sub-tasks: stories, tasks, epics and so on. Link them in either place:

The Tests section shows each test's latest result, the bugs its runs raised, and an overall coverage label:

LabelMeaning
Not coveredNo tests are linked.
UntestedTests are linked, but none has passed yet.
Partly testedSome linked tests passed; others haven't been run.
PassingEvery linked test's latest result is Passed.
FailingAt least one linked test's latest result is Failed.
BlockedNone failed, but at least one is Blocked.

On a bug, the same section shows which test runs found it.

6. Reports and the dashboard gadget

The Reports tab has three reports. Each can cover all cycles, one plan or one cycle:

To see progress on a Jira dashboard, edit the dashboard, choose Add gadget, search for Test progress, then pick a project and a cycle or plan.

Exporting

The Export button on the test list, on a cycle and on each report downloads what you see as Excel or CSV, or opens your browser's print window, where Save as PDF makes a PDF. A test export uses the same columns as the importer, so you can import it again.

Automated test results (Jenkins, GitHub Actions, GitLab...)

Your build can send its JUnit XML or Cucumber JSON report to Greenrun after every run. A Jira admin of the project sets it up once in Settings > Automated test results:

REST API

Your own scripts and tools can read and create tests and read cycle results through Greenrun's REST API. It runs on Atlassian's app REST APIs, so your data still never leaves Atlassian's cloud. To set it up:

Every call acts as the person who signed in, with their own Jira permissions: reading needs Browse projects, changing needs Edit issues. Answers are JSON; errors come with a plain message (400 bad request, 401 no or expired token, 403 not allowed, 404 not found, 409 changed by someone else).

A person who closed their Atlassian account is shown by Greenrun as erased-account in fields such as createdBy and executedBy, because Atlassian's privacy rules require Greenrun to remove closed accounts' IDs. Treat that value as "a closed account"; don't look it up in Jira.

Searching from Jira (JQL)

Greenrun adds four functions to Jira's own search, so you can use test results in filters, boards and dashboards:

Jira keeps each answer for a while, and Greenrun updates it about a minute after a change. A function can return up to 1,000 issues; above that, add a project, a cycle or a plan. Jira still only shows issues you're allowed to see.

7. Importing tests (CSV, Excel, Zephyr)

On Test cases, click Import… and choose a .csv or .xlsx file. The file is read in your browser.

Moving from Zephyr

Zephyr Scale: open Test cases, select the tests, then More > Export to Excel.
Zephyr Essential (Squad): use Export test cases > Excel (all fields).
Import that file into Greenrun. Greenrun recognises Zephyr's column names, and your Zephyr data stays exactly where it is.

Please note: the Zephyr importer was built from Zephyr's published column names and tested on look-alike files, not yet on a real customer's export. Before importing everything, try a small export first and check the result. If anything doesn't come across properly, email us the file's column headings and we'll fix it quickly.

Up to 5,000 tests and 20 MB per file. Test results history, attachments and custom fields aren't imported yet.

8. Who can see and change what

Greenrun follows your Jira project permissions. There's nothing extra to set up.

A change to someone's Jira permissions takes up to a minute to apply in Greenrun.

9. Pricing and licences

Free for Jira sites with up to 10 users. Above that, $2.15 per user per month, billed by Atlassian. As with all Jira apps, the price follows your Jira site's user count.

If a licence lapses, Greenrun becomes read-only: you can still see and report on everything, but changes are switched off until a Jira admin renews it in Apps > Manage apps. Your data isn't deleted.

10. Limits

WhatLimit
Steps in one test or shared set200
Tests changed at once (bulk)500
Tests added to a cycle at once500
Files per step / size of a file10 files / 100 MB each
Import file5,000 tests, 20 MB
Issues in one coverage report500

11. Support

We reply within 1 working day (UK hours, Monday to Friday). The support page lists what to include and has the email address.