Back to product

Project Planning for Jira

User guide for the focused tasks dashboard, calendar, and project planner

Version 1.0.0 · Updated May 2026

On this page

1. Introduction

Project Planning for Jira is a Forge-hosted app that turns Jira into a focused task list, calendar, and project planner. It runs entirely inside Atlassian's infrastructure — no external services, no third-party servers — and gives you four primary surfaces: a personal tasks dashboard, a drag-and-drop calendar, a multi-phase project planner, and a settings page. Your data stays in Atlassian.

Who it's for

  • Product, project, and engineering managers running multi-quarter initiatives across teams.
  • Individuals who need a fast personal task view across every Jira project they have access to.
  • Consultants and agencies running client engagements with phases, deliverables, and milestones.
  • Any team that wants Jira-native planning without sending data to external tools.

2. Get started

2.1 Install the app

Project Planning for Jira installs in seconds from the Atlassian Marketplace. You need to be a Jira site admin to install apps for your site.

  1. Sign in to your Jira Cloud site as an admin.
  2. Open Apps → Explore more apps, or visit the listing on marketplace.atlassian.com.
  3. Search for Project Planning for Jira and click Get it now.
  4. Confirm the requested permissions and approve the install.
Free during beta. The app is free to install and use throughout 2026. Pricing tiers may be introduced in 2027 — early adopters receive grandfathered access details by email.

2.2 Open the dashboard

Once installed, the app appears in Jira's top navigation:

  1. Click Apps in the Jira top bar.
  2. Select Project Planning for Jira.
  3. The dashboard opens in your normal Jira chrome — no new tab, no new window.

The first time you open the dashboard, the app provisions a small amount of storage in your Jira region (preferences, saved filters). No data leaves Atlassian's infrastructure during this step.

2.3 A 5-minute tour

The app has four primary surfaces. Switch between them with the left-hand navigation or with keyboard shortcuts 14.

  • My Work — every task assigned to you across every project, in one filterable list.
  • Calendar — drag tasks onto your week. Day-off aware, work-hour aware, capacity aware.
  • Projects — Phases → Deliverables → Tasks. Each PM task can link to a real Jira issue.
  • Settings — theme, default view, work hours, field mappings, and privacy controls.

3. Tasks dashboard

The My Work page is the centerpiece of the app — a single, fast view of every Jira issue currently assigned to you, across every project you have access to.

3.1 What you see

  • Issue key, summary, status, priority, due date — the columns most teams need every day.
  • Project context — project name, key, and avatar so cross-project work doesn't blur together.
  • Sprint context — for issues on a Jira Software board, the current sprint is visible inline.
  • Updated time — relative timestamps (2 hours ago) so you can see what changed without scanning dates.

3.2 Filtering and sorting

Filters are non-destructive — they shape the view, never the underlying data.

  • Status — multi-select from your Jira status set (To Do, In Progress, Done, etc.).
  • Project — limit the list to one or more projects.
  • Priority — Highest, High, Medium, Low, Lowest.
  • Due date — overdue, this week, next week, no due date.
  • Search — free-text search across summary, description, and issue key. Press / to focus the search box.

Sort by updated time, due date, priority, or summary. The sort indicator shows direction; click again to reverse.

3.3 Inline editing

Most fields are editable without leaving the row:

  • Click the status pill to transition the issue (only valid transitions are offered).
  • Click the priority chip to change priority.
  • Click the due date to reschedule.
  • Click the assignee avatar to reassign.

Changes write through to Jira immediately. If a write fails (permissions, validation), the row reverts and the failure reason is shown in a toast.

3.4 Bulk actions

Select multiple tasks with x on each row, or Ctrl+A / Cmd+A to select all visible. Once selected, the action bar offers:

  • Transition — move all selected tasks to the same status (only transitions valid for every selected task are shown).
  • Reassign — set assignee on all selected.
  • Set priority — apply one priority to all selected.

Bulk operations run sequentially with a progress indicator. Failures are reported per-task — successful writes are not rolled back.

4. Calendar & scheduling

The Calendar view turns your unscheduled work into a realistic week. Tasks become draggable blocks; days off, work-hour limits, and per-task duration are all respected.

4.1 Layout

  • Week view (w) — seven columns, hour rows. Default for daily planning.
  • Month view (m) — high-level read of the next four weeks. Useful for spotting overloaded days.
  • Today (t) — jumps the viewport to the current day at any time.

4.2 Scheduling a task

  1. Drag a task from the unscheduled tray onto a calendar slot.
  2. The block snaps to the slot duration you configured in Settings (default 30 minutes).
  3. Resize the block by dragging its bottom edge to extend or shorten the time allocation.
  4. Drag the block to another slot to reschedule.
  5. Click the block to mark the underlying Jira issue as in progress, complete, or to add a comment without leaving the calendar.

4.3 Day-off and work-hour awareness

The calendar respects the working pattern you set in Settings → Work hours:

  • Days off — weekends and any custom days off are visually muted; tasks won't auto-suggest these.
  • Work-hour band — your configured working hours (e.g. 09:00–18:00) are highlighted; outside the band is dimmed.
  • Capacity indicator — each day shows the total scheduled hours and warns if you exceed your daily target.

4.4 Removing a task from the calendar

Drag the block off the calendar back into the unscheduled tray, or right-click → Unschedule. The Jira issue itself is not modified — only your private schedule is changed.

Privacy note. Schedules are private to you. Other users on your Jira site cannot see your scheduled blocks, and the app does not write schedule data to the Jira issue itself.

5. Project planning

The Projects view is for plans that don't fit cleanly into a single Jira project — multi-quarter initiatives, cross-team launches, or client engagements with phases and deliverables.

5.1 The hierarchy

Every plan in the app uses the same three-level structure:

LevelWhat it representsExamples
PhaseA time-boxed stage of the projectDiscovery, Build, Launch
DeliverableA concrete outcome the phase producesArchitecture doc, MVP build, Press release
TaskA unit of work assigned to a personWireframe homepage, Wire payments API, Draft press release

5.2 Linking deliverables to Jira

Each deliverable in your plan can be linked to one Jira issue (typically a Jira epic or story):

  • Click Link Jira issue on a deliverable and search by key or summary.
  • The linked issue's status, assignee, and due date sync into the plan view automatically.
  • Update the linked issue from inside the plan view — changes flow back to Jira.

5.3 Progress and milestones

  • Each phase shows a percent-complete bar based on the share of completed tasks within it.
  • Milestones can be flagged on phases that hit a contractual or external deadline; overdue milestones are highlighted at the top of the plan.
  • The plan timeline shows phase boundaries on a calendar so you can spot dependencies at a glance.

5.4 Recommendations

When a plan has been active for a few days, the app surfaces simple, rule-based recommendations: phases at risk of slipping, deliverables with no linked Jira work, tasks blocked by an overdue dependency. These are computed entirely from your plan and the linked Jira data — no external services are involved.

6. Settings

Open Settings from the gear icon in the top-right of the app, or with Ctrl+, / Cmd+,.

6.1 Preferences

  • Theme — Light, Dark, or follow the Jira theme.
  • Default view — which page (My Work, Calendar, Projects) opens first.
  • Date and number formatting — automatically follows the locale set on your Atlassian account.

6.2 Work hours

  • Work days — toggle each day of the week.
  • Working hours — start and end time per work day.
  • Daily capacity — the total hours of scheduled work that triggers the over-capacity warning.
  • Days off — pick specific dates that should be excluded from scheduling regardless of your weekly pattern.

6.3 Field mapping

If your Jira projects use custom fields for priority, story points, or due-date equivalents, map them here. The app reads these mappings to populate columns and the calendar correctly across heterogeneous projects.

6.4 Privacy

The Privacy tab gives you full GDPR controls without contacting support:

  • Export my data — downloads a JSON file containing every preference, schedule, and plan stored against your account.
  • Delete my data — removes all of your app data from storage. Confirmation requires typing a short token to prevent accidental deletion. Your Jira issues are not affected.
Erasure is permanent. The app does not maintain a recycle bin. Export your data first if you want a copy.

7. Keyboard shortcuts

The app is fully navigable from the keyboard. Press ? at any time to open the in-app shortcut sheet.

7.1 Global

ShortcutAction
?Show shortcut sheet
/Focus search
EscClose modal / clear selection
Ctrl+K / Cmd+KCommand palette
Ctrl+R / Cmd+RRefresh data
Ctrl+, / Cmd+,Open Settings

7.2 Navigation

ShortcutAction
14Switch view (My Work / Calendar / Projects / Reports)
j / Next item in list
k / Previous item
g gTop of list
Shift+GBottom of list

7.3 Tasks

ShortcutAction
EnterOpen task detail
eEdit task
xToggle selection
tTransition task
pSet priority
dSet due date
aReassign
cAdd comment
lLog work
oOpen in Jira

7.4 Calendar

ShortcutAction
wWeek view
mMonth view
tJump to today
/ Navigate weeks or months
nNew scheduled event
uUnschedule selected

7.5 Projects

ShortcutAction
n pNew project
n hNew phase
n dNew deliverable
n tNew task

8. Privacy & data

The app is engineered so your Jira data never leaves Atlassian. This is not a marketing claim — it is enforced at the manifest level.

  • Zero external fetch domains. The Forge manifest declares no external services. The runtime would block any attempt at external HTTP egress.
  • Region-matched storage. All persistent app data lives in Atlassian Forge KVS, region-matched to your Jira instance.
  • No subprocessors. The only data processor involved is Atlassian itself, which already governs your Jira instance.
  • Auto-cleanup on uninstall. When the app is uninstalled, a Forge lifecycle trigger purges all data scoped to the installation within minutes.

For the full statement, see the Privacy Policy and Security Statement.

9. Permissions

The app requests the minimum set of Jira scopes needed to function. Each is mapped to a feature you can see in the UI.

ScopeWhy we need it
read:jira-workFetch the issues assigned to you for the dashboard.
write:jira-workTransition tasks, set priority, change assignee, add comments, log work.
read:project:jiraShow project name, key, and avatar on each task; populate the project filter.
read:jira-userDisplay assignee names and avatars; search assignable users for bulk reassign.
storage:appPersist preferences, saved filters, schedules, and project plans in Forge KVS.
read:board-scope:jira-software / read:sprint:jira-softwareShow sprint context on tasks and group by sprint.
read:field:jira / read:field-configuration:jiraRead custom field metadata for the field-mapping configuration.

The app does not request write access to projects, schemes, configurations, or admin-level data.

10. Troubleshooting

The dashboard is empty

  • Confirm you actually have Jira issues assigned to you — open Jira's own filter assignee = currentUser() in a separate tab.
  • Clear your active filters from the filter bar (the Clear all link).
  • Refresh with Ctrl+R / Cmd+R.

An inline edit didn't save

  • Check the toast at the bottom of the screen — it explains the error returned by Jira.
  • Common causes: you don't have permission to edit that field on that project, the workflow doesn't allow that transition from the current status, or the value is rejected by a project validator.
  • Try the same edit directly in Jira to surface the underlying error.

Dates display in an odd format

  • The app follows the locale set on your Atlassian account profile.
  • Open your Atlassian profile → Account preferences → Language & region.
  • Pick a locale (e.g. English (United Kingdom)) and reload the dashboard.

The greeting shows "there" instead of my name

  • This can happen on first login if your display name has not yet been provisioned in Jira.
  • Open Jira's profile page once, then reload the app.

I can see the app but a feature is missing

  • The AI assistant, AI scheduler, and Daily briefing components are intentionally not included in this release. The product roadmap lists them under future; they will be opt-in when they ship and will be subject to a clear privacy disclosure.

11. FAQ

Does the app send my Jira data to OpenAI or any other AI service?

No. The app makes zero external HTTP requests. AI features are not included in this release. The Forge manifest declares no external fetch domains, which means the platform itself would block any attempt to send data outside Atlassian.

Where is my data stored?

All app data (preferences, schedules, project plans) is stored in Atlassian Forge KVS, region-matched to your Jira Cloud instance. Your Jira issues continue to live in your Jira projects exactly as before — the app reads them through the Jira REST API as you, with your permissions.

Can other users on my Jira site see my schedules?

No. Schedules are scoped to your account. Project plans are visible to anyone with access to the Jira issues they reference.

What happens to my data if I uninstall the app?

The Forge platform fires an appUninstalled lifecycle event. The app's handler deletes all installation-scoped data within minutes. Backups, if any, are purged within 30 days per the DPA.

Does it work with Jira Service Management?

The current release is targeted at Jira Software / Jira Cloud. We have not declared compatibility with Jira Service Management because JSM workflows (queues, requests, SLAs) need bespoke support that is not yet in the app. JSM compatibility is on the roadmap.

Is the app GDPR-compliant?

Yes. Article 15 (export) and Article 17 (erasure) are exposed as one-click controls in Settings → Privacy. The app uses no subprocessors and performs no cross-border data transfer beyond what Atlassian itself does as your existing Jira processor.

Can I use the app on mobile?

The app is built for the desktop Jira Cloud experience. It will render on tablets, but small phone screens are not a primary target.

Is there a paid tier?

Not in this release. The app is free during the public beta. Future pricing tiers will be communicated by email and on the Marketplace listing well before they take effect.

12. Support

ChannelUse it for
support@chefstackz.comHow-to questions, bug reports, feature requests
security@chefstackz.comResponsible security disclosure
privacy@chefstackz.comGDPR & privacy questions
legal@chefstackz.comDPA, terms, vendor onboarding

Response targets

SeverityInitial responseResolution target
P0 — outage1 hour (24×7)4 hours
P1 — major feature broken4 business hours1 business day
P2 — minor degradation1 business day5 business days
P3 — question / cosmetic2 business daysbest-effort

Business hours: Monday–Friday, 09:00–18:00 UTC. Languages: English.