Jira apps, built on Forge
Your data never leaves Atlassian.
Vector Grove builds small, sharp Jira apps that turn information Jira already has into ordinary, searchable fields. Two apps, each doing one thing completely.
Both apps run entirely on Atlassian’s Forge platform. There are no Vector Grove servers, no third-party services, no API keys to hand over, and no data leaving Atlassian infrastructure — because there is nowhere for it to go.
The apps
Sprint Dates for Jira
Sprint start and end dates as real, searchable fields
Jira knows when every sprint starts and ends — it just will not let you search by it. This adds Sprint Start Date and Sprint End Date to every work item in a sprint, as ordinary indexed Jira date fields.
How it worksTest Coverage for Jira
Which requirements have tests? Ask Jira, in JQL
Your test management app knows which work items have tests. Jira does not. This adds Test Coverage and Linked Test Count as ordinary indexed Jira fields, computed from the links already in your site.
How it worksMarketplace status. Both apps are in final preparation for listing on the Atlassian Marketplace. This page will carry the listing links once they are live.
One idea, applied twice
Jira’s search is the most powerful thing in the product, and it can only see fields. Anything that is not a field — a sprint’s schedule, a link to a test — can at best be dug out with a search: it can never be a navigator column, never be sorted on, and never land in a CSV export.
Both apps do the same thing about it: take something Jira already knows, and publish it as a real, indexed field.
"Sprint End Date" <= endOfMonth() AND status != Done
"Test Coverage" = "Not covered" AND status != Done AND fixVersion = "3.2"
Because the results are ordinary Jira fields, they work everywhere ordinary fields work: JQL, saved filters, navigator columns and sorting, and CSV export.
Why “runs on Atlassian” matters
Many Jira apps that add fields do that work on the vendor’s own servers. When they do, your issue data leaves Atlassian, sits in someone else’s database, and your security review has to account for it.
Neither of these apps can do that. They are Forge apps with no egress permissions at all, so the platform itself — not a promise in a privacy policy — is what stops data from leaving.
Pricing
Neither app is on the Atlassian Marketplace yet, so there is nothing to buy today and no rate is binding anywhere — see Marketplace status above. What follows is what the pricing will be when they list.
Both apps will be free on Jira sites of 10 users or fewer. That is Atlassian’s rule for Marketplace apps, not a trial. Above that, each will be priced per user per month with the rate falling as your site grows; the rates will be shown on the Marketplace listing, which is the only place they are ever binding.
Support
Bug reports, questions and feature requests go to the public issue tracker. We aim to respond within two business days. More detail on the support page.