Rapids is built to be a seamless extension of your Jira experience. It leverages Jira’s native architecture, ensuring that your data remains accurate, secure, and synchronized in real-time without requiring external databases.
Real-Time Synchronization
Because Rapids queries the Jira database directly via standard REST APIs, any change you make in Jira - such as updating an estimation, closing a ticket, or adding a link - is instantly reflected in the dependency graph. There is no manual sync button or background delay.
Respecting Jira Configuration
Rapids adapts to how your team already works:
- Estimations: Rapids supports both Story Points and Man-Days (Original Estimate). It dynamically reads whichever estimation field is active in your project settings.
- Issue Links: Rapids supports all default and custom Jira issue link types (e.g., blocks, is blocked by, depends on, relates to). You can configure which specific link types should be interpreted as blocking dependencies in the settings panel.
Security & Permissions
- Data Residency: Your project data never leaves the Atlassian Cloud. Rapids does not store your issues or link details on external servers, ensuring strict compliance with your organization’s data privacy policies.
- Access Control: Rapids respects all Jira permission schemes. Users can only see issues, sprints, and dependency links that they already have permission to view within standard Jira.