Installing the Jira Bridge on macOS
Requirements to set up the Flow Production Tracking Jira Bridge
- A Flow Production Tracking Project
- A Jira Project
- Admin access to Flow Production Tracking and Jira
- A Flow Production Tracking Jira Bridge server location
- A Flow Production Tracking Event Daemon server location
- An understanding of Flow Production Tracking entities and Jira issues
- An understanding of the hierarchies for each project
- A hierarchy mapping between the Flow Production Tracking and Jira projects
- A status mapping between the Flow Production Tracking and Jira projects
This installation guide will walk through all the necessary requirements to set up the Flow Production Tracking Jira Bridge.
Notes about mapping
Jira field ID codes
A concise mapping plan between the specific Flow Production Tracking project entities' field code IDs and the specific Jira project issues' field code IDs will be needed to get the desired bridge functionality working.
It's important to note that even the seemingly built-in Jira issue types (Epic, Story, etc.) can have custom field codes in places and not a standardized named field code. Your assumption should be that every field is a custom field, and you should verify what the field code id is for mapping. Use a browser's "Inspect" option (right-click on the site page field you want to check, select "Inspect" at bottom) to access the Developer Panel and locate each specific field's code for use in creating the appropriate mapping needed in handlers.
An example of this would be: The "Description" field ID code for a Jira Epic issue could be "description", but the Epic Name field ID code for a Jira Epic issue could be "customfield_#####" instead of something generic like "name" or "epicname".
It's important to verify the internal field ID codes for every field on Flow Production Tracking and Jira that you want to map across the platforms for Flow Production Tracking entities and Jira issues with the Flow Production Tracking Jira Bridge. Also note field codes may be unique per project, and per issue/entity. Always verify them.
Check custom field IDs in Jira
For more information about finding custom field IDs, please see Atlassian's documentation at https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html.
System requirements
The Flow Production Tracking Jira Bridge installation guide has been tested on macOS and Windows. Below we outline the minimum requirements to run the bridge, along with the hardware and software used in testing.
Minimum requirements
- Python 3.9 or greater
- A Flow Production Tracking site
- A Jira site
Recommendations for macOS installation
The following hardware and software is used in images throughout the installation guide, where installation for macOS is mentioned.
- Apple M1 MacBook Pro
- macOS Monterey Version 12.6
- Python 3.11
- Homebrew (package installer for Mac)
- ngrok (to access locally hosted server)
- Python IDLE (Python script editor)
- pip (package installer for Python)