BevelpineApps

View My GitHub Profile

Initiative Timeline for Jira

Keep one list of initiatives with start and end dates, attach the Jira issues that belong to each one by issue key, and see the initiatives as lanes on a single timeline, each with a % done figure read from Jira.

Where to find it after installing

The app is a global page. Open Apps in Jira’s sidebar and choose Initiative Timeline. There is nothing to configure first.

Adding an initiative

At the bottom of the page, under New initiative:

  1. Enter a Name. It is required, and can be up to 120 characters.
  2. Optionally enter a Start date and an End date, written as YYYY-MM-DD (for example 2026-10-01).
  3. In Issue keys, enter the keys of the Jira issues that belong to this initiative, separated by commas, spaces or new lines. One initiative can link up to 100 keys.
  4. Click Add initiative.

Before you save, the form tells you what it made of the keys you entered, for example: “2 valid key(s) recognised. 1 duplicate(s) collapsed: KAN-3. 1 entry/entries are not issue keys and will be ignored: not-a-key.” Keys are upper-cased, so kan-3 and KAN-3 count as the same key.

After a save the page confirms it, for example “Added “Mobile app relaunch”. 4 issue key(s) linked.”, and the form empties.

The app never finds issues for you. It reads only the keys you enter.

What the form refuses

Nothing is saved, and the form says why, when:

Reading the page

The list sentence at the top says how many initiatives are shown, for example “Showing all 5 initiatives.”

The timeline has one lane per initiative. Each lane is positioned and sized by that initiative’s own dates, against the span of all the dated initiatives, which the caption states: “Timeline spans 2026-01-12 to 2026-12-18 (341 days), across 5 dated initiatives.” The bars show dates, not progress.

% done appears under each lane and on each initiative’s card, for example “0% done — 0 of 2 linked issue(s) are in a Done status category.” It is the share of the linked issues that Jira returned whose status is in Jira’s Done status category. It is a count of issues, not of story points or hours.

Keys that Jira did not return are named on the card and left out of the percentage, rather than counted as not done: “1 of 3: KAN-58. They may have been deleted, moved, or be invisible to you.” A key that does not exist is reported this way.

The issue status line under the timeline says how many of the linked keys Jira returned, for example “Issue status: 15 of 16 distinct linked key(s) returned by Jira, over 1 query and 1 page(s).”

Show issues on a card opens a table of that initiative’s issues with the columns Issue, Summary, Status and Done?.

Editing and deleting

Permissions

The app asks for two Atlassian permissions:

The app never creates, edits, transitions or deletes anything in Jira.

Limits and known issues

Your data

The app runs entirely on Atlassian Forge.

See the privacy policy for the full detail.

Support

bevelpine.support@proton.me · Mon–Fri, 09:00–17:00 BST · Support