Skip to Content

Jitterbit Jira Tracker App

Overview

Jitterbit provides the Jira Tracker app through Jitterbit Marketplace. Built with Jitterbit App Builder, it is a product lifecycle tracking app for cross-functional teams. Product Management captures and scopes incoming tickets, and UX, Engineering, and Technical Documentation each track their part of the work as it moves through delivery. Tabbed dashboards give each discipline a view of ticket status by product and quarter.

You download the app as an App Builder release package (an .LP file) from Marketplace and install it into your own App Builder instance, where you can configure and extend it to fit your process.

This page describes how the app works, its core features and data model, and covers the prerequisites, how to download and install it, how to configure it for your environment, how access is controlled, and common troubleshooting steps.

How it works

Product Management enters and scopes a ticket, forming a Plan of Intent (POI). The other disciplines then track their work against that ticket, and status changes roll up into the dashboards:

flowchart TD A["Product Management
creates a ticket"] --> B["Scope: product, customer,
ACV, pillar, and quarter"] B --> C["UX tracks design
requirements and readiness"] B --> D["Engineering maps to sprints
and the Plan of Record"] B --> E["Documentation tracks
content and release notes"] C --> F["Status updates
by discipline"] D --> F E --> F F --> G["Tabbed dashboards:
ticket counts by status,
filtered by quarter"]

Here, a Plan of Intent (POI) is the initial scoped set of work, and the Plan of Record (POR) is what Engineering commits to deliver. Annual Contract Value (ACV) is captured on the ticket to track fiscal impact.

Core features

When you install and configure Jira Tracker, it provides the following capabilities:

  • Ticket intake and scoping: Product Management captures tickets with a product, customer, Annual Contract Value (ACV), pillar, and quarter.

  • Cross-functional tracking: UX, Engineering, and Technical Documentation each track their own status on a ticket. Engineering maps tickets to sprints and to the Plan of Record.

  • Tabbed analytics dashboards: Four tabs (Requirement, UX Design, Documentation, and Engineering) chart ticket counts by workflow status for each product. Charts respond to the active quarter filter and support drill-down to the underlying ticket list.

  • Workspace personalization: Each user's profile stores workspace defaults, such as a preferred product and quarter, so new tickets and views are pre-populated accordingly.

  • Comments: Each ticket keeps a chronological comment log for an auditable history.

  • Grid tools: Ticket views include global search, column filtering, and CSV export.

Data model

Jira Tracker stores all of its data in its own tables. Each table has a data usage type, set by its Install Option, that controls how its data is treated when the app is installed in a new environment: Developer and Shared data (such as lookups) are seeded on install, and User data (such as tickets) is left for each environment to populate.

Table Usage type Purpose
Ticket User Core work items; links each ticket to its product, release, team members, and per-discipline statuses.
Comment User Chronological comments on a ticket.
User User Internal user profiles, department mapping, and workspace defaults.
Session User Per-user runtime state and active filters.
Status Shared Workflow states (for example, In Progress, Complete), with color and sort settings.
StatusType Shared Groups statuses so each discipline manages its own set of states.
Outlook Shared Health indicators (for example, On Track, At Risk) with color coding.
Sprint Shared Time-boxed engineering iterations that tickets are mapped to.
Product Shared Master list of products or modules used to segment tickets and reporting.
Pillar Shared Strategic themes that work aligns to.
Quarter Shared Fiscal or calendar quarters used for roadmap planning and filtering.
Release Shared Scheduled release versions and milestones.
Department Shared Organizational units mapped to users.
Parameter Shared Global settings and defaults.

The Ticket table links to User through several role-specific keys (ProductManagerID, UXDesignerID, and EngineerID). Deleting a Ticket cascades to its Comment records, and deleting a StatusType cascades to its Status records.

Business logic

Status values and workflow paths are driven by the lookup tables (Status, StatusType, Outlook) and by configuration rather than by hardcoded text, so you can adjust states without changing the app's logic. Validations are applied at the table level so that forms and grids inherit them. When a user creates a ticket, the form pre-populates values such as the product and quarter from that user's workspace defaults.

Prerequisites

To use Jira Tracker, you need the following:

  • A Jitterbit Harmony license with access to App Builder. This enables the Marketplace download; if your organization is not licensed for App Builder, the Download app action is replaced by a Get app request action (see Download and install).

  • An App Builder instance running App Builder 4.61, the version the current package is built for. Each package installs only on its exact App Builder version; if your instance is on a different version, contact Jitterbit support to request a matching package.

  • A PostgreSQL database for your App Builder instance.

The app is self-contained and does not require a connection to any external system.

Download and install

Download the app from Marketplace

  1. Log in to the Harmony portal at https://login.jitterbit.com and open Marketplace.

  2. Locate the app named Jira Tracker. You can use the search bar or, in the Filters pane under Type, select App to show only apps.

  3. Click the app card to open the Details panel. Review the app's Requirements (the App Builder version and database it needs).

  4. Click the app's Go to documentation link to open this documentation in a separate tab, and keep it open for reference.

  5. Do one of the following, depending on whether your organization is licensed for App Builder:

    • Download app: If your organization is licensed for App Builder, click Download app, on either the app card or the Details panel. Your browser saves the .LP file to its download location, and an App Builder file downloaded successfully notification confirms the download.

    • Get app: If your organization is not licensed for App Builder, the action is labeled Get app. The Details panel shows a message that an App Builder license is required, with a Submit button. Click Submit to send a request for a representative to contact you about App Builder; a Message successfully sent notification confirms it.

Install the app in App Builder

Install the downloaded .LP file into your App Builder instance:

  1. Log in to App Builder and go to the IDE.

  2. Under Deploy, click Install Release.

  3. Click + Package, then Browse and select the .LP file you downloaded.

  4. Click Save. The Release panel displays the package information, then close the Package dialog.

  5. Confirm the details are correct, then click Install.

To preview a package's contents before you install it, click the Manifest button.

Modifying the app in a development environment

The app's data source installs sealed. If you deploy the app to a development environment and intend to modify it, unseal the data source so you can edit the app's objects. Leave it sealed in QA and production to preserve equivalence across environments. See Seal or unseal a data source.

Configuration and setup

After you install the app into a new environment, complete the following steps to make it ready to use:

  1. Set up the user-group realm. The release does not ship the realm that provisions its user groups, so create it before you assign users. In the IDE, go to User Management > Realms and click + Realm. In the Applications panel, click Select for Jira Tracker; in the Groups panel, click Select for Jira Tracker Administrator and Jira Tracker User. See Realms for the full procedure, including naming the realm and delegating a security provider.

  2. Add users and set their workspace defaults. On the Users page, add each user and set their workspace defaults (such as a preferred product and quarter) so new tickets and views are pre-populated. To grant access, assign the user to a group on the User Group tab of the User page, either Jira Tracker Administrator or Jira Tracker User. See Security and access.

  3. Populate the lookup tables. The app ships with sample lookup data. Replace it with your organization's values for Product, Pillar, Quarter, Release, Sprint, Department, and Status.

Security and access

Jira Tracker uses App Builder role-based security with two access groups, Jira Tracker Administrator and Jira Tracker User. You assign users to these groups on the User Group tab of the User page, which provisions membership through an App Builder realm that you create during configuration. Access to each area is as follows:

Area Jira Tracker Administrator Jira Tracker User
Ticket creation and editing Full access Create and update (no delete)
Workflow dashboards Full access View, and change filters
User profile and filter settings Full access Full access to their own record
Lookup and administrative tables Full access No access (menus hidden)

Dashboards show all tickets; users narrow what they see with the workspace and dashboard filters rather than through per-row restrictions. Ticket history is preserved through the Comment log.

Troubleshooting

Dashboard charts do not show the expected tickets

  • Symptom: A dashboard tab shows fewer tickets than expected, or none.

  • Possible cause: The dashboards respond to the active quarter and workspace filters. A filter may be excluding the tickets you expect.

  • Resolution: Adjust or clear the quarter and dashboard filters.

A new ticket is pre-filled with the wrong product or quarter

  • Symptom: When a user creates a ticket, the product or quarter is pre-populated with a value they did not choose.

  • Possible cause: New tickets inherit the workspace defaults set in the user's profile.

  • Resolution: Update the workspace defaults in the user's profile, or change the values directly on the ticket.

For further help, review your App Builder logs and contact Jitterbit support.