Trees across projects
Mix work items from any project, at any depth. Add folders, memos and planning items for work that isn't in Jira yet. Drag rows around, or use the keyboard, cut and paste.
For Jira Cloud · Built on Atlassian Forge
TreeCraft: Issue Hierarchies
Put work items from any project into one tree, as deep as you need. Rules keep it up to date. Totals, progress and formulas roll up the branches. And when the numbers are right, you can write them back to Jira.
What it does
Jira gives you epics, stories and subtasks. Real work rarely fits in three levels or one project. TreeCraft lets you arrange it the way your team thinks about it.
Rules that build the tree
Pull work items in from a JQL query, with fields and values suggested as you type, a board, a text search or another hierarchy. Bring in subtasks, children and linked work items. Filter, sort and group by any field. The tree refreshes when Jira changes.
Totals, progress and formulas
Show any Jira field and edit it in place. Add up estimates and story points over each branch, track progress and time in status, or write your own formulas, with field names and functions suggested as you type.
Write-backs to Jira
Copy a total into a field, move a parent's status when its children are done, shift due dates by working days, or turn planning items into real work items. You see a preview first, and every run can be undone.
Search and workflows
Find a hierarchy's work items anywhere in Jira with issue in treecraftHierarchy("Roadmap"). Query the tree itself (children of, ancestors of, leaves). Use a workflow condition or validator to allow a transition only for work items in a hierarchy.
Right where you work
Open hierarchies from the app's own page, a project page, a work item panel or a board, and put a hierarchy or its cumulative flow chart on a dashboard. The app is available in eight languages and follows your site's light or dark theme.
Views, export and sharing
Save column sets as views and share them with groups or roles. Export to Excel, CSV or JSON, print the current view, or send a link that opens the same state.
Permissions and admin
Give View, Edit, Automate or Control per hierarchy to everyone, groups, project roles or people. Name app admins who aren't Jira admins. Set limits, a working calendar, history, backups and restores.
Rovo agent
Describe the hierarchy you want in plain words. The Hierarchy helper agent in Rovo suggests the rules and adds them once you confirm. It can also outline part of a tree so Rovo can summarize it.
Conditional formatting
Colour rows and cells from their values, so late work, large estimates and blocked work stand out. Highlight the rows that pass your tests, give each status or person its own colour, or split story points into bands with level bars. Rules are saved with the view, colour timeline bars too, and carry into dashboard gadgets and Excel exports. More on formatting
Timeline and workload
Plan with a timeline beside the tree. Drag bars to change dates, link dependencies, let Schedule move work that starts too early, and follow the critical path. See each person's work against their hours, and level it when someone has too much.
A closer look
Screens from the app, with sample data.
Start from a template, or by levels
Pick a starting point: an empty tree, your own backlog, a release, a board, or the levels you work in, such as initiative, epic, story and subtask. The rules are made for you and stay editable. You can also narrow it with JQL as you create it.
Make late work stand out
Formatting rules colour rows and cells from their values: late work in red, each status category in its colour, story points with level bars. Start from a ready-made rule or from a column's menu, and the grid changes as you edit.
Formulas without looking up names
Type the start of a name, and the formula box lists the fields, functions and aggregations that match, with each field's name in Jira on the line under the list. JQL boxes do the same for fields, operators and values.
Change Jira in bulk, safely
Write-backs show what would change before anything happens. They run as you, with your Jira permissions, and each run is listed so you can undo it.
A settings page for each hierarchy
Each hierarchy has its own settings page, with tabs for its details, who can access it, Jira search and views. Deleting it is kept apart in a Danger zone tab.
Settings in Jira's admin area
Admins find the app's settings in Jira's admin area, grouped in one menu. A setup guide takes a new site through access, limits and a first hierarchy.
Plan on a timeline
Bars show each work item's dates beside the tree, with arrows for dependencies. Turn on the critical path to see which work sets the finish date, and let Schedule move work that starts too early.
See who has too much
The workload compares each person's planned work with their hours, week by week. Drag a work item to someone with room, or let levelling move lower-priority work later.
Your data stays in Atlassian
TreeCraft is built to Atlassian's Runs on Atlassian requirements. There is no PluginCraft server in the middle.
- Stored in your Jira siteHierarchies, rules, history and settings live in Atlassian's Forge storage for your Jira site.
- Nothing leaves AtlassianThe app makes no calls to outside servers. It has no analytics, no tracking and no outside AI services.
- Your Jira permissions applyPeople only see and change the work items Jira already lets them see and change.
- Logs without contentApp logs hold ids, counts and error codes. Never work item text, names or emails.
Details are in the privacy policy.
Licensing
Licensing is coming soon.
Questions in the meantime? Write to info@plugincraft.ca.
Email us