Frequently Asked Questions

Weir is a capacity planning app for Jira Cloud. It helps engineering and project teams understand how much work their people can actually take on before committing to a sprint. Instead of discovering overloads mid-sprint, Weir surfaces load imbalances at planning time - so you can balance work across your team before things tip.

Most Jira teams plan sprints by feel - dragging issues into a sprint until it "looks about right." The result is that some people end up with three times the work of others, issues get deprioritised mid-sprint, and velocity becomes unpredictable. Weir makes the workload visible before the sprint starts, so teams can make deliberate assignments rather than hopeful ones.

Capacity planning is the practice of comparing the work you want to do against the time and people available to do it. In a sprint context, it means knowing how many story points or hours each person can take on - accounting for leave, part-time availability, and existing commitments - before you finalise which issues go in. Good capacity planning reduces mid-sprint surprises and helps teams consistently deliver what they commit to.

Weir works directly within your existing Jira projects and sprints. It reads sprint data from Jira - issues, assignees, estimates - and adds a capacity layer on top. You continue planning in Jira as usual; Weir gives you a clear view of who is over-committed and who has room before you start the sprint. There is nothing to migrate and no parallel system to maintain.

Weir is currently in development. We do not have a firm launch date to share yet - until it's published to the Atlassian Marketplace, it isn't possible to install or trial the app. Check this page or the Weir product page for updates as development progresses.

Send an email to support@aquariumapps.io with the subject "Weir launch notification" and we will add you to the list. We will send a single email when Weir becomes available on the Marketplace - no newsletters, no drip campaigns.

Pricing and trial details are still being worked out. Atlassian Marketplace apps commonly include a free trial period, and we intend to offer one. Specific pricing will be confirmed closer to launch.

The planned feature set for the initial release includes:

• Sprint load visualisation - a clear view of total estimated work across an active or upcoming sprint, broken down by person
• Person-level availability - set working hours, planned leave, and part-time capacity per person so estimates reflect reality
• Overload detection - flags anyone over capacity before you commit the sprint (see below for how)
• Work balancing - see at a glance who has headroom and who is at risk, making it easy to redistribute issues during sprint planning

Weir compares the total estimated work assigned to each person in a sprint against their configured availability for the sprint period. Anyone whose assigned load exceeds their available time is flagged. The intent is to make this visible at planning time - before the sprint starts - rather than discovering it on day three when someone is already behind.

No - see "How does Weir relate to Jira sprints?" above. Weir adds a capacity layer alongside Jira's existing planning tools; it does not replace the backlog view or the sprint board.

Yes, like Stint - see "Does Aquarium Apps have access to my Jira data?" below for what that means.

Weir will read sprint and issue data from Jira's APIs and store app-specific state (availability settings, capacity configurations) in Forge Storage on Atlassian's infrastructure. Your Jira data stays in Jira - Weir does not export it or copy it to any external system.

No. Because Weir runs on Atlassian Forge, Aquarium Apps operates no external servers and has no ability to query your Jira data. Forge apps are isolated to your Jira instance and can only access data through Atlassian's permissioned APIs. Aquarium Apps cannot see your issues, your team, or your sprint data.

Your Jira data is unaffected - Weir reads it but does not modify or copy it outside your instance. App-specific configuration in Forge Storage is soft-deleted per our Privacy Policy's retention terms.