Use Planning to agree dates for related issues and identify work that needs attention. A saved QQL filter selects the issues. You can inspect their hierarchy and connections, edit dates and change status through the workflow. Saved changes belong to the issues and appear elsewhere in Quevell.
When to use Planning
Open a plan when preparing a release, coordinating teams or reviewing dates. In the same view, you can inspect parent and nested issues, unfinished blockers and work that extends beyond an agreed schedule.
How Planning works. You decide issue dates using the schedule and its warnings. Changing one issue's dates leaves connected issue dates unchanged. Durations include weekends. Critical paths and assignee capacity are not calculated. Review which warnings will appear or disappear before saving new dates.
Use the team board and sprint controls to manage a sprint's scope and goal. Planning displays issue dates. Changing those dates does not start a sprint or add issues to one.
Check access and prepare issues
Viewing a plan requires access to its saved filter and issues. Project permissions and issue security apply throughout. Sharing a filter does not grant access to its results: two people may see different issues and totals in the same plan. Archived issues are excluded from Planning.
| Action | Access |
|---|---|
| Read the plan and issue details | Access to the saved filter and the relevant issues |
| Change a start or due date | Permission to edit the selected issue |
| Add or remove a connection | Permission to edit both issues; both must be included in the loaded plan |
| Change status | Separate transition permission and an available workflow transition |
If an action is unavailable, ask an administrator to check company and project access and issue security.
An issue can have one date or no dates. There is no need to invent dates to make it appear in the plan.
Choose the plan's source
- Open "Planning" in the sidebar, or the "Planning" tab of a project when working within that project.
- Choose a "Saved filter" below the table. If no filter fits, follow "Manage filters" to issue search, write a QQL query and save it. Return to Planning and select the filter.
- Expand "Show QQL" to check the condition. A project's tab limits the results to that project, even when the saved filter includes several projects.
- Check the loaded issue count and any partial-plan notice before assessing the schedule.
For example, you can save this query to select work from two projects. Replace WEB and API with your own project keys:
project in (WEB, API) order by dueDate asc
The saved query defines the source. View filters below the table only narrow the loaded data. They do not add an issue from another project if it was absent from the source result. See the QQL reference for conditions, functions and sorting.
Without a selected filter, Planning does not load the whole company. On a later visit, the browser may select this person's last available filter in this company.
Check how much of the plan is loaded
"Number of issues" beside the legend sets a loading limit from 1 to 2000. The default is 200. Enter the limit and press "Apply".
"Loaded 30 of 2001 issues" means that 2001 accessible issues match the saved filter, but only 30 have been loaded for this plan. Increase the limit or narrow the saved filter. If more than 2000 issues match, use smaller filters to review the work in parts.
A separate count describes rows matching the view filters. Collapsing branches reduces the displayed row count; search narrows the matches. Parent rows retained as context are counted separately.
Derived dates, completion counts, connections and warnings use loaded issues only. A parent outside the selection is not added automatically. Planning loads up to 4000 connections between selected issues and shows a separate warning if that limit is exceeded. A partial plan without warnings does not establish that work outside it has no problems.
Read the hierarchy and timeline
On a wide screen, the issue hierarchy is on the left and the calendar timeline is on the right. Hierarchy levels follow company settings. Expand an individual branch or use "Expand all" and "Collapse all". A parent's completion count compares loaded descendants in the "Done" category with all its loaded descendants, across every nested level. Completion follows the status category, not the workflow status name.
| Mark | Meaning |
|---|---|
| Solid bar | The issue's own start and due dates |
| Dashed bar | A range derived from loaded descendants when the parent has no dates of its own |
| Single marker | Only a start date or only a due date is set |
| Invalid-date crosses | The start is after the due date; the dates need to be reviewed |
| "Today" line | The current day on the timeline |
A parent's own dates take precedence over dates derived from its descendants. When only one parent date is set, Planning does not fill in the other automatically. Issues without dates remain in the hierarchy. A derived range also requires review when descendant dates are incomplete.
Choose "Days", "Weeks" or "Months" to change scale. The arrows beside "Today" move the period; "Today" returns to the current date. Drag the divider in the hierarchy header to change the space available for names on a wide screen. The legend below the table explains the marks.
Find an issue and open its details
Search by key or title below the table, or filter by project and status. "More filters" contains assignee, priority and hierarchy level. The status filter groups issues by status category; each row retains the exact workflow status name. Parents of matching issues remain in the hierarchy as context.
Select an issue to open a compact panel over the plan. It contains the assignee, priority, dates, status, connections and reasons for warnings. The key at the top opens the normal issue page. "Show on timeline" moves the period to the selected issue.
On a phone, the main view is a list with dates. "Show on timeline" opens a compact timeline for the selected issue. Edit dates in the panel's fields. Use "Back to plan", close the panel or press outside it to return to the list. Closing the panel discards its unsaved date draft.
Review schedule warnings
Two expandable summaries sit below the filters. "Needs attention" lists issues that require review because of schedule conflicts or overdue work. "Dates to review" contains issues with missing or incomplete dates that have no other warnings. Several reasons on one issue still count as one issue.
| Reason | What to review |
|---|---|
| Start after due date | The selected issue's two dates |
| Overdue | An unfinished issue whose due date has passed |
| Blocked | An unfinished issue that blocks this work |
| Dependency date conflict | A blocker whose due date is after the dependent issue's start |
| Dependency cycle | Blocking connections that lead back to the same issue |
| Outside parent dates | Nested issue dates beyond the parent's own schedule |
| Descendant date conflict | Nested work beyond the selected parent's own schedule |
| Incomplete dates | A missing boundary or an incomplete derived range |
Select an issue in a summary to reveal it in the plan and read the explanation. The list has pages. An issue in the "Done" category is not treated as currently overdue or as an unfinished blocker. Other date conflicts can remain visible.
Dependency checks consider blocking connections within the loaded plan. An ordinary connection does not create a blocker. A warning describes the plan's data; the workflow still decides which status transitions are available.
Change dates
- Select an issue and edit "Start date" and "Due date" in its panel. You can clear a field if that date is no longer known.
- Review the preview: current and proposed dates, warnings on this issue, and changes to warnings on other loaded connected issues.
- Press "Save" to write the dates or "Cancel" to discard the proposal.
On a wide screen, you can drag an issue's own bar with two valid dates to move the interval, or drag an edge to change one boundary. Dragging opens the same preview and requires saving. A parent's derived bar only represents descendant dates and cannot be dragged to change them. The calendar step is one day; equal start and due dates represent a single day.
Saving changes only the selected issue. Its parent, descendants and connected issues keep their dates. Review the new warnings and adjust other issues separately if necessary. Date changes use the normal access checks and appear in issue history.
If someone has already changed the issue, Quevell reports a conflict and retains the draft in the open panel. Press "Refresh plan" inside the panel, compare the proposal with the current dates, then save again or cancel. Save any draft you want to keep before changing the source or closing the panel: drafts do not carry over to another plan.
Change status
Press the current status in the panel. The menu lists transitions available to you from the current workflow state. Each entry shows its target status and action name. When no transitions are available, status changes are unavailable.
Save or cancel a pending date draft first. Then select a transition. It runs immediately, without a separate status save button, using Quevell's normal validation, history and automation.
After a successful transition, the complete loaded plan refreshes, including the issue state, hierarchy, counts and warnings. An issue that no longer matches the saved QQL filter leaves the result. For a version conflict, press "Refresh plan" and choose a current transition. Read any access or network error; if the write outcome is uncertain, refresh the plan before trying again.
Inspect and change dependencies
The connections section in an issue's panel shows the type, direction and other issue. Select a connected issue to move to it within the plan. "Show connections" and "Hide connections" control timeline lines. "Dependency chain" includes connections of neighbouring issues, but displays a bounded view of up to two steps and 12 connections, not the company's entire graph. "Show more" expands the list from four to 12 connections; it does not remove that limit or reveal all company connections.
A timeline line requires both rows to be visible, a due date on its source and a start date on its destination. A missing line therefore does not mean there is no saved connection: check the panel's list.
To add a connection:
- Open "Add dependency".
- Choose a link type and a direction relative to the current issue.
- Type an issue key or part of its title, or paste an issue link from this same site. Select the matching suggestion.
- Press "Add". The connection is saved immediately and the plan refreshes.
Suggestions come from editable issues in the loaded plan. If the issue is missing, include it in the saved filter and check the loading limit and permissions. Use the company-wide plan with both projects for a connection across projects. An existing identical connection is not added again. Link types and labels follow company settings.
"Remove dependency" deletes the chosen connection immediately. Adding or removing a connection does not change issue dates. Blocking connections take part in warning calculations; other types keep their own meaning without becoming blockers.
Refresh and share a view
"Refresh" reads the saved filter and issues again. Use it after changes in another tab or by another person. Changing the source does not present old rows as the new result. If a filter is deleted, unavailable or invalid, correct it through issue search or choose another filter.
The page address contains the chosen filter and view settings, so you can copy it to a colleague. The colleague needs their own access to the filter and issues. The browser also remembers the last available filter and hierarchy width separately for each person and company.
"Reset view" clears display settings and the draft while keeping the selected filter. It does not undo saved dates, statuses or connections. Change saved data through a new action on the issue.
Use the keyboard
| Focus location | Keys and result |
|---|---|
| Issue hierarchy | Up and Down select a row; Right expands a branch and Left collapses it |
| Issue hierarchy | Home and End select the first and last visible rows; Enter opens details |
| Plan | Escape clears selection and closes details; an open menu handles Escape first |
| Hierarchy divider | Left and Right change width; Home restores the initial width and End selects the maximum |
| Dependency search | Up and Down select a suggestion, Enter confirms it and Escape closes the list |
| Status menu | Tab moves through actions and Enter chooses one; Escape closes the menu and returns focus to the status |
Dates can be entered in fields without dragging. Reach the issue key with Tab and open it with Enter.
Resolve unexpected results
| Situation | Next step |
|---|---|
| The plan is empty | Check the saved filter, project tab and view filters; archived issues are excluded |
| An issue appears in Quevell search but is absent from the plan | Check QQL, the loading limit and the current project's restriction |
| A parent or dependency is not visible | Include both issues in the source, expand branches and check the connection limit |
| An issue is not listed in dependency suggestions | Check that both issues are loaded and editable |
| Dates are not editable | Ask an administrator to check edit permission, issue access and account restrictions, including your assigned user seat |
| A status transition is not available | Check separate transition permission, the workflow and any pending date draft |
| An issue disappears after saving | Check whether it still matches the saved filter and the view filters |
| A conflict or error appears | Read the message, refresh the plan and compare the current data with your intended change |
Open the issue by its key to work with other fields, attachments and comments. See Issues and projects for those actions.