Skip to main content

View Project Overview

Route: Open Project Overview
Assignee: Project Manager / All team members 📊

Project Overview displays all Jira tickets of the project in a hierarchical structure — from Epic down to Task/Story and Subtask. The PM uses this screen to track progress and update ticket status directly in AIPD without opening Jira.

Prerequisite setup

Data in Project Overview is pulled from Jira via the integration configured in Setup Jira & Confluence. If the table is empty or missing data, check the project's Jira connection.


Overview interface

The screen consists of two main areas:

  • Filter bar at the top: Search and ticket classification filters.
  • Data table at the bottom: Ticket list in a hierarchical tree structure.

Step 1: Search and filter tickets

Above the table there are 4 independent filters — they can be combined at the same time:

FilterDescription
SearchSearch by Jira Key (e.g., PROJ-123) or Summary content. Press Enter to apply, or press the X button to clear.
All typesFilter by issue type: Epic, Task, Story, Bug, Subtask, etc. (list pulled dynamically from project data).
All statusesFilter by status: To Do, In Progress, Done, Blocked.
All assigneesFilter by assignee — list pulled from the project's Jira members.

Click "Clear" at the end of the row to remove all filters and return to the default state.


Step 2: Read the ticket table

The table displays the following columns:

ColumnContent
KeyJira ticket code (e.g., PROJ-42). Badge color changes by type: Epic (dark blue), Task/Story/Bug (default), Subtask (lighter).
SummaryTicket title. Child tickets are indented by level and connected by hierarchy lines.
TypeIssue type (Epic, Task, Story, Bug, Subtask, etc.).
StatusCurrent status with a colored badge: Done (green), In Progress (blue), Blocked (red), To Do (gray).
AssigneeThe assignee — shown with an initial-letter avatar and full name.
Due DateDeadline.

Expand / collapse the hierarchy tree

Tickets that have children (an Epic with child Tasks, a Task with Subtasks) show an arrow ▾ button on the left of the name. Click to collapse the whole child branch. Click again to expand it.

Load more data

The table loads 20 tickets at a time. When you scroll to the bottom of the page, the system automatically loads more and shows a "Loading more..." message at the bottom.


Step 3: Edit a ticket (PM / users with Update permission)

Edit permission

The Edit button only appears for users with Update permission on the Project Overview screen (workspace.project.overview:update). Members with only View permission can see the table but cannot edit — clicking a row will not show the menu.

The PM configures permissions for each role in Setup Access Management.

Perform the edit:

  1. Click any row in the table — a small floating menu appears just above or below that row.
  2. The floating menu has 2 buttons:
    • Edit (pencil icon) — opens the ticket edit modal.
    • Close (X icon) — closes the menu without doing anything.
  3. Click "Edit" to open the "Edit {Jira Key}" modal.

Fields in the edit modal

FieldRequiredNote
SummaryYesTicket title
DescriptionNoDetailed description (textarea auto-expands 3–8 lines)
StatusYesTo Do / In Progress / Done / Blocked
AssigneeNoPick from the member list — can be cleared with the X button in the field
Due dateNoPick a date from the DatePicker
  1. Fill in the information you want to change.
  2. Click "Save" to save — the row in the table updates immediately without reloading the page.
  3. Click "Cancel" to close the modal without saving.

Permissions summary

ActionViewUpdate
View the ticket table
Filter and search
Expand / collapse the tree
Click row → show floating menu
Edit Summary, Status, Assignee, Due date