A board app is sold on its options and kept for something duller. Manage Board, the board SolaceIn built for Jira Server, was downloaded 1,300+ times by the hardest audience Atlassian had: administrators who could not try an app on a whim, because installing one meant a change request. What kept it installed was never the swimlane rules. It was how fast it opened on somebody else's hardware, whether it survived the next Jira upgrade, and how many clicks the move you came to make took.
Two things this post is not. Manage Board is a Jira Server app and stays one: Atlassian ended Server support on 15 February 2024, and the listing now offers no trial and no purchase, only a .jar download, under the notice that server apps are no longer sold or supported. And Time And History, the Cloud app those rules now govern, is Jira Cloud only: there is no Server or Data Center build of it. If you are still self-hosted, nothing here is for sale to you; if you are on Cloud, the Server years are the reason to read on.
Boards are not judged on features
Board apps are sold on configuration: card layouts, swimlane rules, colour schemes, field pickers. They are kept on something duller. A board is a screen you open several times a day, usually while thinking about something else. What you notice is three things: whether it opened, whether it looks the way it did yesterday, and how many clicks the move you came to make took.
None of that produces a screenshot, which is why it kept losing to features on our own roadmap.
Three rules Jira Server beat into us
Manage Board was built for Jira Server, declaring compatibility with Jira 7.13 to 8.5, and self-hosted Jira imposed constraints a cloud-only board never had to think about.
- It opened on somebody else's hardware. A board that felt instant on a demo instance could crawl on a decade-old production instance whose workflow every administrator before you had edited and nobody had rebuilt. Performance was not a polish item there; it was the feature.
- It was installed by an administrator, not a user. Nobody added a Server app on a whim. It arrived through a change request, so it had to be worth the paperwork on day one.
- It had to survive the upgrade cycle. Server admins planned Jira upgrades months ahead, and an app that might be compatible was a reason to postpone the upgrade or drop the app. Being ready early was worth more than any single feature.
An app that got those three right earned the chance to be judged on its board. An app that got them wrong was uninstalled before anyone looked at the swimlanes.
All three came off Server with us, and each one is visible in Time And History today.
- It runs on somebody else's instance. Every Jira read runs as the person viewing the report, so nobody sees an issue their own Jira permissions would hide.
- It has to be worth the paperwork on day one. Pick a project and a date range and the table is there — no custom field to create, no automation rule to switch on, no quarter spent waiting for data to accumulate, because the numbers come out of the change history Jira already stored.
- It has to survive the next change. Durations are floored rather than rounded up, the table footer states which page its Avg, Median, Min and Max cover, and a status an issue never entered shows a dash rather than a zero. Conventions that do not drift are what let a number you quoted in March survive being re-run in September.
Every option has a running cost
The instinct with a board is to make everything configurable and let each team decide. That instinct is expensive in a way that is easy to miss at the time.
Each option has to be documented, tested against every supported Jira version, kept working through the next upgrade, and eventually explained to whoever inherits your instance from the person who configured it. A setting added in an afternoon is maintained for years, and most of those years are yours rather than ours.
The useful question is not "could this be configurable" but "what does your team lose if it is not". Most of the time the answer is nothing, and the default gets better instead. The same trade turns up well outside boards — the release branch that assembles itself is this argument applied to release tooling, where the default is one command instead of an hour of manual merging.
Manage Board on the Marketplace today
Manage Board was downloaded 1,300+ times on the Atlassian Marketplace during the Server era, a count read from the listing on 6 September 2026.
The review that puts the outcome best is Philip Bennett's on that listing: "Great job, thank you! With this app, I save a lot of time managing my projects." Not one word about an option.
That is the outcome worth optimising for. A board is infrastructure: the compliment it earns is that nobody talks about it.
Manage Board's platform is gone; SolaceIn is not. Time And History shipped 2.3.0 on 6 September 2026 and is one of the three apps we publish. The Cloud side is younger and the numbers are smaller, which is the honest way to give them: 5.0 out of 5 from three reviews.
Check the claim on one sprint
Everything above is checkable in five minutes and without a purchase order. Open Time in Status on the sprint that closed last week, set your work calendar, and read the footer: Avg, Median, Min and Max over the issues on the page in front of you, so you can recompute them from the rows on screen. If the number does not survive that, you have lost five minutes.
You could do the same thing by hand — export the change history and compute the intervals in a spreadsheet. It works once. The file is stale the moment it is downloaded, the arithmetic is yours to defend, and next quarter somebody repeats it slightly differently and gets a different number with the same name; the manual and native routes are sized up in full here, and what a work calendar changes in your numbers covers the clock all of it is measured on.
Time And History for Jira Cloud is five reports built from issue history — Time in Status, Assignee Time, Time to Resolution, Time in Changes and Transition Count — and each answers one question rather than one report you configure into five. Install it from the Atlassian Marketplace and run Time in Status on last week's sprint — free for up to 10 users, so the first team can try it before anyone has to raise a purchase order.
Manage Board stays a Jira Server app; the rule about defaults is the one that carried over. Download count, Marketplace terms and the review quoted above checked 6 September 2026 — the listings are the authority.