RGBIQ

Get started with RGBIQ Release Views for Jira

Build a focused view of Jira releases and work items across spaces. Native Jira versions and work item release assignments remain the source of truth.

1. Install and start your trial

  1. Ask your Jira site administrator to open RGBIQ Release Views for Jira on Atlassian Marketplace.
  2. Review the price, trial terms, permissions, and customer terms, then install the app.
  3. Open Apps → RGBIQ Release Views for Jira in Jira.

A site administrator manages trials and subscriptions through Atlassian. If a trial or subscription is inactive, the app displays subscription instructions. Installing the app does not grant access to Jira work that you cannot otherwise see.

2. Create your first release view

  1. Select Create View and enter a clear name, such as “Customer Portal Launch.”
  2. Choose your scope: Jira spaces, specific releases, or JQL.
  3. Select the spaces or releases, or enter your JQL, then save.
  4. Use Select View to return to it later. New views are private until shared.

For JQL scopes, the report starts with work items assigned to a release. Child items may also appear even when they have no release assignment of their own.

A view can load up to 5,000 work items. Use a focused scope for large portfolios. Loading speed and refresh availability also depend on Jira permissions, API limits, and the fields selected.

3. Choose a report

ReportUse it to
ReleasesReview release dates, status, approvals, and work progress together. Filter table columns or select chart groups to focus the review.
Work ItemsInspect release work, expand epics, stories and sub-tasks, and show linked issues beside source work items.
Release TimelineExplore release dates over time. Zoom to widen or narrow the date columns and inspect releases or Release Set targets.
Needs AttentionFind overdue releases, missing release dates, and approval follow-ups.

Make the report yours

Understand release readiness

Review testing workflow status and linked test-case or change work items beside release work. Development summaries show commit and pull request information available from tools already connected to Jira. These summaries can be partial or cached. The app does not run tests, enforce approvals, or calculate a guaranteed readiness score.

4. Group versions into a Release Set

Open Release Sets within Releases and create a named group of related Jira versions. Add an optional launch target and inspect the members in the report and timeline.

A Release Set belongs to its saved view. It groups existing versions; it does not synchronize versions, change their dates, or move work items. A set's target date is separate from its member release dates.

5. Share the view

Use Edit View and the sharing controls to choose who may view or edit it. Owners and authorized editors manage shared settings; Jira administrators retain administrative controls. Every reader's own Jira permissions still apply, so two people can see different data in the same saved view.

Shared column selections and chart settings belong to the view. Column widths and collapsed columns remain specific to each user.

Refresh, troubleshoot, and get help

Contact RGBIQ Support & Feedback or email support@rgbiq.com. Include the report, action, error message, and approximate time. Never send passwords, API keys, or an unredacted export of confidential Jira work.

Read our privacy policy and security information.