All 2024 2025 2026 Abstain Agile Almarise Ampin Ampin.app Amsterdam Anaheim API App Approval Approval Path Apps Artigiano Del Software AsciiDoc Atlassian Audit Automation Billing Board BPMN Brandbook Bug Carol Change Christmas Cloud Code Collaboration Comala Community Comparison Compliance Condition Conditional Confluence Content Contract Signatures Cooperation Cost Coworking CSV Custom Domains Customer Success Story Customization Dark Mode Data Analytics Data Center DC DC to Cloud Decadis Delegate Delegating Deployment Design Development DG Prolink Diagram Discount Document Management Documentation Domains Draw.io Drawio EazyBI Ecosystem Email Envorso EOL Event Excalidraw Excel Expectations Export External Share External Share for Confluence Fabio Genovese Feature Financial Flexible User License Forge Future Gladwell Academy Google Forms Growth Guest Guest Account Herzum HTML Integration Interview JES Jira Journey JSON Kanban Karma Knowledge Base Latex License Life in Codes Loom Macro Macro Pack Madalina Minut Management Maria Luisa Frigerio Markdown Marketplace Maximum Billing Quantity Mermaid Migration Miro MQB Nimble Evolution Notification Old Street Solutions OpenAPI Paid Partner Partnership PDF PDF Export PDF Export for Confluence Permission Schemes Plans PlantUML Platinum Predictions Premium Prepare Pricing Product Project Project Templates Report Reports Review Roadmap RTE SAML/SSO Savings Scroll Viewport Scrum Secure Security Selected User Settings Share Sharing Smart Checklist Smart Fields Software Deployment Song Sourcesense Spotlight Style Success Summary Summit Swagger Team Team''26 Test Manager Timeline Trend Tutorial Use Cases Video Vote Voting Warsaw Dynamics Web Summit Word Workflow Workspace Year
Categories
Tags
Management
Featured image

We’ve all been there: your Jira (or Confluence) instance hits 252 users. Everything seems fine until you realize you’re no longer on the 250-user plan. You’ve crossed the threshold into the 500-user tier, and your Atlassian bill has effectively doubled overnight. Lately, with pricing changes becoming more noticeable and impactful (as we explored in our previous article on peak billing ), these situations are no longer edge cases - they’re becoming the norm.

Featured image

OrbTech, a hypothetical mid-sized tech company, is deploying a new feature. The recent development of a new functionality takes many steps and requires cooperation from multiple departments. Let’s dive into their journey, highlighting how the Approval Path for Jira played a pivotal role. Creating the feature Maya, the dev lead, initiates the first approval request using Approval Path within their Jira system to ensure the new feature meets OrbTech’s initial standards and requirements.