Time color for JiraOne Epic, one project
For example a small game or a campaign, finished in a few weeks to a few months.
Read your Jira Timeline at a glance
Colors Planning Tasks, Milestones and Epics the way your team sets them up, marks weekends and public holidays on the timeline, and shows how many working days a bar takes when you hover over it.
Coming soon to the Chrome Web Store
View source
Works with project Timelines on Jira Cloud (*.atlassian.net).
See it in action
34 seconds, no sound: turning the extension on, then hovering over bars and Milestones on a demo project.
Made for teams like this
Several short projects run at the same time, and each one is handed from role to role: art, engineering, QA, marketing.
Many projects at once
All projects sit on one Timeline, so you can see how their schedules line up.
Roles work in sequence
Each role picks up its part on schedule, and Milestones mark every delivery.
For example: small game studios, live-ops events, marketing campaigns, video production.
Recommended setup: one Timeline for the schedule, one board per role
The extension is designed for teams that keep scheduling and execution apart. The main board holds the schedule. Each role's board shows only its own part of that schedule, and the team creates the actual work items from there.
Issue types
| Type | Used for |
|---|---|
| Epic | One short project, such as a small game or a campaign |
| Planning Task | A role's work over a period; set its start and due dates and its role |
| Milestone | A key delivery date, linked to the work that must be done by then |
| Task, Story, Bug… | The actual hands-on work |
Boards
- The main board Timeline shows only Epics, Planning Tasks and Milestones: the schedule for the whole project.
- Each role's board filters to its own Planning Tasks, e.g.
issuetype = "Planning Task" AND "Role" = "Art"(add Epics too if your team wants them). - Create the work items for each Planning Task's period and link them (relates to) to the matching Milestone.
How the extension helps
- Colors separate the schedule from delivery dates, and Milestones show as diamonds
- Hover over a Planning Task to see its role
- See working days, with weekends and public holidays excluded, while you schedule
- Milestones show their progress; hover to list the linked work still open
- A Jira admin saves the settings in the project, so teammates just install and go, with no file to import
You don't have to follow this setup. Tell the configuration which issue types you use for scheduling and for delivery dates, and which field holds the start date, and colors, holidays and working days all work the same. The issue types don't have to be called Planning Task or Milestone.
Hover over a Milestone to see all its linked work
Each linked issue is listed with its status, dates and title; finished ones are struck through. You can see what's left without opening each issue.
Features
Issue type colors
Planning Tasks and Milestones each get their own color, and Milestones can show as diamonds, so they stay easy to find on a busy Timeline.
Weekends and holidays
Your admin lists public holidays, company days off and make-up workdays, and days off are marked on the timeline. No external calendar is contacted.
Working days
Hover over or drag a bar to see its working days, with weekends and holidays excluded.
Milestone progress
Hover over a Milestone to see its linked issues, progress and due date.
Project settings
Settings can be saved in the Jira project, so they apply as soon as teammates open the Timeline. You can also import a configuration file.
Light and dark
Follows Jira's light or dark theme automatically.
All features
Timeline display
- Custom colors for Planning Tasks and Milestones, or keep Jira's own colors
- Milestones as diamonds, labeled with progress and due date
- Dashed outline on Epics flagged by a Jira field
- Darker shading from Target end to Due date
- Thinner, lighter dependency lines
- Hide the current period highlight (today's blue line stays)
- Hide issue keys in the left column
Dates
- Mark weekends
- Mark the days off your admin lists; make-up workdays count as working days
- Show working days, without weekends and holidays, when you hover over or drag a bar
- Choose which days of the week are days off
On hover
- Planning Task: shows its role
- Milestone: lists linked issues with status, dates and title
- Done issues are struck through; in-progress issues come first
Controls
- Milestones move as a whole and can't be stretched
- Scroll the timeline with the left and right arrow keys (hold Shift to go faster)
- Floating toolbar: pause or resume, reload; drag it anywhere
Settings
- Preview a configuration file before importing; you're asked before anything is replaced
- Export settings, restore the previous configuration, or remove a site
- Colors and switches sync to your other computers through Chrome
- A configuration file can include the Timeline URL for one-click opening
- Built-in configuration generator for admins, no hand-written JSON
Security and privacy
- Uses your current Jira sign-in; no password or API token needed
- Issue data is used only in your browser and never sent to the developer
- On a project Timeline, reads the project and its settings first; issue data is requested only when project settings or an imported configuration apply
- Reads data only; never changes anything in Jira
Get started
Users
- Install the extension.
- If your Jira admin saved the settings in the project, open the project's Timeline. That's it.
- Otherwise, click the extension icon in the toolbar and choose Manage settings.
- On Import & manage, import the configuration file (JSON) from your admin, check the preview, and save.
Uses your current Jira sign-in. You never enter a password or API token.
Jira admins
- Open Manage settings and switch to Create configuration (admin).
- Enter the site URL, the issue type IDs and the field IDs you need.
- Download the file, import it yourself and check the Timeline.
- Then share the file with your users.
The page links to where each ID can be found, so there's no JSON to write by hand.
Supported
- Project Timelines on Jira Cloud (https://*.atlassian.net)
- Not yet supported: Jira Server, Data Center and custom domains
- Extension language: English (default) and Traditional Chinese, following your browser language
- Jira language: English and Traditional Chinese
Privacy
Jira issue data is used only in your browser. It is never sent to the developer, and there is no tracking or analytics. See the privacy policy for details.