Jira Configuration
Set up the Jira project, work types, and workflow states
Configuration Modes
The app supports two configuration modes for setting up the Jira project where release tickets are created and managed.
Default Mode (Auto-Setup)
Recommended for organizations that don't have an existing release management project. The app creates everything automatically:
- A new company-managed Jira project dedicated to release governance
- Custom work types (issue types) like Release Request, Emergency Release, Minor Release
- All 12 release workflow statuses (Draft, Planned, Approval Pending, Approved, etc.)
- Jira workflows mapped to each work type with proper transitions
- A hardened permission scheme that prevents manual edits to release tickets
Existing Project Mode
If you already have a Jira project for release tracking, you can integrate the app with it. Select the project and the app reads the existing workflow statuses and issue types.
- Select your existing Jira project from the dropdown
- Choose which work types to use for releases
- The app imports the existing workflow statuses for each work type
- You can customize transitions in the workflow editor
Setting Up a New Project
Open Settings and click Edit on Jira Configuration
Navigate to Settings from the Admin menu in the sidebar. Click the kebab menu on Jira Configuration and select Edit.
Choose Default (Auto-Setup) mode
Select the "Default" tab. Enter your desired Project Name (e.g., "Release Management") and Project Key (e.g., "RMC").
Define Work Types
Add the work types you need. Default suggestions: Release Request, Minor Release Request, Emergency Release Request. You can add up to 10.
Configure Workflow States (optional)
Expand the workflow editor to customize states and transitions. The default 12-state workflow covers most use cases. You can add custom states (up to 35 total).
Click New Setup
The app runs the setup process with a progress overlay showing each step. Once complete, your project is ready.
Default Workflow States
The app ships with 12 pre-configured lifecycle states:
| State | Category | Transitions To |
|---|---|---|
| Draft | To Do | Planned, Cancelled |
| Planned | To Do | Approval Pending, Cancelled |
| Approval Pending | In Progress | Approved, Rejected, Correction Requested, Cancelled |
| Approved | In Progress | Ready for Deployment, Cancelled |
| Rejected | In Progress | Cancelled |
| Correction Requested | In Progress | Draft, Cancelled |
| Ready for Deployment | In Progress | Deployment In Progress, Cancelled |
| Deployment In Progress | In Progress | Released, Deployed, Rolled Back |
| Deployed | In Progress | Released, Rolled Back |
| Released | Done | Rolled Back |
| Cancelled | Done | (terminal) |
| Rolled Back | Done | (terminal) |
Release Workflow States Section
After setup, the Settings page shows a read-only Release Workflow States section that displays the actual Jira statuses for your configured work types. Use the Refresh button to fetch the latest statuses from Jira if they don't appear immediately after setup.
Environments
Configure the deployment environments available when creating a release. Default environments: Production, Staging, QA, Development. You can add, remove, or rename them in the Environments section of Settings.
Team Membership Policy
The Team Membership Policy controls whether users can only create and manage releases for their own team, or for any team. When enabled:
- Users can only create releases for teams they belong to
- Users can only change the status of releases for their team
- Users can only edit releases belonging to their team
- Drafts are exempt — you can draft a release for any team