Inspiration

Organizations and independent teams frequently manage departmental structures, budgets, and milestone roadmaps in dedicated desktop software such as PFine Organisation Project Management System (v0.1.0), while day-to-day execution takes place inside Jira Cloud. That split leaves context fragmented: leadership tracks high-level milestones without live Jira issue keys, and Jira users execute individual tickets without weighted departmental visibility. We built pfine-pm-bridge on Atlassian Forge so organizational milestone velocity and Jira execution stay connected in one place.

What it does

PFine Organisation Project Management System (v0.1.0) pairs a standalone Windows desktop application (pfine-organisation-project-management-setup-win10-win11-0.1.0.exe, built on a lightweight PHP/MySQL architecture) with pfine-pm-bridge, a custom Atlassian Forge Jira Admin page (jira-admin-page-custom-ui) deployed to production with read:jira-work and write:jira-work scopes.

Inside Jira Cloud, pfine-pm-bridge enables teams to:

  • Organize Departments & Weighted Milestones: Create departments with assigned leads, filter milestones by department, and assign priority weights (1, 3, or 5) alongside target due dates.
  • Measure Weighted Completion Velocity: Automatically calculates real-time weighted progress across all organizational milestones using each milestone's priority weight \(w_i\), completed deliverables \(d_i\), and total deliverables \(t_i\):

$$V_p = \frac{\sum_{i=1}^{n} w_i \cdot \left(\frac{d_i}{t_i}\right)}{\sum_{i=1}^{n} w_i} \times 100\%$$

  • Push Deliverables Directly to Jira: Discovers active Jira projects via @forge/bridge (requestJira against /rest/api/3/project/search) and creates linked Jira tasks (/rest/api/3/issue) with one click, writing the created Jira issue key (PROJ-123) right back onto the deliverable row.
  • Export Portable Desktop Snapshots: Downloads a structured pfine-organisation-pm-snapshot.json file containing departments, milestones, task states, and linked Jira keys for portability with the PFine v0.1.0 desktop workflow.

How we built it

  • Atlassian Forge & Custom UI (pfine-pm-bridge): Scaffolded using the Forge CLI (jira-admin-page-custom-ui) with React, @forge/bridge (view.getContext() and requestJira()), and clean, accessible CSS (App.css) aligned with Jira Cloud's visual hierarchy.
  • Scoped Jira REST Integration & Production Release: Declared read:jira-work and write:jira-work scopes in manifest.yml, deployed to the Forge Production environment (forge deploy -e production --approve MAJOR_VERSION_RULE), verified live on Jira Cloud (patadvent.atlassian.net), and enabled Sharing distribution targeting Jira (&product=jira).
  • Desktop Companion (v0.1.0): Packaged as a Windows 10/11 installer (pfine-organisation-project-management-setup-win10-win11-0.1.0.exe) built on a lean PHP/MySQL architecture designed for low overhead and fast local operation. Below is an example of the portable JSON snapshot generated between the Forge app and desktop workflow:
{
  "source": "PFine Organisation PM v0.1.0",
  "departments": [
    { "id": "dept-1", "name": "Engineering & Core Architecture", "lead": "Patrick Wilson" }
  ],
  "milestones": [
    {
      "id": "ms-1",
      "title": "v0.1.0 Core Desktop & Jira Sync Bridge",
      "weight": 5,
      "tasks": [
        { "id": "t-3", "title": "Sync department milestones with Jira Cloud", "done": false, "jiraKey": "SCRUM-12" }
      ]
    }
  ]
}

Challenges we ran into

Forge Scopes & Production Major Version Upgrades: Adding read:jira-work and write:jira-work required explicit major version approval (MAJOR_VERSION_RULE) and clean static asset bundling (npm run build inside static/hello-world) before production deployment.

Product-Specific Sharing Link Targeting: Configured the Atlassian Developer Console Distribution settings so the generated Sharing installation URL explicitly targets Jira (&product=jira) for seamless one-click testing by judges.

Accomplishments that we're proud of

Delivering a zero-bloat, self-contained Atlassian Forge production app that turns abstract departmental milestones into real, trackable Jira issues in a single click.

Bridging a standalone Windows desktop project management tool (PFine Organisation Project Management System) with Jira Cloud without external API bloat.

What's next for PFine Organisation Project Management System (pfine-pm-bridge)

Live Bi-Directional Cloud Sync: Connect real-time API synchronization between pfine360.com, the PFine desktop database, and Jira Cloud so issue transitions update milestone progress automatically.

Multi-Project & Executive Reporting: Add cross-project milestone rollups, sprint velocity comparisons, and scheduled department health digests inside Jira Cloud.
Share this project:

Updates

Submission history