# ij-solutions > There is always a solution > Contact: jonas@ij-solutions.com ### Posts #### A Comprehensive Guide to Understanding Epics and Cloning an Issue in Jira Manual cloning can be a time-consuming challenge for Jira admins, team leads, and project managers who manage recurring templates, scale workflows across teams, or maintain dependencies in cross-project initiatives. Cloning issues in Jira offers a solution, allowing teams to duplicate tasks effortlessly while retaining key details.Simplify Workflows with Issue CloningIn Jira, an issue — also known as a work item, request, ticket, or task — represents a single work item that’s tracked from creation to completion. However, while cloning an issue in Jira is relatively straightforward, complications tend to arise when cloning Epics with multiple related issues. The root of the problem lies with Jira’s native cloning function, which only operates at the issue level. This limitation requires teams managing recurring projects, sprint templates, or multi-team Epics to manually duplicate and reorganize every related issue. As a result, relationships can become broken, workflows may get disrupted, and inconsistencies across projects will start to emerge.The Pitfalls of Replicating Issues ManuallyWithout issue cloning, teams must resort to manual data entry, which is slow, error-prone, and inefficient. This repetitive task not only delays decision-making but also increases the risk of a duplicate issue in Jira and human error, leading to:Data entry errors: Missing fields or incorrect valuesRelationship breaks: Child issues losing parent linksCross-project gaps: Issues losing context when moved between projectsCompliance risks: Incomplete audit trails and missing historical recordsMoreover, mishandled data or formatting inconsistencies during manual duplication can lead to regulatory breaches, which put organizations at risk. It also increases the risk of inconsistent task relationships and incomplete setups, especially in critical processes like deployment, where missing dependencies can cause operational failure.Practical Applications of Cloning Issues in JiraOn a positive note, cloning issues in Jira simplifies project management by eliminating redundant work and ensuring accuracy across different teams and projects. Here are several scenarios where this feature can prove valuable:Moving issues from a designer’s board to a developer’s projectSharing a bug report from a support portal with the engineering teamUsing an issue as a template for recurring tasksReplicating an epic for multiple teams working on the same projectAdding a cloned task to another project’s epicSpinning up identical project templates across departmentsDuplicating a feature epic for multiple product teamsReusing standard bug triage workflows across projectsPreserving links between epics, stories, and subtasks across cloned issuesMigrating related issues into new projects without breaking issue hierarchiesBy leveraging cloning, teams can streamline processes, preserve workflow structures, and avoid unnecessary duplication.Why Jira Admins Love Epic CloneThis is where Epic Clone stands out. It transforms the way teams manage complex projects in Jira by automating the duplication of entire Epics, along with their child issues, subtasks, and dependencies. Unlike Jira’s native cloning, Epic Clone preserves project structures across multiple initiatives. Here are a few ways it makes a difference:Full Epic cloning: Clone epics with all child issues, subtasks, and linked issues intact – saving time and reducing manual efforts. Customizable cloning options: Select exactly which fields, links, and components to clone. Cross-project cloning: Duplicate epics between projects — ideal for cross-functional workflows. Bulk cloning: Save time by cloning multiple epics or issues at once Preserves Epic structures: keeps parent-child relationships intact, even across projectsSeamless integration with Jira: Built into Jira’s user interface for a hassle-free experience Ready to Do Away with Redundant Work?Epic Clone makes issue duplication effortless, maintains project structures, and streamlines workflows with ease. With flexible customization options, cloning issues in Jira minimizes errors and keeps task relationships intact. To optimize your process even further, understanding how to clone an Epic in Jira and adopting best practices for Jira are key. Stop wasting time on repetitive work and start working smarter. Try Epic Clone today! #### Automate Jira Cloning with Epic Clone’s New REST API for Issue Hierarchies We’re excited to announce a powerful new feature for Epic Clone for Jira Cloud: a cloning REST API that enables you to fully automate the cloning of issue hierarchies — from initiatives or epics down to subtasks — directly from your own tools or scripts.Whether you’re managing complex projects across multiple teams or need to create standardized issue structures on a recurring schedule, this new capability gives you the flexibility and control you need.Why a Cloning API?Until now, cloning work item hierarchies in Jira has primarily been a manual or UI-driven process. But many of our users need to:Clone predefined issue structures regularly.Trigger cloning automatically from external systems (e.g. CRM, ERP, or DevOps tools).Integrate cloning into CI/CD or workflow automation pipelines.Set up scheduled cloning jobs — e.g. to generate a monthly roadmap or team template.Our new cloning REST API makes all of that possible. What You Can Do with the Epic Clone APIHere are just a few use cases this new feature unlocks:🔁 Scheduled Cloning: Set up a job to clone a full epic hierarchy every week or month — ideal for recurring sprints, release templates, or team onboarding tasks.⚙️ Workflow Integration: Trigger a cloning operation automatically from another tool (like a project management system, form submission, or script).🔗 Cross-System Automation: Connect Jira to external systems — clone issue hierarchies when an event occurs in another platform.📦 Template Rollouts at Scale: Use the API to replicate standard project structures across teams or business units, saving hours of manual setup.You’ll find concrete examples and JSON payloads in our documentation:👉 Explore Use Cases in Our DocsUnlock the Full Power of Jira AutomationOne of the most impactful ways to use the new cloning REST API is by combining it with Jira Automation. With just a few clicks, you can create automation rules that send a web request to the Epic Clone API — triggering a full hierarchy clone based on virtually any event in Jira.Example Use Cases:🆕 Auto-Generate Templates on Issue Creation: Automatically clone a predefined epic structure when a new project, epic, or task is created.⏳ Time-Based Automation: Schedule cloning to happen at the start of each sprint or month using a time trigger.🔁 Status-Driven Workflows: Trigger cloning when an issue transitions to a certain status — e.g. “Ready for Planning” or “New Feature Request.”By combining Jira Automation with Epic Clone’s REST API, you unlock a new level of process automation — reducing manual steps, eliminating errors, and keeping teams aligned.You’re no longer limited to static templates or manual duplication — now you can create fully dynamic, rules-based cloning flows that scale with your team.👉 Learn how to send web requests from Jira Automation in the Atlassian documentation. Who Is It For?This feature is perfect for:Project managers looking to standardize their processes.DevOps engineers building automations around development lifecycle.Jira administrators seeking advanced customization options.IT and business teams who want to streamline project kickoff.No matter your role, if you rely on repeatable project structures in Jira, this API will save you time, avoid headaches, and reduce errors.Get StartedThe cloning API is available now to all Epic Clone for Jira Cloud users. You can find full API reference, payload examples, and setup instructions in our documentation:👉 Start Using the Cloning APIHave questions or need help setting it up? Our team is here to support you. Just reach out to us or book a demo. #### Epic Clone Update: Clone in Background for Faster, Smoother Jira Workflows With the latest release of Epic Clone, we’re introducing clone in background, a game-changing feature designed to streamline how you work with large Jira epics and complex issue hierarchies. Whether you’re cloning an entire initiative with dozens of child issues or duplicating large epics with multiple attachments, this update brings speed, reliability, and flexibility to your Jira experience. Clone in Background: Work Smarter, Not HarderPreviously, cloning large work items in Jira required you to keep the cloning dialog open until the operation completed. For complex hierarchies or issues with many sub-tasks and child issues, this could take several minutes—or longer—making it an inconvenient and time-consuming experience.With clone in background, that’s a thing of the past.Now you can:Start cloning large parent issues with extensive child issue hierarchiesClose the cloning dialog and continue working in Jira while cloning happens behind the scenesLet cloning operations run for up to 15 minutes in the background—fully automated, no interruptions Real-World Example: Cloning Large Work ItemsImagine you’re duplicating a feature epic that includes 50+ linked stories, sub-tasks, and test cases. In previous versions of Epic Clone, you had to wait and watch the progress dialog, unable to multitask during the operation.Now, with the clone in background feature, you can start the process, close the dialog, and immediately return to your backlog, board, or roadmap—free to focus on your next task while Epic Clone takes care of the rest. Attachment Cloning: More Stable, More ReliableWe’ve also improved how Epic Clone handles issues with numerous or oversized attachments.Before this release, cloning work items with large files could result in timeouts, stalling the operation and requiring manual intervention. Our new optimization ensures:Attachments are now cloned in parallel with the rest of the operationLarge or slow-moving attachments no longer block other cloning stepsImproved reliability and fewer timeout errors Ready to Try the New Epic Clone?These new capabilities are now available in the latest version of Epic Clone for Jira Cloud.We built this update to support busy project managers, product owners, and teams who rely on Jira to move fast and stay organized. Whether you’re scaling your work across teams or preparing templates for recurring projects, Epic Clone is now more powerful and user-friendly than ever.👉 Install or update Epic Clone from the Atlassian Marketplace to experience the new background cloning feature today. #### Essential Jira Tools and Best Practices to Boost Your Team’s Productivity Jira is a powerful project management tool that helps teams streamline workflows and improve collaboration. However, there are limitations to its ability to manage complex tasks and scale projects; challenges that the product’s native features can’t fully solve. By implementing best practices for Jira and leveraging the tools that we listed here, teams can optimize the product to work smarter, not harder.3 Significant Roadblocks to Seamless Jira WorkflowsBefore we dive into these best practices, let’s explore some of the common hurdles teams face when using Jira.#1 Poor support for non-Agile methodologiesJira is mainly designed for Agile teams, but many organizations are adopting hybrid project management methodologies. Since Jira doesn’t fully support these methods, teams are forced to utilize extra resources to create workarounds, leading to inefficiencies and inconsistencies in tracking project progress.#2 Limited decision-making supportWhile Jira provides insights into team performance and work progress, the data it generates may be insufficient for making strategic decisions. The lack of real-time forecasting and predictive analytics means that project managers must rely on external tools or manual analysis to make informed choices. This gap can lead to delays, misaligned priorities, and ineffective problem-solving.#3 No resource managementThe standard version of Jira doesn’t include built-in resource management tools. This makes it difficult for teams to allocate resources efficiently across multiple projects.Without an integrated system to monitor availability and workload, project managers often turn to external tools or manual tracking, increasing the risk of errors and adding unnecessary complexity to project planning.Epic Clone for Faster, More Efficient Project ManagementOne standout tool is Epic Clone. It doesn’t just automate the cloning of Epics; it also offers several benefits for teams working with various project structures. This includes a more user-friendly interface for duplicating entire Epics with their child issues and subtasks — functionality that would typically require custom scripts, such as those in ScriptRunner or other similar apps.In addition to simplifying the cloning process, Epic Clone:Supports non-Agile methodologies: Allows teams to retain child issue dependencies when cloning an Epic. This improves visibility into work and dependencies, making it easier to track progress and coordinate effortsEmpowers teams to make more informed decisions: A structured overview ensures better alignment and efficiency across various projectsSimplifies resource and workload management: Enables teams to replicate project structures across multiple initiatives Do also check out our resources on Epic management and cloning issues in Jira for in-depth guidance on optimizing project workflows and your team productivity. Maximizing Efficiency with Automation and Best Practices for JiraJira’s automation features help teams work more efficiently by assigning tasks, sending notifications, and updating statuses automatically. Boards like Scrum, Kanban, and Mixed improve project visibility while reporting tools identify bottlenecks and optimize performance.Collaboration is also easier with built-in chat and commenting, ensuring clear communication. Additionally, feedback collection helps teams refine workflows over time.Integrating external tools makes Jira even more powerful. Teams can boost efficiency across projects by generating advanced reports, customizing field visibility, connecting third-party apps, and automating repetitive tasks.Epic Clone is just the beginning. Several other powerful tools can supercharge Jira’s functionality, including:Project and resource managementPlanyway is used for scheduling and time tracking, BigPicture for Gantt charts and roadmaps, and Structure for the hierarchical organization of issues.Reporting and analyticseazyBI Reports and Charts enable advanced data analysis and the creation of customized dashboards.Workflow automation and customizationScriptrunner automates tasks with Groovy scripts, and Automation for Jira paves the way for no-code workflow management.Test management and quality assuranceZephyr integrates test management directly within Jira, making it ideal if testing is part of your app flow.Asset and configuration managementAssets simplifies asset tracking and configuration management within Jira.Unlocking Jira’s Full Potential with the Right ToolsOptimizing productivity in Jira requires leveraging the right tools. Epic Clone streamlines issue management, supports non-Agile workflows, and enhances workload visibility. When combined with additional productivity tools, it ensures efficient project execution and informed decision-making. Don’t wait — transform your project management experience and maximize efficiency with these best practices for Jira today! #### How Custom Forge Apps Transform Jira Workflows for Enterprise Why Marketplace Apps Can't Solve Enterprise ProblemsYour enterprise workflows are unique. So why settle for generic solutions?The truth is that standard Atlassian Forge apps serve roughly 80% of most organizations' needs, but enterprise success lives entirely in that remaining 20%. Marketplace apps are built for the masses; designed to satisfy common denominators across thousands of organizations.These generic apps force your unique processes into predetermined boxes, creating friction where you need flow, complexity where you need simplicity. When workflow efficiency becomes your competitive edge, custom apps become essential. 3 Ways Custom Apps Drive Major Efficiency GainsNow, let’s check out three ways how custom apps built on Atlassian Forge can bring magic to your organization's efficiency: 1. Automated, Workflow-Specific ActionsComplex business processes get automated end-to-end. Think IT service requests that route themselves, bulk project setup that happens in minutes instead of days, and compliance workflows that never miss a step. Without automation via custom apps, teams waste their time on repetitive manual processes that competitors may have already automated. Take our Epic Clone app, for instance. It removes manual project recreation entirely. What previously consumed days now takes minutes. The ROI impact? Teams redirect their focus from mind-numbing repetitive tasks to strategic work that moves the needle.2. Seamless Tool Integration & Data SynchronizationOrganizations stuck with generic solutions face constant data inconsistencies, creating bottlenecks that slow decision-making and erode stakeholder confidence. Real-time, bidirectional data flows between Atlassian and your enterprise systems create something magical: information that stays accurate without human intervention. Cross-platform automation connects HR systems, CRMs, and analytics platforms, eliminating duplicate data entry while ensuring information accuracy across your entire tech stack.No more spreadsheet reconciliation nightmares. No more "wait, which system has the latest version?"3. Custom UI & Reporting for Business InsightsGeneric reporting tools force executives to make strategic decisions with incomplete or irrelevant data, putting your competitive advantage at risk when agile competitors are acting on real-time insights.Actionable dashboards surface directly within Jira and Confluence, displaying exactly the metrics that matter to your decision-making processes. Advanced reporting tailored to your specific KPIs provides real-time visibility into priorities, blockers, and operational metrics that generic solutions simply can't deliver.Check out this hypothetical scenario of how a global consulting firm could transform its client onboarding process using a custom app:Example Scenario: Global Consulting Firm's Client Onboarding ProcessThe Challenge: Each new enterprise client demanded creating complex project structures with 150+ interconnected tasks across multiple teams, which is a logistical nightmare.Manual Process: If done manually, it will require three full days per client to recreate project hierarchies and assign resources.Custom Solution: The solution is through a custom Forge app connecting Jira with CRM and HR systems for automated project generation.Results Achieved:Client setup time: 3 days → 30 minutes per new engagement.Resource allocation: Automatic team assignment based on skills and availability from the HR system.Revenue acceleration: Faster project starts increased billable hours by 15%.Client satisfaction: Reduced onboarding delays, improved Net Promoter Score by 12 points. Competitive Advantages: Faster client engagement: Begin billable work immediately after contract signing.Resource optimization: Automatic skill-based team assignments remove bottlenecks.Scalability advantage: Handle 3x more simultaneous client onboardings without additional overhead.Quality consistency: Standardized processes ensure no critical steps are missed.When You Need Custom Apps Instead of Standard SolutionsHere's when custom Forge apps transform Jira workflows from functional to game-changing:Scenario 1: Complex Organization-Specific WorkflowsMulti-level operations require custom field mapping and cross-project coordination that goes far beyond marketplace capabilities. Picture this: a custom solution using our Epic Clone app that automatically triggers bulk cloning of entire product launch templates across global regions after specific workflow transitions. Using our app, you can clone epics or even initiatives together with their child issues. But here's the kicker: we customized the app further by integrating with regional compliance requirements and local team structures in ways that standard cloning simply can't touch.Scenario 2: Cross-System Integration RequirementsReal-time data synchronization between Atlassian and your enterprise systems demands precision. We've built custom integrations connecting specialized HR systems with our User Absence Planner app, automatically updating team availability based on leave requests, training schedules, and skills certifications.Another example? We created a tailored migration solution that moved work items from Azure DevOps to Jira, specifically configured for unique field mappings and workflow states. Months of manual migration work became days of automated precision.Scenario 3: Advanced Project Management NeedsBeyond standard milestone tracking, we can customize our Project Milestones app to synchronize directly with your company's OKR definitions and tracking systems. This creates dynamic dependency visualizations that adapt to changing business priorities and automatically escalate risks based on your specific business rules.Your milestones become living connections to strategic objectives, not just project checkpoints.Why You Need Expert Forge DevelopersThe expertise gap is real. Custom Atlassian Forge development demands specialized knowledge that most internal teams simply don't possess:Risk mitigation: Professional development prevents costly mistakes and ensures scalability from day one.Time-to-value: Expert teams deliver solutions 3x faster than internal development efforts.Ongoing optimization: Continuous improvement based on usage patterns and business evolution.Deep expertise: Understanding what Atlassian Forge truly offers, planning legacy app rebuilds, and designing scalable Atlassian architecture.At ij-solutions, we bring years of specialized Forge development experience, helping enterprises transform their Atlassian workflows without the learning curve or implementation risks.Curious whether a custom Forge app could transform your team's work? Let ij-solutions show you what's possible and help you unlock enterprise-grade workflow automation. #### How to Avoid Jira Bulk Clone Errors and Preserve Issue Relationships Bulk cloning in Jira is supposed to save time. In reality, it often creates extra work.Imagine cloning an epic with 50 user stories for an upcoming sprint — only to realize every issue now starts with “CLONE –”, links are broken, and subtasks are detached. Or worse, you’re trying to replicate a multi-level Jira hierarchy across teams and discover Jira can’t reliably preserve epic–story–subtask relationships.At ij-solutions, we work with Jira admins and enterprise teams who face these problems daily. The challenge isn’t cloning issues — it’s maintaining structure, relationships, and data integrity at scale. Jira’s Native Cloning: What It Can and Can’t DoAtlassian has improved Jira’s native cloning capabilities, especially with the introduction of epic cloning that includes child issues.What Jira handles well:Cloning single issues with most standard fields and attachmentsCloning epics with their direct child storiesBasic parent–child relationships in simple hierarchiesWhere native Jira cloning breaks down:Multi-level hierarchies beyond two levels are not preservedCross-project cloning breaks issue relationshipsNo control over cloned issue naming (e.g. forced “CLONE –” prefixes when configured in the entire instance)No customization for field mapping during cloningSignificant manual cleanup required after every bulk operationFor teams managing complex Jira projects, these limitations quickly become blockers. Common Jira Bulk Cloning ProblemsTeams attempting bulk cloning in Jira typically run into the same issues:Epic–story–subtask hierarchies disappear, leaving orphaned issuesIssue links are lost, including blockers, dependencies, and “relates to” linksCustom fields copy inconsistently, forcing manual verificationSprint planning and tracking suffer due to broken relationshipsThe result is increased administrative overhead and reduced delivery speed. 3 Common Workarounds — and Why They Don’t ScaleMost Jira teams rely on one of these approaches:1. CSV Export and ImportUseful for simple duplication, but it removes all relationships, comments, and attachments. Rebuilding links manually is time-consuming and error-prone.2. Jira Automation RulesAutomation can create issues from templates, but it struggles with multi-level hierarchies, consumes execution limits, and becomes difficult to maintain as projects evolve.3. Manual Cloning with CleanupCloning issues one by one and fixing names and links manually works in theory — but doesn’t scale. Performance issues and human error quickly creep in.None of these approaches reliably preserve complex issue relationships during bulk cloning. How Epic Clone Solves Jira Bulk Cloning at ScaleSpecialized Jira apps like Epic Clone are designed to handle the gaps left by native Jira cloning.Advanced hierarchy cloning Epic Clone allows you to clone entire epics with multi-level hierarchies in a single operation. Epic–story–subtask relationships and issue links are preserved automatically.Automation-ready cloning With Epic Clone’s REST API, cloning can be triggered via Jira Automation rules, schedules, or external systems — enabling repeatable and controlled workflows.Enterprise-ready features Background cloning for large datasets (up to 15 minutes)Cross-project cloning with field adjustments (assignee, components, fix versions, estimations)Permission controls for governance and complianceBuilt on Atlassian Forge, ensuring data never leaves your Jira instanceRuns on Atlassian certified When to Use Native Jira Cloning vs. an AppUse native Jira cloning for simple, same-project duplication with minimal hierarchy and acceptable manual cleanup.Use Epic Clone when you need to preserve issue relationships, clone across projects, automate processes, or scale Jira usage across teams.Want to clone Jira issues without breaking hierarchies or spending hours on cleanup?👉 Try Epic Clone and experience reliable Jira bulk cloning. #### ij-solutions Security Advisory 2025-001 SummaryTwo security vulnerabilities were identified in the app User Absence Planner for Jira Data Center that could allow unauthorized modification of administrative settings and the injection of malicious scripts into user-generated content. These issues have been fully resolved.Affected ProductApp: User Absence Planner for Jira Data CenterAffected Versions: All versions prior to 1.9.0Fixed Version: 1.9.0Vulnerability Details1. Insufficient Permission Check on Admin Settings EndpointA backend endpoint intended for system administrators did not correctly verify permissions. Under specific conditions, a regular user could access the endpoint and modify administrative configuration data.2. Stored Cross-Site Scripting (XSS) in User-provided Input FieldsUser-provided input in absence fields was not fully sanitized, which could allow malicious script injection and execution in certain views.Please note: No exploit instructions or proof-of-concept details are provided, in accordance with Atlassian’s security disclosure guidelines.Severityij-solutions has assessed these vulnerabilities as High severity based on potential impact and Atlassian’s guidance.RemediationAll customers should upgrade to version 1.9.0 or later as soon as possible.Version 1.9.0 includes complete fixes for both vulnerabilities.If your instance cannot be upgraded immediately, we recommend restricting access to administrative functionality and monitoring logs for suspicious requests until the upgrade can be performed.Disclosure TimelineDateEvent24-10-2025Vulnerabilities reported to ij-solutions29-10-2025Investigation and validation completed30-10-2025Version 1.9.0 released with security fixes07-12-2025Public disclosure of this advisoryContactIf you have questions or need assistance upgrading, please contact our support team:support@ij-solutions.atlassian.net #### Introducing Bulk Cloning via JQL in Epic Clone – A Major Leap for Teams in Jira At ij-solutions, we are committed to helping teams work smarter inside Jira. Today we’re excited to announce one of the most anticipated enhancements to our Epic Clone app: bulk cloning based on a JQL search. This new capability marks a significant milestone, enabling users to replicate large sets of Jira items faster, more accurately, and with fewer manual steps.Why This MattersCloning multiple issues in Jira has long been a repetitive and time-consuming task—especially when you need to clone items matching specific criteria. With this update, teams can now harness the full power of JQL search to filter, select, and bulk clone items with precision. Whether you’re managing templates, repeating sprint structures, or replicating large backlogs, this is a genuine productivity boost. Using JQL search in the Item Navigator to select items for bulk cloning This screenshot illustrates how easy it is to target the exact items you want to clone. With a single JQL query, teams can surface the full hierarchy of relevant issues and immediately prepare them for cloning.A Closer Look at the New FeatureBefore exploring the individual capabilities, it’s helpful to see how the new bulk cloning interface comes together. Bulk cloning configuration screen in Epic Clone The interface gives you a clear overview of the selected issues, all derived directly from your JQL results. From here, you can fine-tune how the cloned items behave, what is included, and how the hierarchy is preserved.Feature Highlights: How Bulk Cloning via JQL WorksThis update introduces several enhancements designed to make Jira item cloning more intuitive and efficient.1. Clone Issues Directly from Any JQL SearchRun any JQL query—simple or complex—to instantly filter the items you want to clone. This may include epics, stories, sub-tasks, or mixed issue types.2. Hierarchical Preview With Load-More SupportYou can browse the full item structure, preview up to 50 items at a time, and load additional items for very large clone sets. Previewing issue hierarchy and loading additional items before cloning 3. Cross-Space Cloning OptionsClone items within the same space or into a completely different one — a powerful capability for teams working across multiple Jira spaces.4. Summary Modification ToolsUse find & replace, prefixes, and suffixes to instantly adapt item summaries to the new context. Editing summaries with find & replace, prefix, or suffix options 5. Drag-and-Drop Hierarchy AdjustmentsEasily reorder, re-parent, or restructure cloned items before executing the clone.These improvements work together to ensure that even complex cloning operations stay manageable, visible, and adaptable.Real-World Use CasesTo demonstrate the power of bulk cloning based on JQL, here are common scenarios where teams benefit most:Repeatable Sprint or Release StructuresTeams using template epics or templated sprint setups can now clone entire structures through a simple JQL query.Large-Scale Project RolloutsOrganizations can replicate full work item sets into multiple projects without doing that manually or conducting one-by-one clones of epics.Backlog Replication Across TeamsUse a JQL query such as:project = ABC AND labels = "campaign" AND issuetype = Story…and instantly clone the whole campaign backlog into another teams space.Parallel Work BranchingTeams that need a separate set of items for branching or testing can duplicate issues cleanly while maintaining structure. Hierarchy preserved during JQL-based bulk cloning in Epic Clone This visual breakdown makes it clear how Epic Clone preserves the full hierarchy across all cloning operations.Tips for Getting the Best ResultsWhile the new cloning engine is designed to be intuitive, a few best practices can further improve your experience:Craft precise JQL queries to ensure you’re cloning exactly the issues you intend.Preview the full list using the load-more option when working with large datasets.Use prefix/suffix modifiers to label cloned items for new sprints, versions, or projects.Decide your linking strategy—whether to keep links to original items or create independent clones.With these recommendations, you can make the most out of JQL-driven cloning and streamline your workflows even further.How to Get StartedUpdate Epic Clone to the latest version (only necessary if you are running on an outdated major version).Open the Item NavigatorEnter your JQL search to define your clone set.Open Apps → Bulk Clone.Select the target space.Configure cloning settings (attachments, links, summary editing).Review the structure.Click Clone and let the app handle the rest. Ready to Speed Up Your Jira Workflow?The introduction of bulk cloning via JQL in Epic Clone is a major step forward for teams that manage structured, repeatable workflows. By combining powerful search filtering with flexible cloning options, Jira teams can now work faster, cleaner, and more consistently than ever before. Try Epic Clone free today to take advantage. #### Introducing Projects Insight Edge: Your Comprehensive Jira Project Analysis Tool We are thrilled to unveil Projects Insight Edge, the all-in-one solution for Jira project management, now available on the Atlassian Marketplace. Developed during the prestigious Codegeist hackathon, this ultimate tool earned a bonus prize in the “Runs on Atlassian” category, proving its value and innovation.With Project Insight Edge, Jira users gain unprecedented visibility into their entire Jira project landscape, providing analytics and insights that go beyond Jira’s default reporting capabilities.Why We Built Projects Insight Edge – Lack of A Comprehensive Overview of All Jira Projects with Relevant KPIsJira users often struggle with fragmented project data, lacking a Jira project report that consolidates key performance indicators (KPIs) across all projects. While Jira provides a list of all accessible projects, it lacks detailed insights into critical data such as issue counts, user access, and project status. We created Project Insight Edge to eliminate that hassle and provide a comprehensive overview of health, status, and progress across all Jira projects. Many users resort to manually creating complex filters and dashboards to extract this information. Recognizing the need for an out-of-the-box solution, we set out to create an app that aggregates data from all Jira projects into a single, comprehensive report. Our goal was to empower users with the ability to make data-driven, strategic decisions without the hassle of manual data compilation.How Project Insight Edge Transforms Jira Project Management – Insight Into All Projects at a Glance!Managing multiple Jira projects efficiently requires real-time insights and comprehensive reporting. Our tool delivers exactly that, empowering teams to make informed decisions, optimize workflows, and improve project outcomes. Project Insight Edge aggregates a unified view of project data, such as issue counts, user access, and project status, into a single, easy-to-navigate dashboard. Whether you're managing a few projects or hundreds, this app is your go-to solution for tracking project health and identifying areas for improvement.Stay tuned as we delve deeper into the features and benefits of Projects Insight Edge, and explore how it can transform your Jira experience.Features and Benefits of Projects Insight EdgeKey Features:Insights Dashboard: This feature provides a comprehensive analysis of all Jira projects accessible to the user. It includes key metrics such as:Total number of issues (globally and per project)Number of users with project accessIssue status category breakdown (To Do, In Progress, Done)Percentage of unresolved, unassigned, and overdue issuesQuality issues percentagePIE Score (Projects Insight Edge Score), an aggregation of several metrics to reflect project health.Insights History: Users can track saved analyses over time, allowing them to evaluate trends and the effectiveness of implemented actions. Data is presented in both table and chart formats for easy visualization.Admin Settings: Provides Jira administrators with full control over app configurations, including user access, metric thresholds, and scheduled analyses. This ensures that the app can be tailored to meet specific organizational needs.Scheduled Analysis: Automates data collection with daily or weekly scheduled analyses, ensuring consistent monitoring without manual intervention.Rovo Agent: Offers deeper insights and actionable recommendations, enhancing the app's standard functionality by providing explanations on metric calculations and improvement suggestions. User Benefits from Projects Insight EdgeComprehensive Project Overview: Users gain a holistic view of their project landscape, enabling data-driven decision-making and improved project outcomes.Actionable Insights: The app provides recommendations for metrics with low or average performance, helping users to take corrective actions.Trend Analysis: By saving and comparing analysis results over time, users can identify trends and measure the impact of their strategic decisions.Enhanced Security and Control: With admin settings, organizations can ensure that project data remains protected and accessible only to authorized users.Projects Insight Edge is designed to empower Jira users with the insights needed to optimize project management and drive success. Real-World Applications of Projects Insight EdgeWho Benefits from Project Insight Edge?This tool is designed for a wide range of Jira users, including: Project Managers: Gain a 360-degree view of your Jira project health, track progress, and identify areas of improvement Team Leads: Monitor team performance, identify bottlenecks, and optimize task allocationJira Administrators: Configure and maintain Jira environment and simply project data analysis while ensuring compliance with internal policies.  Business Analysts: Use historical insights and recommendations to develop data-driven strategies Practical Applications:Project Health Monitoring: Using the PIE Score, project managers can instantly assess the overall health of their projects, which aggregates various metrics into a single, actionable score. This helps in identifying projects that require immediate attention.Resource Allocation: To ensure workloads are evenly distributed to prevent bottlenecks and improve efficiency, team leads can analyze user access and issue distribution across projectsTrend Analysis: Utilize the Insight History feature to track project metrics over time, identify trends, and measure the impact of strategic decisions. This data-driven approach supports continuous improvement in Jira project management.Automated Reporting: Keep stakeholders informed with automated scheduled reporting, reducing manual effort. This feature is particularly useful for organizations with a large number of projects, as it saves time and reduces the risk of oversight.Security and Compliance: Maintain control over access settings, ensuring sensitive project data remains protected. These use cases demonstrate how Projects Insight Edge can be a valuable tool for enhancing project management and strategic planning within Jira environments. Getting Started with Projects Insight EdgeInstallation GuideTo install the app from the Atlassian Marketplace in your Jira instance, follow these steps:Access the Marketplace: In your Jira instance, navigate to the top menu and click on Apps, then select Explore more apps.Search for the App: Use the search bar to find the app ‘Projects Insight Edge’. Select it from the search results.Start the Installation: Click on Try it free to start a free trial of the app.Install the App: Follow the on-screen instructions to complete the installation process. Once installed, a confirmation message will appear, indicating that the app has been added to your Jira instance.Post-Installation Configuration: There is no mandatory post-installation configuration for Projects Insight Edge. However, you can check the admin settings page for settings you can apply there. Based on your preferences and the environment you are working in, you can define permissions, metrics thresholds, and scheduled analysis intervals there. For more information, check our documentation.By following these steps, you can successfully install and configure the app from the Marketplace in your Jira instance.Configuration Tips for Post-Installation ConfigurationHere are some configuration tips for setting up Projects Insight Edge after installation:Access Settings:Purpose: Control who can access and use the app.Configuration: Set access permissions by group or individual user. Restrict access to only those users or groups who need to use the app, ensuring that project analyses by the app are only available to authorized personnel. Please note that the access settings for the Jira projects and their issues is always respected, and users won’t be able to see issues via the app that they don’t see in Jira.Statistics Settings:Purpose: Customize the thresholds and weighting for project metrics.Configuration: Define thresholds for low, medium, and high values for various metrics displayed on the analysis dashboard. Adjust the importance of each metric by setting the weighting for the PIE score calculation. This customization allows the app to reflect the specific priorities and characteristics of your Jira instance and organization.Project Settings:Purpose: Specify which issue types are considered quality issues.Configuration: Define quality issues globally for the entire instance or customize them per project. This flexibility ensures that the app aligns with your organization's definition of quality issues, allowing for more accurate project health assessments.Scheduled Analysis Settings:Purpose: Automate regular analyses to track project performance over time.Configuration: Enable scheduled analyses to run at regular intervals, such as daily or weekly. This ensures consistent monitoring and historical data collection, allowing for trend analysis and strategic planning.By configuring these settings, administrators can tailor the Projects Insight Edge app to better fit their organization's needs, enhancing its effectiveness in monitoring and improving project health. Community Engagement: Help Shape the Future of Projects Insight EdgeAt ij-solutions, we value your feedback–it’s essential to the continuous improvement of our apps. Your insights help us refine Projects Insight Edge, ensuring it meets your needs and enhances your Jira project management experience. We invite you to share your thoughts–whether it’s your experience using the app, feature suggestions, or any challenges you’ve encountered. Your input directly influences future updates, making the app even more powerful and user-friendly. How to share your feedback:Raise a support request: ij-solutions help centerContact us via email: info@ij-solutions.comContact form on website: ij-solutions.com/contact-us Start Your Trial TodayExperience the full potential of Project Insight Edge, now available on the Atlassian Marketplace. This app gives you a comprehensive Jira project landscape and report, empowering you to make data-driven decisions with ease. Whether you’re a project manager, team lead, or business analyst, you’ll gain valuable insights to optimize your workflow. From the Insights Dashboard to the Rovo Agent's actionable recommendations, the app is designed to help you stay ahead.We’d love to hear about your experience—your feedback helps us enhance the app to better serve your needs. Try Projects Insight Edge today and take your Jira project management to the next level!For support or further inquiries, please feel free to reach out to us. We are here to assist you in making the most of your Jira projects with Projects Insight Edge. #### IT Service Request Management Made Easy with Workflow Automation In any organization, an IT service request is a regular part of daily operations. Whether it's setting up new hardware, granting software access, or handling password resets, these essential tasks can quickly pile up, especially when created manually.While these tasks are important, they’re also time-consuming and prone to human error. Without automation, even the simplest request can quickly snowball into an administrative burden. Let’s explore how tools like Epic Clone can change that. Common IT Service Request Challenges Faced by TeamsAs organizations grow, so does the number of incoming service requests. While each request may seem simple on its own, the reality is that:The same processes are repeated for similar requestsImportant steps are sometimes overlookedDeadlines may be missedVisibility over the progress of different projects can be lost The result? Fragmented workflows and miscommunication across departments. A Smarter Way to Manage IT Service RequestsInstead of building everything from scratch, teams can create a template Work Item for recurring tasks, then duplicate that Work Item whenever needed using tools such as Epic Clone.Let’s use new hire onboarding as a practical example. This process often includes:Setting up email accessCreating VPN credentialsProvisioning hardwareScheduling security briefingsAdding software licenses Managing all these activities requires a structured approach. Epic Clone helps IT teams manage complex service work structures in Jira by replicating entire work structure – Epics, Stories, Tasks, and Subtasks, while preserving their relationship, due dates, and assignees. Although this structure originates from software development, it can easily be adapted into other sectors like service management or operations. For instance, IT teams may use Epics, Stories, and Tasks to group and manage work based on business priorities, service requests, or ongoing operational needs. To make execution even more manageable, both Stories and Tasks can be broken down into Subtasks, allowing teams to assign specific actions and track detailed progress.Here’s an example in Jira:An Epic represents a major initiative, like New Hire OnboardingStories outline user-focused deliverables, such as Setting up accounts and accessTasks cover operational activities like Provisioning hardware or Scheduling security briefingsSubtasks break down detailed steps, like Creating email credentials or Installing software Jira’s native clone function can handle single tasks, but it isn’t capable of dealing with complex, recurring service requests. Here's how Epic Clone goes a step further: Unlike Jira’s native clone, with which you can only copy one issue at a time, it duplicates the entire Work Item with all linked Requirements, Tasks, and Subtasks at onceJira doesn’t maintain issue links or hierarchy, whereas Epic Clone ensures that dependencies and workflows remain intact It lets you adjust fields like assignees, due dates, and Original estimate during cloning, something Jira’s default clone can’t doIt saves time and reduces the chance of errors by replicating full structures, including relationships and assignmentsIt scales effortlessly, something Jira’s basic clone isn’t built for Here’s a basic setup IT teams can follow:Set up a template structure for recurring Tasks, such as user onboarding or server setupStore the template either in the same project or in a dedicated template projectClone the template whenever needed and assign Tasks to the responsible colleagues during cloning To get the best results, it’s also advisable to:Monitor and review each cloned Work Item structure to ensure accuracyTest on a small scale before implementing it fullyUpdate templates regularly to abide by the latest best practices and standards Adopting this structured and proactive approach enables IT teams to lay the groundwork for smoother, more consistent service delivery. Unlock Long-Term Benefits with Epic CloneOver time, they may find themselves enjoying several benefits that go beyond simple task duplication:Automated duplication and consistency: Clone entire Work Items while preserving hierarchy and structure Maintain critical relationships: Retain issue links and dependencies to track progress more effectivelyCustomize as you go: Adjust fields such as assignees, due dates, and Original estimate during the cloning processEfficient project setup: Replicate successful work item structures instantly and reduce the time spent on managing requestsScalable processes: Maintain a uniform approach across multiple projects as request volume growsSmarter resource planning: Duplicate pre-assigned tasks and resource allocations to simplify work distribution and prevent bottlenecks Bring Order to IT Teams with Repeatable WorkflowsIn Jira, workflows is a marker of how each request moves from start to finish. While Epic Clone doesn’t replicate the workflows themselves, it enables IT teams to optimize their business processes and to do more than just copying tasks; it allows them to clone entire work structures, including field values, relationships, and assignments.This is especially helpful when handling recurring IT services like onboarding, software rollouts, or equipment requests. Instead of building workflows from scratch each time, IT teams can streamline operations and focus on delivering quality service:Automate standard requests: Ensure that essential steps like account creation or security access are always includedPreserve issue relationships: Track dependencies between Tasks and Action Items with easeEnhance incident resolution: Apply predefined workflows across similar incidentsBalance team workload: Avoid overloading your service desk by replicating Work Items with pre-assigned resourcesStandardize IT project rollouts: Whether you're conducting system upgrades or compliance audits, Epic Clone keeps your workflows efficient and reduces setup errors As teams continue to support evolving business needs, the ability to scale, standardize, and streamline IT service request management becomes increasingly critical. That’s why it’s time to start operating smarter and faster. Empower your organization with Epic Clone today and transform the way you manage service requests in Jira. #### Jira Epics Made Easy: Clone Smarter & Avoid These 4 Pitfalls As a Jira admin or project manager, managing Epics can be complex, especially when duplicating child issues, subtasks, and dependencies. Breaking them down helps track progress, but speed and precision are key. This is why knowing how to clone an Epic in Jira efficiently is essential for keeping workflows smooth and projects on track. By mastering this, teams can reduce repetitive work and focus on execution rather than manual setup. This matters for two key reasons. First, it empowers project managers to set clear priorities and ensure that tasks are completed in a structured manner. Second, it fosters a culture of continuous improvement by empowering teams to regularly review completed tasks and refine their processes.4 Risks of Managing Epics Without AutomationOn the contrary, manual data entry can do more harm than good, especially without the right tools. Below are some of the key challenges teams face when managing Epics manually.1 – Inconsistent Issue Relationships and Missing DependenciesThe first big hurdle teams must overcome is maintaining consistency across issues. As projects expand, tracking multiple Epics and their related stories becomes increasingly difficult.Without a structured approach, teams can lose track of progress and dependencies. The result? What started as a well-planned project can easily spiral into chaos and confusion.2 – Time-Draining Manual Project SetupManually setting up repeated workflows is another major challenge. Recreating similar projects from scratch causes teams to lose valuable time that could be better spent on execution.Meanwhile, correctly prioritizing tasks and properly establishing dependencies can become overwhelming, especially when managing multiple projects simultaneously.3 – Scaling Agile Becomes a HeadacheThese problems are further amplified when scaling Agile practices across teams. While Agile works well for small, focused teams, larger enterprises may struggle with coordination. As teams grow, communication gaps widen, leading to lost, miscommunicated, or misunderstood information.Traditional organizations with rigid hierarchies may clash with Agile’s fast and flexible approach. Thus, striking a balance between agility and governance can be difficult, especially as projects scale.  Successfully implementing Agile practices in an enterprise requires more than just process changes. Each team member must have a clear understanding of Agile principles, while project leaders must be well-equipped to guide teams effectively.4 – Human Errors Multiply with Every Manual CloneThe right tools are crucial for maintaining alignment and efficiency. Without proper tracking, integration, and testing tools, keeping multiple teams synchronized while maintaining speed becomes nearly impossible.    To make matters worse, cloning an Epic manually means copying every child issue, subtask, and linked item one by one. This isn’t just tedious; it also increases the risk of mistakes. The bigger the project, the more time and resources are wasted on tasks that could be automated.Smarter Workflow Management with Epic CloneEpic Clone by ij-solutions provides a comprehensive solution to these challenges by seamlessly integrating into Jira’s native user interface. For example, it allows users to easily clone an Epic with issues in Jira, eliminating the need to recreate dependencies manually. If you’re new to managing Epics, consider reviewing our guide to cloning an issue in Jira for additional insights. Automation also plays a key role in saving time. Instead of manually setting up stories and tasks, teams can instantly replicate entire Epics, reducing effort and accelerating project setup. They may also use this guide on best practices in Jira to enhance their team’s productivity. Likewise, for teams handling repeated workflows, Epic Clone makes planning easier by retaining resource allocations, making workload management more efficient.Optimize Resource Allocation by Learning How to Clone an Epic in Jira TodayManaging Epics in Jira doesn't have to be overwhelming. With the right tools, teams can streamline workflows, maintain consistency, and scale Agile practices seamlessly. Don’t let repetitive tasks bog your team down. Equip them with the ability to clone an Epic in Jira so they can focus on what truly matters: delivering impactful results. Ready to transform your Jira experience? Try Epic Clone today. #### Jira for Marketing Teams: How Epic Clone Boosts Workflow Efficiency Marketing is the heartbeat of any business plan. It’s what connects your brand with the people who need the products or services you offer. However, many organizations fall into the trap of treating marketing as a one-off campaign instead of a continuous process. The good news? Tools like Jira for marketing projects are transforming how teams operate.Why? Modern marketing has become more complex than ever. It’s no longer just about coming up with a good idea; it’s about coordinating cross-functional teams, hitting deadlines, managing content production, securing stakeholder approvals, and tracking performance metrics across multiple channels.However, while Jira helps bring structure to the chaos, it still has its limits, especially when teams choose to rebuild their campaigns from scratch.Challenges of Manual Marketing Campaign ManagementRecreating the same work item structures manually might seem harmless at first, but it can be costly in the long run. Here are a few potential challenges teams may face:Operational delays that make it harder to respond quickly to changing circumstancesSecurity risks due to mishandling or sharing sensitive campaign data with unauthorized personnelIncreased human errors caused by fatigue, leading to inconsistent outputs and subpar campaign executionFormatting and structure issues that complicate reporting and collaboration If not addressed early, these inefficiencies tend to multiply, especially as teams grow or manage multiple projects simultaneously. Simplifying Marketing Campaigns with Epic CloneBuilt for teams using Jira for marketing projects, Epic Clone is a powerful tool that’s designed to address these exact pain points.Unlike Jira’s default clone, which only copies individual issues without preserving relationships, Epic Clone allows marketing teams to duplicate complex Work Items with just one click. That includes all linked Stories, Tasks, and Subtasks, while maintaining their structure and hierarchy.This framework, which is commonly seen in software development teams, can be just as valuable in marketing, operations, and other non-technical teams that manage complex workstreams. For example, in Jira:An Epic represents a major initiative, a large body of work that needs to be broken down into smaller, more manageable pieces. Example “Product Launch Campaign”Stories break this down into key specific deliverables, such as “Content Creation” or “Email Strategy.”Tasks are similar in size to Stories, but tend to focus on technical and operational activities such as “Asset Requests” or “Team Coordination.” Both Stories and Tasks can be further broken down into Subtasks, which represent the most detailed steps needed, such as “Writing Blog Copy” or “Designing Visuals.” Need to make tweaks? The tool lets you review and customize fields before cloning. A quick way to do this is to replace and bulk edit options or placeholders.For projects that don’t require any changes, the Quick Clone feature enables instant replication of hierarchical Work Items and all their child issues while preserving hierarchy and structure.Let’s say a marketing team is launching a new project in the next quarter. The campaign typically includes:A product briefCopywriting tasks for email and landing pagesDesign requests for banners and adsSocial media schedulingInternal approvals and feedback loops With Epic Clone, there’s no need to recreate the same tasks every time. The team only needs to:Clone the previous launch Work Item Update campaign-specific details like launch dates, new assets, and copy Assign campaign tasks to designated team members during cloning Kick off the campaign Unlocking Efficiency, Consistency, and ScalabilityOver time, Epic Clone helps marketing teams unlock key benefits that elevate their campaign management, including:Automate and maintain consistency across campaigns: Ensure a consistent setup across every campaign, save time, and reduce manual errorsPreserve hierarchy and relationships: Gain better visibility over dependencies and track progress effectivelyCustomize fields during cloning: Start every new project with accurate and relevant detailsAccelerate campaign setup: Spend less time on configurations and more on creative strategyScale efficiently across multiple projects: Apply workflows across various campaigns while maintaining standardizationOptimize resource allocation: Plan smarter and avoid common bottlenecks across concurrent campaigns Enhancing Workflow Accuracy in Teams Using Jira for MarketingIn Jira, workflows define how issues progress from start to finish. While Epic Clone doesn’t duplicate the workflows themselves, it allows marketing teams to replicate entire work item structures, complete with all related tasks, due dates, and assigned responsibilities.More importantly, replicating proven structures reinforces accountability. By maintaining built-in checkpoints and assigning roles, everyone knows exactly what to do and when to do it.With Epic Clone, high-performing teams using Jira for marketing projects can turn their most effective campaign workflows into repeatable systems that save time, reduce errors, and deliver faster results. Don’t just run campaigns. Operate with confidence. Try Epic Clone today. #### Jira Integrations Explained: Automation, Marketplace Apps, or a Custom Forge App — Which One Is Right for You? When you need to connect Jira with another system — whether that's syncing issues from Azure DevOps, pulling data from a CRM, or migrating an entire project history — you have three main options: Jira Automation, a third-party Marketplace app, or a custom-built Forge app. Each approach works well in the right situation and falls short in the wrong one. This post explains how they compare and how to choose.What does "integrating Jira with another system" actually mean?A Jira integration is any setup that lets Jira exchange data with an external tool — creating issues based on events in another system, syncing status updates, migrating historical records, or triggering actions across platforms. The complexity ranges from a simple webhook to a fully bidirectional synchronisation that keeps two live systems aligned in real time.The right approach depends on three factors: how complex your workflow logic is, how much control you need over field mapping and data transformation, and whether the integration needs to be maintained long-term or is a one-time migration.Option 1: Jira Automation Jira Automation is the built-in rules engine available on all Jira Cloud plans. It lets you trigger actions — creating issues, updating fields, sending notifications — based on events inside Jira or from external sources via webhooks. An Automation rule can be triggered by calling a webhook, but also send web requests as an Automation action Where it works well:Lightweight, event-driven triggers (e.g. "when an issue is created in Project A, create a linked issue in Project B")Notifications to external systems like Slack or emailSimple field updates triggered by status changesWhere it hits its limits:Jira Automation is not designed for complex integrations with external systems. It has no persistent state, meaning it cannot handle multi-step synchronisation logic that depends on what happened in a previous run. Webhook payloads from external systems need to match a specific structure, and transforming or filtering that data inside Automation rules is awkward at best. Rate limits also apply — on high-volume projects, rules can queue or fail silently.If your integration requires conditional field mapping, bidirectional sync, error handling, or any meaningful transformation of incoming data, Automation alone will not be enough.Option 2: Marketplace AppsThe Atlassian Marketplace has several apps built specifically for system integrations — tools like Exalate, Backbone Issue Sync, and ZigiOps cover common use cases such as Jira-to-Jira sync, Jira-to-ServiceNow, and cross-company collaboration.Where they work well:Standard integration patterns between widely-used systemsTeams that need something running quickly without custom developmentScenarios where the default field mappings match your actual configurationWhere they fall short:Marketplace integration apps are built around the most common configurations. When your Jira setup — or the system you're integrating with — has custom fields, non-standard workflows, or specific business logic, these apps can struggle. Some apps offer scripting or rule-based customisation to handle edge cases, but getting that configuration right for a complex setup takes significant time and specialist knowledge. You can end up spending weeks tuning an app that was supposed to save you weeks.There are also commercial considerations: licensing costs scale with users or data volume, and you're dependent on the vendor's roadmap for ongoing support and compatibility updates.Option 3: A Custom Forge AppAtlassian Forge is the cloud development platform for building apps that run natively inside the Atlassian ecosystem. A custom Forge app built specifically for your integration can handle arbitrary logic, connect to any external API, map fields exactly as needed, and include proper error handling and logging.Where it makes sense:Complex or bidirectional integrations where off-the-shelf tools can't match your configurationMigrations where data needs to be transformed, validated, or mapped before it lands in JiraLong-running or recurring synchronisation with specific scheduling or retry requirementsSituations where security or data residency requirements rule out third-party intermediariesThe honest tradeoff:A custom Forge app requires upfront development effort and someone who knows the Forge platform. It is not the right choice for a simple, standard use case where a Marketplace app would do the job. But when the complexity is real, a tailored app will be more reliable and easier to maintain than a heavily customised third-party tool.A real-world example: migrating from Azure DevOps to JiraA healthcare software company needed to migrate their entire development workflow from Azure DevOps to Jira Cloud. Their setup included custom fields, specific issue hierarchies, and compliance-related metadata that had to be preserved accurately during the transition.We evaluated several Marketplace migration apps. Some lacked the configuration options needed to handle the custom field structure on the Azure DevOps side. Others offered enough flexibility in theory, but getting the mapping logic right required so much custom scripting within the app that the effort was comparable to building something from scratch — without the reliability or maintainability.The decision was to build a custom Forge app tailored to their exact configuration in both systems. The app handled field mapping, data transformation, and validation before any record was written to Jira. The migration ran in controlled batches, with logging at each step so issues could be caught and corrected before they propagated. The result was a clean, auditable migration with no manual cleanup required after the fact.How to decide which approach is right for your situationSituationRecommended approachSimple event-based triggers, no external data transformationJira AutomationStandard integration between two common tools, default field mapping fitsMarketplace appComplex field mapping, custom workflows, or non-standard configurationCustom Forge appOne-time migration with transformation and validation requirementsCustom Forge appStandard migration between well-supported platformsMarketplace app (evaluate carefully)FAQ: Jira integrations and system connectionsCan Jira Automation connect to external systems like Azure DevOps or ServiceNow?Jira Automation can send and receive webhook calls, which allows basic event-driven communication with external systems. However, it does not support persistent state, complex data transformation, or reliable bidirectional sync. For anything beyond simple triggers, a more capable solution is needed.What is a Forge app and how is it different from a Connect app?A Forge app is a cloud-native Atlassian application that runs on Atlassian's own infrastructure. Unlike older Connect apps, Forge apps do not require you to host your own backend — the code runs inside the Atlassian platform, which simplifies security and compliance. Forge is Atlassian's recommended framework for new app development as Connect is deprecated and Connect apps need to be migrated to Forge.When should I use a Marketplace integration app instead of building something custom?If your Jira configuration is relatively standard and the Marketplace app supports the systems you're connecting, a Marketplace app is usually faster and more cost-effective. The risk is when your workflows or field configurations fall outside what the app was designed for — at that point, customisation effort can escalate quickly.How long does a custom Forge integration or migration typically take to build?It depends heavily on the complexity of the systems involved and the volume of data. A focused migration project with well-defined requirements typically takes a few weeks from scoping to completion. Ongoing bidirectional sync integrations take longer due to the need for error handling, scheduling logic, and testing across edge cases.Is a custom Forge app a realistic option for smaller teams or smaller budgets?It can be, particularly for one-time migrations where the alternative is weeks of manual data entry or a poorly configured Marketplace tool. The key is having a clear scope upfront. A well-defined migration project is often more predictable in cost than a Marketplace app that keeps needing adjustment.Need help figuring out the right approach?If you're evaluating options for a Jira integration or migration and aren't sure which route fits your situation, we're happy to talk it through. ij-solutions has hands-on experience building custom Forge apps and running complex migrations. We can help you avoid the dead ends before you invest time in the wrong direction.Get in touch with ij-solutions to discuss your requirements. #### Jira Template: Supercharge Your Project Workflow with Reusable Templates Why Jira Templates Are Your Workflow Game-Changer Stop rebuilding the wheel. Every. Single. Time. Think about it: how often do your teams create similar epics, stories, or bug reports? Without templates, each project manager reinvents basic structures, leading to inconsistent workflows and frustrated team members who can't find what they need.Jira templates come in a clutch because they deliver five game-changing benefits that smart admins can't ignore. First, you get to save time by automating the issue creation process instead of manual configuration marathons. You’ll also ensure consistency through standardized fields and workflows organization-wide, so every team speaks the same project language. Errors are also reduced thanks to the pre-defined structures that minimize human mistakes during those rushed project launches.But here's where it gets strategic: Jira templates also support best practices by embedding proven methodologies like Scrum, Kanban, and ITSM directly into your workflow DNA. You can even accelerate onboarding because your new hires are starting with established structures instead of guessing how your organization operates.3 Types of Jira Templates You Should KnowNot all templates are created equal. Understanding which type solves your specific workflow challenges makes the difference between template success and template chaos.1. Issue TemplatesThese templates handle the grunt work of pre-filled common fields like summary, description, and priority. Perfect for recurring tasks like onboarding checklists or bug reports, they reduce manual re-entry and errors that plague busy teams. One click, and your standard-issue template appears with all the right fields populated. Issue template configuration interface showing customizable field types (e.g., short text, paragraph, date, and URL fields). You can select appropriate field types to match your specific workflow needs, ensuring each issue type captures the right contextual information for efficient project management. 2. Project Templates These fully configured setups include workflows, permissions, and notifications built right in. Atlassian provides proven examples like Scrum, Kanban, DevOps, and Bug Tracking templates that establish consistent processes without starting from scratch. Why reinvent project architecture when battle-tested frameworks already exist? Here’s what a Kanban project template would look like. 3. Automation Templates They bring intelligence to your workflows through ready-made automation rules. They auto-assign issues based on criteria, send deadline reminders, and transition statuses as work progresses. Jira's template library offers hundreds of automation recipes that transform manual administrative tasks into background processes. Find out more in the Jira Automation Playground by Atlassian When Jira Templates Hit Their LimitsUnfortunately, Jira templates aren't magic bullets, and you might encounter these frustrations when working with them out of the box:No hierarchical template support – You can't create a story with predefined subtasks natively, forcing teams into manual setup after template application.Post-creation application – When a template is configured to apply after issue creation, Jira updates the newly created issue with the template’s preset field values, which can overwrite user input and cause confusion.System field limitations – Can't set default values for descriptions or enforce specific formats across teams.No dynamic variables – Forget auto-inserting current users, dates, or context-specific priorities during creation.Complex linking challenges – Epic-story-subtask relationships and issue links aren't fully supported, breaking sophisticated project hierarchies that mature teams depend on. You’re still going to need advanced bulk clone strategies in Jira to replicate intricate epic structures across departments.Customization barriers – Adapting to unique project needs becomes unnecessarily difficult.Performance concerns – Large template structures clutter the UI and slow down team productivity during critical project phases.Go Beyond Jira Template Limitations with Epic CloneThe template gap becomes obvious when you need to replicate existing complex hierarchies between issues, complete with custom field values and intricate relationships. Templates create new structures. But what happens when you need to duplicate successful project patterns?Epic Clone bridges this critical divide with powerful advantages that templates simply can't match:Clone entire epic structures with preserved relationships - every parent-child link, custom field, and issue connection stays intact. Create a Jira epic template with an approved structure that you can easily clone and customize for any project. Background processing handles large projects without UI blocking, so teams keep working while clones generate.Cross-project cloning with field modification capabilities lets you adapt successful patterns to new contexts.Bulk operations that templates can't handle, including Epic Clone's new REST API for automated cloning workflows. Here's a real-world scenario that showcases the difference: Your Jira template creates a standard epic structure for new marketing campaigns. Great start! But when Q4 planning arrives, you need to replicate your most successful Q3 campaign epic - complete with all subtasks, custom fields, and team assignments - across five different regions.Templates force you to start from scratch each time. Epic Clone replicates that winning issue hierarchy across teams with region-specific customizations in minutes, not hours!Jira Templates vs. Epic Clone: Decision MatrixStill uncertain which approach fits your workflow needs? This decision matrix cuts through the confusion and points you toward the right solution for your specific scenario.ScenarioUse Jira TemplatesUse Epic ClonePurposeCreate standardized new structuresDuplicate existing hierarchies with dataBest ForRecurring standardized tasks, new project setupReplicating complex epics, cross-project duplicationHierarchiesLimited to flat/simple structuresExcellent for initiatives → epic → story → subtask chainsBulk OperationsManual, limited scopeBulk cloning with preserved relationshipsCustomizationNo, static predefined fieldsYes, edit fields and bulk changes before cloningUse CasesSimple checklists without customization Similar projects, recurring complex workflowsThe choice becomes clear when you understand your project complexity and replication needs. Jira Templates excel at creating fresh structures, while Epic Clone dominates when duplicating proven workflows and work structures across teams or projects.Ready to clone complex project structures beyond template limitations? Try Epic Clone free today. #### Leveraging the Best Agile Project Management Tools for Smarter Team Collaboration When scaling Agile frameworks across multiple teams, it’s essential for an organization to have the best Agile project management tools in place. Without them, adding new processes without thoughtful implementation can lead to unnecessary complexity and slow progress.But with the right intent, scaling Agile can bring about structure and clarity. It’s about ensuring that teams don’t just move faster, but faster together.Let’s say your software development team is gearing up to launch a new feature. For the front-end team, this involves a well-defined workflow that includes:Implementing visual and interactive elementsHandling data integrationConducting rigorous tests and quality assuranceOptimizing code and assets to ensure smooth performanceCollaborating with designers, backend engineers, product managers, and support teams to coordinate the launchMonitoring the launch for any immediate issuesConducting post-launch maintenance This process repeats with every new release. But here’s the problem: unless there’s a way to reuse and replicate these setups, the team will likely spend unnecessary time rebuilding the same structure again and again. The Hidden Challenges of Manual Epic DuplicationJira has long been a favourite project management platform for Agile teams. It makes it easy to create Epics, break them into Stories and Tasks, and track progress across sprints and releases.Yet, while Jira allows you to clone individual issues, it cannot duplicate entire Epics in one go. Therefore, if your team wants to reuse an Epic from a previous release, they’ll need to manually recreate each Story, Subtask, and dependency.Not only is this time-consuming, but it also opens the door to errors and inconsistencies.Here are a few examples of what often goes wrong:Operational inefficiency: Repeating the same setup process over and over takes up the team’s time and delays critical decisionsHuman error: Fatigue and distractions can cause inconsistencies or missed steps that directly impact product qualityData inconsistency: Without a uniform template or automation, formatting and structure can vary from one project to another, and lead to miscommunicationSecurity risks: Sensitive data or restricted access settings can be mishandled during manual duplication, increasing the company’s risk of violating security and compliance protocols This goes to show that, for teams aiming to scale, continuing with manual duplication simply isn’t sustainable. How the Best Agile Project Management Tools Help Teams Scale SmarterSo, how can the front-end department remove these friction points and scale more effectively? Tools like Epic Clone are built for this very purpose. Designed to work with Jira and other Agile project management platforms, Epic Clone allows users to duplicate entire Epics, along with Stories, Tasks, and Subtasks, while adjusting fields like assignees, components, and due dates on the go. It gets better. Epic Clone supports the cloning of multiple issues simultaneously, which eliminates concerns about cloning limits.These standout characteristics address the previously discussed obstacles by:Boosting efficiency and speed: Project managers can clone entire Epics in bulk, drastically reducing setup time across parallel teamsMinimizing human error: Team members can significantly reduce the likelihood of missed tasks or misassigned stories that occur with repetitive stepsStandardizing formatting and structure: Templates make handovers and reporting much easier by ensuring consistency across teams and allowing Epics to retain their hierarchical relationships What Does This Mean for Agile Teams at Scale?Fundamentally, Epic cloning is about building scalable systems that empower teams to move swiftly and with more confidence.Here’s how Epic Clone translates into real-world gains for your organization:Time: Launch new initiatives quicker by replicating proven Epic structuresConsistency: Ensure all projects align with your organization’s best practicesTemplate-ready setups: Teams can hit the ground running with a pre-established Epic structure rather than reinventing the wheel every timeHierarchy retention: Parent-child relationships within issues can be preserved, maintaining traceability and contextSmarter resource allocation: Successful workflows can be copied across teams, improving manpower utilization across teams and projects Scaling Agile isn’t about adding more steps; it’s about removing barriers.If your software development company is constantly juggling the same workflows across multiple teams, adopting tools like Epic Clone can be a game-changer.Ready to streamline your Agile operations? Explore the best Agile project management tools and discover how Epic Clone can help your organization scale with speed, consistency, and confidence. #### New: Issue Hierarchy Cloning in Jira Made Easy Managing complex projects often involves dealing with intricate issue hierarchies, where knowing how to clone an issue in Jira becomes essential. Previously, replicating these structures required extensive manual work—carefully cloning each issue individually and then reconstructing relationships and contexts by hand.With an app like Epic Clone, you could at least clone epics with their child issues and possible sub-tasks in bulk. However, what if you have an additional hierarchy level above epics? In many cases, epics aren’t the top of everything. They are situated on one hierarchy level within a larger structure across Jira projects.Imagine a work item type referred to as an 'Initiative,' positioned above Epics within the hierarchy. For instance, this Initiative encompasses four Epics, each of which contains multiple tasks and stories beneath it. Replicating the entire structure can be both time-consuming and prone to errors, which can frustrate users. This process requires not only cloning each work item individually but also reestablishing the relationships between initiatives and epics, as well as between epics and stories, among others. New Feature for Epic Clone: Replication of HierarchiesWith the latest significant update to our Epic Clone app, we're thrilled to introduce Issue Hierarchy Cloning, a revolutionary feature designed to save you significant time and effort. Instead of individually cloning each issue or epic and rebuilding parent-child relationships, Epic Clone now allows you to replicate entire hierarchies instantly, from the top-level parent issue through all nested child issues. This is particularly useful when teams need to clone Jira projects with issues intact, ensuring no data or structure is lost in the process. Before vs. After: Streamlining Your WorkflowBefore this update, cloning an issue hierarchy in Jira required considerable manual intervention:Without an app like Epic Clone:Clone the parent issue.Individually clone each child issue and subtask.Manually restore all hierarchical links and relationships.Double-check to ensure no relationships were missed, risking potential errors or incomplete issue structures.With Epic Clone before the latest update:Clone the parent issue of the epic.Individually clone each epic under the parent along with its child issues and subtasks using Epic Clone.Manually restore parent link in Epics to the new parent. With our new Issue Hierarchy Cloning, you can now:Clone entire issue structures with just a few clicks.Maintain all existing relationships, nested levels, and contexts automatically.Reduce errors and ensure consistency across duplicated issues.Significantly cut down the setup time for recurring or repetitive projects. Epic Clone also supports advanced use cases like the ability to clone Jira issues to another project, retaining all the original structure and links.The latest update has brought significant improvements to hierarchy cloning, as illustrated by the example work item hierarchy mentioned earlier. At the top, you will find information detailing the total number of child items and the various hierarchy levels present within the structure. Explore our comprehensive guide on epics and cloning in Jira, designed to help teams duplicate tasks effortlessly while retaining key details. Experience the DifferenceThis powerful enhancement ensures that your team spends less time on repetitive tasks and more time delivering value. By preserving the full context and structure of your Jira issues automatically, your workflows become seamless and more efficient than ever before.From individual tasks to full initiatives, our tool helps you clone Jira issues to another project, or even clone an issue in Jira with full hierarchy replication. Say goodbye to repetitive manual cloning.Try the enhanced Epic Clone app today and experience the difference in your productivity and workflow management. #### Rebuilding Legacy Atlassian Apps on Forge: Challenges and How Expert Consultants Help Why Migrating to Forge Isn't a Simple ProcessPlanning to "migrate" your Connect app to Forge? Stop. Think rebuild instead.Here's the uncomfortable truth: Forge isn't a migration platform. It's a complete rearchitecture project that demands strategic thinking and patience. While other Atlassian migrations, like Server to Cloud, offer automated tools and guided pathways, Forge operates in an entirely different universe.Why such a dramatic shift? Core incompatibilities run deep. Forge imposes 16MB payload limits that can shatter existing data models, plus 25-second execution timeouts, forcing you to rethink background processes. You're dealing with new permissions models, security tokens replacing JWT systems, and event-driven execution patterns.Connect-on-Forge exists as a migration option, sure. But it essentially runs your same Connect code on Forge infrastructure rather than creating a true Forge app. Most Atlassian Forge experts don't recommend this approach for long-term success. Unlike Server/DC migrations, Forge offers no automated data transfer utilities. No migration tools. Just you, your team, and the challenge of rebuilding from scratch.When Forge Rebuilds Make Strategic SenseSo why rebuild at all? Simple answer: competitive advantage.Enhanced security tops the list. Tenant isolation, strict permission scopes, and OAuth 2.0 authentication—these aren't just buzzwords for your next board meeting. They're real compliance wins that can unlock enterprise deals previously out of reach.Infrastructure headaches? Gone. Forge's serverless, Atlassian-managed environment eliminates the operational overhead that's been draining your DevOps budget. No more 3 AM server alerts or capacity planning spreadsheets.But here's where it gets interesting for forward-thinking CTOs: access to capabilities that simply don't exist elsewhere. Advanced APIs that unlock new workflow possibilities. Immediate updates without waiting for admin approval cycles. Granular permissions that finally give users exactly what they need—nothing more, nothing less. Most importantly? Future-proofing. Atlassian's strategic cloud direction post-2025 isn't speculation—it's their published roadmap. Early movers gain first-mover advantages while competitors scramble to catch up later. 4 Major Challenges You'll Face in Rebuilds & How Forge Experts HelpLet's be honest about what you're walking into and how expert consultants turn these obstacles into advantages.1– Skills Gap & Learning CurveForge's serverless architecture requires entirely new expertise that most internal teams lack. Teams need upskilling in unfamiliar APIs, permission models, and UI frameworks, which can extend project timelines by 3–6 months.❌ Budget overruns and missed deadlines become inevitable when internal teams learn on the job. ✅ Consultants bring Forge-ready expertise immediately, eliminating months of costly internal upskilling and accelerating time-to-value.2– Platform Evolution & StabilityRapid Forge updates can break existing functionality overnight, creating unexpected maintenance overhead. At the same time, continuous monitoring becomes non-negotiable but drains internal resources. Feature deprecations can also impact carefully planned development roadmaps, forcing costly pivots.❌ Platform instability threatens business continuity and increases technical debt. ✅ Consulting teams can track Atlassian updates proactively and adapt your apps before breaking changes impact operations.3– Technical Limitations & ConstraintsRuntime limits force complete data model redesigns that internal teams often get wrong. Storage caps also require architectural overhauls beyond typical in-house capabilities. API parity gaps may eliminate beloved existing functionality, creating user adoption resistance.❌ Poor architectural decisions create scalability bottlenecks that require expensive rewrites.✅ Expert consultants can design future-proof architectures from day one, avoiding costly technical debt.4– Business Continuity RisksDowntime during transition periods threatens user productivity and revenue. Staff training on new interfaces disrupts established workflows, further reducing team efficiency. Temporary loss of advanced features during rebuild phases impacts operational capabilities.❌ Operational disruption directly impacts bottom-line performance. ✅ Experienced consultants minimize business disruption through phased rollouts and comprehensive change management strategies.Strategic Forge Rebuild Planning FrameworkSuccess demands structure. Fortunately, at ij-solutions, we guide clients through our proven 8-step framework to ensure continuity, compliance, and efficiency at every stage of Forge rebuild.Assess & Document: We catalog every feature, workflow, dependency, and data model in your current app, creating the blueprint for what must be preserved versus reimagined.Analyze Forge Capabilities: We study platform quotas and check feature parity against your requirements, identifying functionality gaps before they derail timelines.Design New Architecture: We define your app structure with Forge constraints in mind, planning data migration pathways and mapping permissions alongside UI/UX considerations.Prepare Migration Plan: We prioritize critical features ruthlessly and set up isolated development environments with comprehensive test strategies that determine launch success.Develop & Iterate: We build modules incrementally while testing continuously, refactoring as we discover what works versus what looks good on paper.Migrate Data & Integrations: We back up existing data multiple times before implementing import scripts, validating data integrity obsessively to preserve user trust.User Acceptance & Rollout: We pilot with key users for honest feedback, train staff thoroughly, and iterate based on real usage patterns, not assumptions.Monitor & Optimize: We track performance metrics religiously and respond to platform updates quickly because continuous improvement isn't optional, it's survival.Why Expert Forge Consultants Accelerate SuccessAs the Forge specialists, we aim to deliver measurable value:Strategic planning with comprehensive rebuild roadmaps aligned to your business objectives.Technical execution through expert development teams with specialized Forge experience.Change management support, including user training and adoption strategies.Ongoing optimization based on platform evolution and performance monitoring.Atlassian's cloud-first future makes Forge inevitable for serious enterprise applications. The question isn't whether to rebuild, but whether you'll do it efficiently with expert guidance or expensively through painful trial-and-error.Ready to navigate your Forge rebuild successfully? Let ij-solutions help you plan a smart, cost-effective app development strategy that protects your investment and accelerates your timeline. #### Runs on Atlassian Badge: What Does It Mean? We’re excited to announce that all of our apps on the Atlassian Marketplace now carry the new “Runs on Atlassian” badge — a mark of trust, performance, and robust data security. This badge signifies that an app runs entirely on Atlassian’s own cloud infrastructure, offering best-in-class protection for your data with zero data egress.What Is the “Runs on Atlassian” Badge?Introduced by Atlassian in May 2025, the “Runs on Atlassian” badge highlights Marketplace apps that are fully hosted on Atlassian’s cloud platform. These apps never transfer data outside of your Atlassian Cloud instance. In simple terms:No external data processingNo third-party serversNo data egress — ever This is a game-changing guarantee for companies that prioritize data residency, privacy, and compliance.What’s the difference between Runs on Atlassian and Cloud Fortified?Our apps hold both badges, but you might wonder what's the difference between both. We can quote the official blog post from Atlassian at this point:Both Runs on Atlassian and Cloud Fortified are trust badges, but they reflect different aspects of an app’s security posture.Runs on Atlassian indicates that apps are Atlassian-hosted and won’t egress data without the customer’s consent, a technical fact that Atlassian can programmatically verify.Cloud Fortified is a broader set of signals that includes organizational behaviors and practices, like support, reliability, and bug bounty participation. Because they reflect different requirements, an app might have one of the badges, or both. Cloud Fortified is an important signal that a partner has invested in advanced trust practices across their business.Why It Matters for YouIn today’s cloud-driven environment, security and compliance are top of mind for IT teams, security professionals, and business leaders alike. The “Runs on Atlassian” designation assures you that:Your data stays inside the Atlassian Cloud at all timesApp performance is optimized with Atlassian’s secure, high-availability infrastructureYou meet internal compliance and governance standards more easilyThere’s no need for additional security audits or vendor risk assessments For organizations in regulated industries or those with strict data governance policies, this badge provides peace of mind that third-party app usage won’t compromise security.Our Commitment to Secure, Compliant AppsAt ij-solutions, we’re proud to be early adopters of Atlassian’s highest security standards. Our apps — including Epic Clone, Duplicate Epic, Project Milestones, User Absence Planner, and Projects Insight Edge — are now fully compliant with the “Runs on Atlassian” criteria.This means that when you install any of our apps, you can be confident that:Your data never leaves Atlassian’s secure infrastructureYou maintain control over your informationYou’re using tools built with enterprise-grade security in mind What’s NextWe believe that transparency, trust, and performance are the future of the Atlassian ecosystem. With the “Runs on Atlassian” badge, we’re doubling down on our promise to deliver apps that are not only powerful and easy to use — but also secure by design.Ready to explore our apps? Visit our Marketplace profile and experience the difference of apps that run where your data belongs — on your Atlassian Cloud site. #### Scaling Jira Without Chaos: Advanced Strategies of Enterprise Bulk Cloning Project The Enterprise Cloning ChallengePicture this scenario. Your team needs to replicate 500 Jira issues across three projects by next week. How would you do this?At enterprise scale, bulk cloning isn't just admin work, it's mission-critical infrastructure management. Manual approaches that work for small teams become operational risks when you're dealing with complex project hierarchies and tight deadlines.Here's why: enterprise-scale bulk cloning isn't just about moving data from Point A to Point B. You're dealing with interconnected webs of epic hierarchies, custom field mappings, and issue dependencies that took months to build. Data integrity, hierarchy preservation, and workflow continuity are all at risk when cloning processes break down.The stakes? Teams miss sprint deadlines and projects derail. And somewhere, a project manager is explaining to executives why the "simple copying task" turned into a three-week recovery operation.Business Drivers Behind Enterprise Bulk CloningWhy do organizations even attempt bulk issue cloning at scale in the first place? The business case is compelling:Time efficiency at scale: You're replicating thousands of issues with minimal clicks instead of drowning your teams in weeks of tedious manual recreation across global projects. This is critical for enterprises managing hundreds of concurrent projects across global teams.Cross-departmental consistency: Multi-project organizations need uniformity because standardized processes ensure compliance and prevent costly workflow variations that undermine governance structures.Large-scale testing and QA: Complex test cases and scenarios need quick reproduction across multiple environments. This is essential for enterprises that have rigorous quality assurance requirements and regulatory compliance breathing down their necks.Project migration and consolidation: When M&As happen, organizational restructuring becomes inevitable. During these chaotic periods, you need to move massive volumes of issues seamlessly while maintaining data integrity and audit trails.Enterprise process standardization: Proven Jira templates and workflows should duplicate across departments and regions effortlessly, ensuring HR onboarding sequences, service management templates, and compliance processes stay consistent company-wide.Cross-team synchronization: Align related teams with identical issue structures so global departments operate from the same playbook, reducing miscommunication and improving scalability. Enterprise risk reduction: Automated cloning eliminates manual entry errors and preserves data quality at scale. This is important for organizations where data integrity impacts compliance, reporting, and strategic decision-making. Why Native Jira Falls Short for Enterprise Needs & Its ImpactJira's native cloning feels adequate until you hit enterprise scale. Here are the critical limitations and risks most teams don't anticipate:Risk CategoryNative Jira LimitationEnterprise ImpactManual OperationsLimited bulk cloning functionality available - restricted to same-project operations with quantity limits per batch.Teams waste weeks manually copying hundreds of issues one by one.Broken HierarchiesEpic-child relationships are preserved, but relationships among child issues may be lost. Native Jira also limits hierarchy cloning to two levels, whilst third-party apps can handle deeper hierarchies.Sprint planning becomes impossible when child issues lose relationships between each other. Custom Field LossLimited customization (e.g., renaming issues) prevents field remapping and transformation rules.Reporting dashboards break, and automated workflows stop functioning.Missing ContextAttachments and historical data are often skipped during operations.Critical project documentation and decision history vanish forever.Performance LimitsMemory-intensive operations can cause system timeouts in Jira Server/Data Center environments. Jira Cloud performance remains stable due to limited bulk operations.Large enterprise projects fail halfway through, leaving corrupted data structures.The enterprise reality is harsh but simple: native tools were designed for small-scale operations, not complex organizational workflows across multiple teams and projects. Jira's native capabilities become a bottleneck, not a solution.Epic Clone: Built for Enterprise ScaleFortunately, where native Jira stumbles, specialized tools step up. We designed Epic Clone app specifically to handle the complexities that break standard cloning workflows at enterprise scale.Background processing: Handles 15-minute runtime for massive projects without blocking dialogs or freezing your interface, letting teams continue working while complex cloning operations run seamlessly behind the scenes.Hierarchy preservation: Complete epic → story → subtask chains are maintained automatically with all parent-child relationships intact, eliminating the manual reconstruction work that destroys productivity in native Jira. Our app allows you to clone initiatives above epics and connect the complex relationships between initiatives, epics, stories, and subtasks. Attachment handling: You can enable or disable attachment cloning per project, meaning you transfer only absolutely important files while avoiding system bloat from unnecessarily large documents that slow down operations.Cloning REST API: Automate bulk cloning operations through REST API, enabling scheduled cloning jobs and integration with external systems for streamlined workflow automation across your entire organization.Progress transparency: Source and target summaries confirm successful cloning operations for all users. Additionally, administrators gain valuable insights through usage statistics that track how frequently the app is used and the total number of issues cloned across the instance, providing data for monitoring adoption and system utilization. Once the cloning is done, you’ll get the links to all the cloned issues. What takes hours of manual work happens in minutes with automated processing, transforming bulk cloning from a dreaded administrative burden into a strategic operational advantage.Strategic Recommendations for Safe Bulk CloningEnterprise bulk cloning isn't just about moving data faster. It's about maintaining the complex relationships and hierarchies that make Jira valuable while scaling operations without breaking workflows.To get it right, follow these strategic recommendations:Define exactly what needs cloning and why. Are you replicating a single product rollout or duplicating a multi-region launch? The distinction matters because scope creep exponentially increases complexity and failure points.Validate configurations on limited datasets before scaling. Why? Corrupted hierarchies at enterprise scale create cascading failures that require weeks to untangle. Preventing rework saves time and preserves team credibility.Leverage apps like Epic Clone that preserve hierarchies automatically. Native Jira cloning can break issue links. Epic Clone maintains parent-child relationships and custom field mappings that took months to establish.Verify cloned data integrity before execution. Spot-checking isn't enough. Run comprehensive validation on epic hierarchies and dependencies because discovering broken relationships after teams start working derails projects and progress. Want to scale your cloning operations without the chaos? Try Epic Clone free today and experience enterprise-grade bulk cloning that works. #### Scaling Smart: How Strategic Atlassian Architecture & Integration Consulting Saves Time, Money, and Headaches The Hidden Dangers of Unplanned Atlassian Growth Picture this scenario. Your startup launched with a scrappy 10-person team using basic Jira and Confluence setups. Fast forward three years, and you're now managing 500+ users across multiple departments, each with their workflows, custom fields, and "quick fixes" that someone implemented last quarter.Sound familiar?This is where strategic Atlassian consulting pays dividends. Instead of reacting to inefficiencies, expert consultants help enterprises design scalable architectures that prevent technical debt, streamline integrations, and safeguard compliance.Without proper guidance, workflows become confusing puzzles, automations break mysteriously, and security gaps emerge between tools. Teams waste hours on broken processes while IT patches problems instead of building solutions, creating compliance risks and spiraling maintenance costs.Strategic consulting transforms this reactive cycle into proactive architecture that scales seamlessly. Architectural problems accumulate quietly until small inefficiencies become business-critical failures. When to Review Your Atlassian EnvironmentTiming matters. But when exactly should you pause growth and assess your architectural foundation?1. Complexity & Scale GrowthYour user base exploded beyond original design parameters, from 50 to 500 users overnight. Multiple projects now have tangled cross-team dependencies that nobody fully understands, creating bottlenecks that delay product launches by weeks. Decision-makers start asking uncomfortable questions about system reliability when downtime directly impacts revenue.2. Increased Customizations & App Usage You've deployed numerous custom apps, scripts, and Forge extensions without a master plan. Complex workflows affect data flow in unexpected ways, costing thousands when a single app update breaks critical workflows. Performance bottlenecks emerge, forcing teams to work around system limitations instead of focusing on strategic initiatives.3. Security, Compliance & Governance Concerns New regulatory requirements hit hard. GDPR, HIPAA, and SOC2 compliance have suddenly become non-negotiable, with potential fines reaching millions for non-compliance. Enterprise security policies shift dramatically, and data residency mandates require immediate architectural validation. Delays here expose organizations to legal liability and lost customer trust.They are all interconnected warning signals. Smart organizations recognize these patterns early and engage an Atlassian consultant before problems compound. 6 Hidden Costs of Scaling Without Strategic PlanningHere's what keeps CTOs awake at night: the exponential cost curve of architectural negligence.Every shortcut creates debt. Every "temporary" workaround becomes permanent. Every quick fix spawns three new problems that require increasingly complex solutions.Cost CategoryImpactBusiness ConsequenceTechnical DebtSuboptimal solutions require constant rework and patches.Maintenance overhead increases while development velocity plummets.Productivity LossTeams spend more time fixing bugs than building features.Time-to-market delays compound while competitive advantage erodes.System InstabilityPoor code quality leads to frequent downtime events.Customer trust deteriorates while reputational damage spreads.Knowledge SilosUnclear ownership creates scattered documentation chaos.Problem resolution slows dramatically while collaboration barriers multiply.Integration BrittlenessHard-to-maintain dependencies break during scale changes.System failures cascade across interconnected business processes.Compliance GapsSecurity vulnerabilities emerge from rapid, unplanned changes.Regulatory fines threaten, while audit failures damage credibility.The bottom line hits hard: architectural problems cost more to fix over time, while an Atlassian consulting service prevents these cascading failures from the start.Seamless Integration Strategy for Enterprise SuccessSeamless integration orchestrates your entire business symphony. Tools become instruments working in harmony rather than competing solo acts.Without expert guidance, DIY integration attempts typically result in data inconsistencies, security vulnerabilities, and maintenance nightmares that consume IT resources for years.With strategic consulting? Different story entirely. Organizations establish scalable APIs, clean data flows, and robust governance frameworks that actually work. Enhanced productivity: Data silos disappear through expertly designed connectors. Teams gain unified dashboards, while fragmented decision-making becomes a thing of the past.Enterprise agility: Real-time visibility emerges across portfolios through properly configured integration layers. Executives finally get that unified view they've demanded.Unified workflows: Project tasks link seamlessly to documentation. Code commits trigger automated workflow updates, and service requests generate intelligent follow-up actions without manual intervention. Expert consultants define clear role hierarchies, leverage Atlassian APIs alongside Forge for truly scalable integrations, and design cross-functional collaboration frameworks where teams work seamlessly rather than competing for resources.Future-Proofing Your Atlassian InvestmentTechnology moves fast. Your architecture needs to move faster. Smart organizations align with Atlassian's strategic direction early. Rebuilding legacy apps on Forge to deliver serverless, secure customization that scales automatically. AI-driven innovation, powered by Atlassian Intelligence and Rovo, transforms routine tasks into automated insights. Cloud-native transitions unlock agility while providing access to cutting-edge features.But here's the critical insight: set it up correctly from the start by leveraging the expertise of a competent Atlassian expert partner during initial configuration and administration. They can help you design architectures that scale with business growth, choose solutions aligned with Atlassian's long-term roadmap, and implement governance frameworks that prevent technical debt accumulation before it starts.Investment protection requires modular systems that adapt to changing requirements while maintaining stability. The goal is for you to build once and scale everywhere.Why Expert Architecture Consulting Pays for ItselfAt ij-solutions, we bring proven Forge expertise to organizations navigating Atlassian's complex ecosystem. Here's what we can deliver:Prevent costly mistakes before they compound, saving maintenance costs annually through battle-tested deployment patterns.Navigate critical decisions about native features versus third-party apps, reducing implementation time, while identifying potential issues early.Design automation strategies that scale without hitting execution limits, cutting manual admin work.Establish structures that prevent configuration drift, ensuring audit-readiness without requiring additional administrative overhead.Transform complex Atlassian ecosystems into streamlined solutions that reduce onboarding time while growing with your business.Ready to scale your Atlassian environment without the growing pains? Let ij-solutions help you design a smart, scalable Atlassian architecture that saves time, money, and stress. #### Using Jira for Project Management: A Modern Guide to Boosting Efficiency Mastering Jira for Streamlined Project ManagementJira has become the go-to platform for project management across most organizations. Teams use it to coordinate work, track what's happening, and keep projects moving forward. But plenty of teams still end up frustrated with messy boards, workflows that don't make sense, and projects that feel chaotic. What separates the teams that love Jira from those that struggle with it is getting the basics right from day one: proper structure, team alignment, and smart reusability. In this guide, we'll walk you through how to set up Jira boards that actually work, organize projects so everyone knows what's going on, keep timelines on track, and create templates you can use again and again.Board Setup & Project OrganizationThe key to scaling your project launches efficiently lies in designing boards that mirror your actual workflow instead of Jira's generic defaults. Use: Scrum boards for sprint-based workflows with fixed timeboxes. Kanban boards for continuous flow work.  But here's where most teams go wrong: they stick with Jira's basic "To Do, In Progress, Done" setup, which creates confusion and slows down progress tracking. Instead, customize columns to reflect your team's reality and reduce admin drag. For example: Marketing teams require "Concept, Creative Review, Legal Approval, Published." IT service teams require "Waiting for Support, In Progress, Waiting for Customer, Resolved."  Board customization streamlines team onboarding by making project status instantly clear to newcomers. For complex initiatives, create multiple boards for different project phases with customized filters and columns. Use strategic swimlanes and quick filters ("My Issues," "This Sprint") to maintain focus without board clutter. This is particularly essential for managers juggling multiple projects simultaneously.Timeline & Cross-Team ManagementWhen you're coordinating launches across departments, timeline visibility becomes your competitive advantage. Use Scrum boards with clearly defined sprints for predictable delivery cycles and accountability. For continuous improvement processes, leverage Kanban's WIP limits and time-in-column indicators to spot bottlenecks before they derail your timelines. Scale your strategic project oversight with Jira roadmaps to map out features, epics, and milestones over time, which gives stakeholders the high-level timeline visibility they need. For better efficiency, link related issues using "blocks" and "relates to" relationships, and create shared epics that unite multiple teams under common goals. You can also create shared summary boards that aggregate progress from multiple teams, and define clear workflows with agreed transitions to reduce the administrative burden of status meetings.The Reusability Game-ChangerSmart Jira project managers don't recreate the wheel. They build once, then replicate everywhere.Jira template creation follows a "build once, use everywhere" philosophy. Just create master project structures that capture your team's best practices, then adapt them for new initiatives. For example, a successful product launch template becomes the foundation for every future release.But here's where most teams hit a wall: maintaining complex project structures during replication. Manual copying breaks epic relationships, loses custom field values, and creates data inconsistencies that take hours to fix.Consider this hypothetical scenario: A software company launches a mobile app across 5 regions (US, Europe, Asia-Pacific, Latin America, Middle East). Each launch requires the same epic structure:Market Research epic (competitor analysis, user surveys, regulatory requirements)Localization epic (translation, cultural adaptation, local payment methods)Marketing Launch epic (PR campaign, influencer outreach, app store optimization)Technical Deployment epic (server setup, CDN configuration, monitoring)Without proper reusability tools, project managers waste weeks recreating these epic hierarchies for each region, risking missed tasks and inconsistent processes. What took five weeks of manual setup should take five hours with smart replication strategies.Epic Clone: Your Efficiency MultiplierMaintaining complex epic → story → subtask relationships during replication requires more than manual copy-paste. Fortunately, the manual nightmare ends here using Epic Clone. Bulk copying issues in Jira? Get it done in one action. Project managers no longer waste hours manually duplicating individual tickets and rebuilding relationships. One click replicates entire project structures and preserves complete project hierarchies (epic-issue-subtasks), making large-scale project rollouts efficient and error-free. You can build a Jira epic template with a pre-approved issue hierarchy that can be easily cloned and tailored for use in any new project. The app’s clone in background feature allows you to clone large epics or complex hierarchies without keeping the dialog open. Cloning runs for up to 15 minutes in the background. This is crucial for large companies with massive projects where teams can continue working while complex structures replicate seamlessly.Better (and optional) attachment cloning keeps projects moving forward. Large or numerous attachments no longer block cloning operations. Other project activities proceed smoothly while attachments are duplicated, ensuring project momentum isn't lost due to file processing delays.The new cloning REST API unlocks powerful automation capabilities for project management at scale. Schedule recurring clones, trigger operations from external systems whenever specific events occur (e.g., new employee onboarding), and deploy templates across teams. This eliminates manual setup hours and accelerates project kickoff from weeks to minutes.This means project setup time drops from days to minutes. Teams launch faster and spend their energy on value creation instead of administrative busywork.Transform Your Project Management EfficiencyEpic Clone delivers measurable project management improvements that transform how teams operate:Time savings: Faster project initiation and setup eliminates weeks of manual structure recreationStandardized processes: Consistent workflows across all teams reduce confusion and improve qualityRisk reduction: No missed tasks in complex workflows when hierarchies remain intact during cloningOnboarding acceleration: New teams start with proven structures instead of building from scratchEnterprise scalability: Replicate successful project frameworks across departments and regions effortlessly Ready to supercharge your project management efficiency with advanced cloning capabilities? Try Epic Clone free today. #### What is Atlassian Forge? A CTOʼs Guide to the Future of App Development An Overview of Atlassian ForgeAtlassian Forge is more than just another enterprise app development platform; it's Atlassian's vision for the future of enterprise software, designed from the ground up to eliminate the complexity that's been strangling IT teams for years.Think serverless architecture meets enterprise security. Forge is a cloud-native app development platform that removes infrastructure overhead entirely, letting your teams focus on what actually matters: building solutions that drive business value for your customers.Here's the strategic context that should get your attention: Atlassian just crossed $5.2 billion in revenue this year, while its marketplace hit the $1 billion milestone back in 2019. We're talking about 25,000+ ecosystem developers building on this platform. If this is not a massive transformation, we don’t know what is!Atlassian's Cloud-First Strategic DirectionSo, why is Atlassian betting everything on Forge? Simple. The old way of building enterprise apps is broken.Traditional development means managing servers, worrying about scaling, and drowning in infrastructure complexity. Forge flips this equation entirely. It's Atlassian's strategic pivot toward a cloud-native future where businesses can innovate without the operational burden that's been holding them back for decades.But Forge isn't just about easier development. It also unlocks possibilities that were previously impossible or prohibitively expensive. Companies can now build custom apps deeply tailored for their own or customers’ internal workflows—the kind of hyper-specific solutions that drive real competitive advantage. Most importantly, legacy Connect apps face an expiration date. By late 2025, Atlassian mandates the shift to Forge, and apps that haven't migrated will stop receiving updates entirely. Are your internal teams or customers depending on those apps? They're left stranded with outdated, potentially vulnerable software. If you delay your Forge migration, you risk losing their trust when you can no longer deliver seamless service or critical security patches.Organizations that embrace this shift early will have solutions that evolve seamlessly with Atlassian's platform updates, while others scramble to catch up.Why CTOs Are Choosing Forge: Enterprise Benefits That Drive ResultsThe numbers don't lie - when enterprise leaders evaluate Forge, they're not just looking at a development platform, they're seeing measurable business impact across operations, security, and strategic value.Operational ExcellenceZero infrastructure management: No server provisioning, scaling, or maintenance headaches.Automatic scalability: Platform handles demand spikes and user growth without intervention.Reduced operational overhead: Atlassian manages hosting, uptime, and version control entirely.Security & ComplianceEnhanced security model: Multi-tenant infrastructure with enforced data residency.Compliance-ready architecture: Built-in GDPR, HIPAA, SOC2 compliance capabilities.Zero egress by default: Data stays within Atlassian's secure environment.Fine-grained access control: Strict permission scopes and tenancy isolation.Strategic ValueDeveloper productivity gains: Order-of-magnitude reduction in code requirements.Faster time-to-market: Focus shifts from infrastructure to business functionality.Future-proofing: Native integration ensures apps evolve with platform updates automatically. At ij-solutions, we built our flagship Epic Clone app entirely on Forge, which demonstrates core Forge capabilities such as enterprise-grade bulk cloning with background processing, cross-project functionality, and complete data residency compliance. Recently, we even added a REST API for automated cloning, opening up entirely new possibilities for workflow integration and scheduled operations. All this is made possible thanks to Forge. Why You Need Forge Experts on Your SideBuilding on Forge isn't like traditional app development. That's precisely why partnering with experts makes the difference between success and expensive mistakes.Complexity navigation: Forge architecture decisions impact long-term scalability. Our team has navigated these choices across dozens of enterprise implementations.Migration strategy: Moving from legacy Connect apps requires specialized knowledge of both frameworks and the pitfalls that derail projects.Custom development: Tailoring Forge apps to enterprise workflows demands hands-on experience with real-world use cases and organizational complexity.Risk mitigation: Expert guidance prevents costly architectural mistakes that become exponentially expensive to fix later.Competitive advantage: Professional implementation unlocks Forge's full platform potential faster than trial-and-error approaches.Customized training: We deliver hands-on Forge development training tailored to your specific setup, team size, and business goals.Long-term partnership: As your Atlassian partner, we provide ongoing support, maintenance, and strategic guidance as your needs evolve. At ij-solutions, we're not just Marketplace app developers, we're your long-term Atlassian partner, bringing deep expertise and practical solutions gained from countless enterprise implementations.The Bottom Line: Forge Decision CriteriaThinking about what to do next? Consider Forge when you need:Custom apps deeply integrated with Atlassian workflowsEnterprise-grade security without infrastructure overheadRapid development cycles with minimal operational burdenFuture-proof solutions aligned with Atlassian's roadmap The question isn't whether to adopt Forge, it's whether to lead the transition or scramble to catch up.Let ij-solutions help you design a smart, cost-effective Forge development strategy and unlock the full potential of cloud-native enterprise app development that scales with your business.  #### When Jira Automation Isn't Enough: How to Avoid Overload and Handle Complex Workflows with Apps At ij-solutions, we've spent years helping Jira teams — from fast-moving product squads to enterprise IT departments — design workflows that actually scale. One pattern comes up again and again: teams start with Jira automation, get great results, and then hit a wall. Rules slow down. Queues back up. What was saving time is now creating work.This article explains how to recognise that breaking point, and when a dedicated Jira app is the right tool for the job.The Automation Sweet Spot — and Where It EndsJira's built-in automation is genuinely powerful. Triggers, conditions, and actions let you eliminate repetitive tasks without writing a line of code. For straightforward workflows — auto-assigning issues, sending notifications, updating statuses — it delivers real value with minimal overhead.But powerful tools have limits. As rule sets grow and data volumes increase, execution queues start to back up, rate limits get hit, and your Jira instance begins to struggle. At that point, adding more automation rules doesn't solve the problem. It deepens it.What Does Jira Automation Overload Actually Look Like?Automation overload doesn't announce itself clearly. It creeps in. Here are the signs to watch for:Execution delays — Rules that fired instantly now take minutes or hours to complete.Queue backlogs — Hundreds or thousands of executions stack up waiting to run.Stuck "In progress" rules — Automations stall indefinitely without completing or failing.Performance degradation — The Jira UI becomes slow during issue updates while rules process in the background.Rate limiting errors — "Too Many Requests" messages appear with increasing frequency.Duplicate triggers — Rules fire multiple times for the same event, creating inconsistent data.Debugging nightmares — Interconnected rule chains become impossible to troubleshoot reliably.Manual babysitting — You're regularly disabling rules, clearing queues, and intervening in what should be automated. If several of these feel familiar, you've reached the breaking point that Jira automation wasn't designed to handle.When Should You Use an App Instead of Jira Automation?The honest answer: when complexity and scale make automation rules a liability rather than an asset. Here are the specific scenarios where a dedicated app makes more sense.Bulk operations with complex templatesAutomation can clone a single issue and update a few fields. But when you need to replicate dozens of related issues — each with custom fields, dependencies, assignees, components, and due dates — chaining together rules becomes a maintenance burden with its own failure modes. A purpose-built app handles this in a single, controlled operation.Enterprise-scale volumeJira Cloud's Standard plan allows around 1,700 automation rule executions per month. Enterprise teams processing hundreds of projects or running regular bulk operations can exhaust that quota quickly. Apps offload the processing, maintaining performance without burning through execution limits.Epic hierarchy cloning across projectsThis is one of the most common pain points we see. Cloning an entire initiative — preserving initiative/epic/story/subtask relationships, issue links, and custom field values — across project boundaries is not something Jira automation handles well. Even experienced Jira admins find themselves rebuilding relationships manually. An app like Epic Clone was built specifically for this.Cross-platform and multi-step conditional workflowsAutomation rules handle simple integrations. Orchestrating workflows across Jira, Confluence, Slack, and external systems — with proper error handling and conditional logic — requires more than rules can reliably provide.Automation vs. Apps: A Practical ComparisonAspectJira AutomationDedicated AppsCostIncluded with plan, but execution limits applyDirect subscription cost, tiered by user countComplexity ceilingSimple workflows work well; complex chains create maintenance overheadSpecialised features reduce admin burden at scaleScalabilityHits limits quickly; can degrade instance performanceOffloads processing; maintains performanceLong-term ROILower upfront cost, but hidden admin costs increase with complexityHigher direct cost, but better efficiency and reliability at scaleDo You Have to Choose One or the Other?No — and this is an important point. Automation and apps work well together.Epic Clone's REST API makes it possible to trigger app-powered cloning operations directly from a Jira automation rule. You write a simple rule that sends a web request to Epic Clone's API when a condition is met — say, the start of a new quarter, or when a specific issue type is created. Epic Clone handles the heavy lifting: replicating full hierarchies with all relationships intact, processing in the background, and modifying attributes in bulk. Want to automatically clone a specific Jira epic template every quarter? Set up a simple Jira automation rule that sends a web request to Epic Clone's API. Suddenly you've got the best of both worlds without the complexity overhead! The result is the responsiveness of native automation with the power of a dedicated app — without the complexity overhead.What Epic Clone Does That Automation Can'tEpic Clone is our Jira app for bulk cloning epics, issues, and full issue hierarchies. Here's what it handles that automation rules can't do reliably:Full hierarchy cloning with preserved relationshipsEpic Clone replicates entire structures — from top-level parent issues through all nested children — including issue links and parent-child relationships. No manual rebuilding required after the fact. Read more about issue hierarchy cloning in Jira. Bulk attribute modification during cloningRather than building separate rules for each field update, Epic Clone lets you modify target project, assignee, labels, components, due dates, and more in a single cloning operation. You decide exactly what gets cloned and what gets changed. Background processing without timeoutsThe cloning process runs in the background for up to 15 minutes, with attachments processed in parallel. Automation sequences typically timeout after a few minutes and can block other operations. Epic Clone doesn't. Frequently Asked QuestionsWhat are the execution limits for Jira automation?On Jira Cloud Standard, teams get approximately 1,700 rule executions per month. Premium and Enterprise plans have higher limits, but all tiers can hit performance degradation when complex rules run at scale.Can Jira automation clone an entire epic with all child issues?Not reliably. Native cloning creates a flat copy of a single issue. Chaining automation rules to clone a hierarchy often results in broken parent-child relationships and missing issue links, particularly when cloning across projects.When should I use Epic Clone instead of Jira automation for cloning?Use Epic Clone when you need to clone epics or issue hierarchies across projects, preserve all relationships and custom field values, modify multiple attributes during cloning, or process large volumes without hitting execution limits.Is Epic Clone compatible with Jira automation?Yes. Epic Clone's REST API can be triggered by a Jira automation rule, letting you combine automation's scheduling and conditional logic with Epic Clone's reliable hierarchy cloning.Finding the Right BalanceJira automation is the right choice for straightforward, lower-volume workflows. Use it for basic triggers and status updates, and monitor your execution metrics carefully as your rule set grows.When complexity and volume push past what automation handles well — particularly around bulk cloning, hierarchy preservation, and cross-project operations — that's the point to bring in a specialised app.At ij-solutions, we help Jira teams design workflows that hold up at enterprise scale. If you're hitting automation limits or struggling with complex cloning operations, Epic Clone is a good place to start.Get started today with a free trial of Epic Clone on the Atlassian Marketplace.Already using Epic Clone? See how teams use it to manage repeating project templates and sprint setups. ### Pages #### About us ij-solutions We’re young, we’re fun, and we know what you want. Since 2015, the Monsfer team has been on a mission to bring effortless, simple mobile payment options to the masses in a modern way. No more checks, no more bulky wallets. Just your mobile phone with one secure app that handles it all. Welcome to your new place to pay. Lorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has ex, no eum aliquid tibique petentium, agam mucius liberavisse eos id. Ut sea accumsan interpretaris, viderer pertinax repudiandae ne ius. the missionLorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has exore, noeum tibique petentium, agam mucius liberavisse Lorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has exore, noeum tibique petentium, agam mucius liberavisse The VisionLorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has exore, noeum tibique petentium, agam mucius liberavisse Lorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has exore, noeum tibique petentium, agam mucius liberavisse Meet the founders gary mintCo-Founder & CEO arin greyCo-Founder & CMO sara nielsCo-Founder & CTO investors Our office in NYC Lorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has exore, noeum tibique petentium, agam mucius liberavisse Lorem ipsum dolor sit amet, te has solet postea. Voluptua quaestio dissentias has exore, noeum tibique petentium, agam mucius liberavisse monsfer’s office Let's keep in touch Have a question before you ditch your checkbook and wallet? Feel free to reach out to us for any reason — we’re here to help! Contact Us #### Apps Epic Clone Clone entire epics in minutes, not hours Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More Project Milestones for Jira Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Projects Insight Edge Get an overview of all Jira projects with KPI analytics, dashboards, and key metrics Get an overview of your Jira projects to track important metrics, KPIs, and overall project health. Access analytics and action recommendations to support strategic, data-driven decisions and optimize project performance Learn More Duplicate Epic Seamlessly clone Jira epics, saving time and ensuring consistency with one click The perfect solution for Jira users seeking to streamline their workflows. With just one click, replicate entire Epics along with your chosen child issues. Learn More #### Blog Return to Home Blog Latest Insights Other popular articles Blog All Search Blog Filter by: #### Contact Us Address ij-solutions GmbH Singapurstraße 5 20457 Hamburg Germany E-Mail info@ij-solutions.com Linkedin Youtube #### Data Privacy Policy Datenschutzerklärung Allgemeiner Hinweis und Pflichtinformationen Benennung der verantwortlichen StelleDie verantwortliche Stelle für die Datenverarbeitung auf dieser Website ist:ij-solutions GmbHJonas MöhringerSingapurstraße 520457 HamburgDie verantwortliche Stelle entscheidet allein oder gemeinsam mit anderen über die Zwecke und Mittel der Verarbeitung von personenbezogenen Daten (z.B. Namen, Kontaktdaten o. Ä.).Widerruf Ihrer Einwilligung zur DatenverarbeitungNur mit Ihrer ausdrücklichen Einwilligung sind einige Vorgänge der Datenverarbeitung möglich. Ein Widerruf Ihrer bereits erteilten Einwilligung ist jederzeit möglich. Für den Widerruf genügt eine formlose Mitteilung per E-Mail. Die Rechtmäßigkeit der bis zum Widerruf erfolgten Datenverarbeitung bleibt vom Widerruf unberührt.Recht auf Beschwerde bei der zuständigen AufsichtsbehördeAls Betroffener steht Ihnen im Falle eines datenschutzrechtlichen Verstoßes ein Beschwerderecht bei der zuständigen Aufsichtsbehörde zu. Zuständige Aufsichtsbehörde bezüglich datenschutzrechtlicher Fragen ist der Landesdatenschutzbeauftragte des Bundeslandes, in dem sich der Sitz unseres Unternehmens befindet. Der folgende Link stellt eine Liste der Datenschutzbeauftragten sowie deren Kontaktdaten bereit: https://www.bfdi.bund.de/DE/Infothek/Anschriften_Links/anschriften_links-node.html.Recht auf DatenübertragbarkeitIhnen steht das Recht zu, Daten, die wir auf Grundlage Ihrer Einwilligung oder in Erfüllung eines Vertrags automatisiert verarbeiten, an sich oder an Dritte aushändigen zu lassen. Die Bereitstellung erfolgt in einem maschinenlesbaren Format. Sofern Sie die direkte Übertragung der Daten an einen anderen Verantwortlichen verlangen, erfolgt dies nur, soweit es technisch machbar ist.Recht auf Auskunft, Berichtigung, Sperrung, LöschungSie haben jederzeit im Rahmen der geltenden gesetzlichen Bestimmungen das Recht auf unentgeltliche Auskunft über Ihre gespeicherten personenbezogenen Daten, Herkunft der Daten, deren Empfänger und den Zweck der Datenverarbeitung und ggf. ein Recht auf Berichtigung, Sperrung oder Löschung dieser Daten. Diesbezüglich und auch zu weiteren Fragen zum Thema personenbezogene Daten können Sie sich jederzeit über die im Impressum aufgeführten Kontaktmöglichkeiten an uns wenden.SSL- bzw. TLS-VerschlüsselungAus Sicherheitsgründen und zum Schutz der Übertragung vertraulicher Inhalte, die Sie an uns als Seitenbetreiber senden, nutzt unsere Website eine SSL-bzw. TLS-Verschlüsselung. Damit sind Daten, die Sie über diese Website übermitteln, für Dritte nicht mitlesbar. Sie erkennen eine verschlüsselte Verbindung an der „https://“ Adresszeile Ihres Browsers und am Schloss-Symbol in der Browserzeile.Server-Log-DateienIn Server-Log-Dateien erhebt und speichert der Provider der Website automatisch Informationen, die Ihr Browser automatisch an uns übermittelt. Dies sind:Besuchte Seite auf unserer DomainDatum und Uhrzeit der ServeranfrageBrowsertyp und BrowserversionVerwendetes BetriebssystemReferrer URLHostname des zugreifenden RechnersIP-AdresseEs findet keine Zusammenführung dieser Daten mit anderen Datenquellen statt. Grundlage der Datenverarbeitung bildet Art. 6 Abs. 1 lit. b DSGVO, der die Verarbeitung von Daten zur Erfüllung eines Vertrags oder vorvertraglicher Maßnahmen gestattet.KontaktformularPer Kontaktformular übermittelte Daten werden einschließlich Ihrer Kontaktdaten gespeichert, um Ihre Anfrage bearbeiten zu können oder um für Anschlussfragen bereitzustehen. Eine Weitergabe dieser Daten findet ohne Ihre Einwilligung nicht statt.Die Verarbeitung der in das Kontaktformular eingegebenen Daten erfolgt ausschließlich auf Grundlage Ihrer Einwilligung (Art. 6 Abs. 1 lit. a DSGVO). Ein Widerruf Ihrer bereits erteilten Einwilligung ist jederzeit möglich. Für den Widerruf genügt eine formlose Mitteilung per E-Mail. Die Rechtmäßigkeit der bis zum Widerruf erfolgten Datenverarbeitungsvorgänge bleibt vom Widerruf unberührt.Über das Kontaktformular übermittelte Daten verbleiben bei uns, bis Sie uns zur Löschung auffordern, Ihre Einwilligung zur Speicherung widerrufen oder keine Notwendigkeit der Datenspeicherung mehr besteht. Zwingende gesetzliche Bestimmungen - insbesondere Aufbewahrungsfristen - bleiben unberührt.CookiesUnsere Website verwendet Cookies. Das sind kleine Textdateien, die Ihr Webbrowser auf Ihrem Endgerät speichert. Cookies helfen uns dabei, unser Angebot nutzerfreundlicher, effektiver und sicherer zu machen.Einige Cookies sind “Session-Cookies.” Solche Cookies werden nach Ende Ihrer Browser-Sitzung von selbst gelöscht. Hingegen bleiben andere Cookies auf Ihrem Endgerät bestehen, bis Sie diese selbst löschen. Solche Cookies helfen uns, Sie bei Rückkehr auf unserer Website wiederzuerkennen.Mit einem modernen Webbrowser können Sie das Setzen von Cookies überwachen, einschränken oder unterbinden. Viele Webbrowser lassen sich so konfigurieren, dass Cookies mit dem Schließen des Programms von selbst gelöscht werden. Die Deaktivierung von Cookies kann eine eingeschränkte Funktionalität unserer Website zur Folge haben.Das Setzen von Cookies, die zur Ausübung elektronischer Kommunikationsvorgänge oder der Bereitstellung bestimmter, von Ihnen erwünschter Funktionen (z.B. Warenkorb) notwendig sind, erfolgt auf Grundlage von Art. 6 Abs. 1 lit. f DSGVO. Als Betreiber dieser Website haben wir ein berechtigtes Interesse an der Speicherung von Cookies zur technisch fehlerfreien und reibungslosen Bereitstellung unserer Dienste. Sofern die Setzung anderer Cookies (z.B. für Analyse-Funktionen) erfolgt, werden diese in dieser Datenschutzerklärung separat behandelt.Abonnieren von KommentarenSie können als Nutzer unserer Website nach erfolgter Anmeldung Kommentare abonnieren. Mit einer Bestätigungs-E-Mail prüfen wir, ob Sie der Inhaber der angegebenen E-Mail-Adresse sind. Sie können die Abo-Funktion für Kommentare jederzeit über einen Link, der sich in einer Abo-Mail befindet, abbestellen. Zur Einrichtung des Abonnements eingegebene Daten werden im Falle der Abmeldung gelöscht. Sollten diese Daten für andere Zwecke und an anderer Stelle an uns übermittelt worden sein, verbleiben diese weiterhin bei uns.YouTubeFür Integration und Darstellung von Videoinhalten nutzt unsere Website Plugins von YouTube. Anbieter des Videoportals ist die YouTube, LLC, 901 Cherry Ave., San Bruno, CA 94066, USA.Bei Aufruf einer Seite mit integriertem YouTube-Plugin wird eine Verbindung zu den Servern von YouTube hergestellt. YouTube erfährt hierdurch, welche unserer Seiten Sie aufgerufen haben.YouTube kann Ihr Surfverhalten direkt Ihrem persönlichen Profil zuzuordnen, sollten Sie in Ihrem YouTube Konto eingeloggt sein. Durch vorheriges Ausloggen haben Sie die Möglichkeit, dies zu unterbinden.Die Nutzung von YouTube erfolgt im Interesse einer ansprechenden Darstellung unserer Online-Angebote. Dies stellt ein berechtigtes Interesse im Sinne von Art. 6 Abs. 1 lit. f DSGVO dar.Einzelheiten zum Umgang mit Nutzerdaten finden Sie in der Datenschutzerklärung von YouTube unter: https://www.google.de/intl/de/policies/privacy.Quelle: Datenschutz-Konfigurator von mein-datenschutzbeauftragter.de #### Epic Clone Epic duplication made effortless Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More Start Free Trial Clone entire epics in minutes, not hours No self-respecting product manager, project manager, or software engineer should have to duplicate issues in Jira one by one to kick off a new project.https://youtu.be/Ji-WBcryXH0 Start by creating a Jira epic template Create a Jira epic template with an approved issue structure (Epic - Issue - Sub-Tasks) that you can effortlessly clone and customize for any need. Bulk copy Jira issues in 3 easy clicks Get new projects up and running in the blink of an eye by cloning what you need—including child issues—across projects. Before cloning, modify parent issue fields to ensure consistency. No coding. No automation. No sweat. We believe anyone—not just Jira pros—can go beyond the limitations of Jira. Epic Clone works effortlessly as an enhancement to the Jira interface that you know and love, no technical expertise required. Ready to bulk clone in Jira? Pick a plan that best suits your needs and get started. Don’t see what you need? Talk to us. Learn More Contact Us We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it’s possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application’s performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It’s a very helpful tool for cloning the whole structure – Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it's possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application's performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It's a very helpful tool for cloning the whole structure - Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace See Epic Clone in action Get in touch with our team to find out just how effortlessly Epic Clone helps teams save time and energy. Book a Demo See the difference Discover why Epic Clone is the smarter choice over Jira’s native cloning—more power, less hassle. Learn More Epic Clone FAQ What is Epic Clone and when should I use it? Epic Clone is an Atlassian Marketplace app that allows you to clone an epic or any other parent item along with its child issues, sub‑tasks, and optionally linked items—all in one single clone operation. It’s ideal for establishing reusable templates (Epic → Issues → Sub‑Tasks) and quickly replicating them across different projects without manual work Can I access Epic Clone in every Jira work item? Cloud version: Yes, with Epic Clone you can copy work items of all types. It doesn't have to be an Epic. DC version: Epic Clone is currently only available in the Epic issue type. Can I clone from one project to another? Yes, copying items across projects is possible in both, Cloud and DC version of the app Are there any permissions-related constraints? Yes. Users must have the necessary permissions in the target project to: Create issues Add attachments (if attachments shall be copied) Assign items (if assignees need to be set) If you lack these permissions, cloning will fail or options may not appear. Can I restrict usage of Epic Clone to certain projects or users? Administrators can limit access to Epic Clone by: Project scope (e.g. only allow usage from template projects) Jira user groups (e.g. internal teams only) This helps ensure consistent practices and avoids accidental cloning by unauthorized users. How does Epic Clone differ from the native Jira clone function or other apps? Jira’s out-of-the-box clone only duplicates individual issues (epic or story) and doesn’t preserve downward hierarchy levels or relationships. Epic Clone enables bulk, hierarchical cloning in one single operation. It offers configuration before cloning (versus automation scripting) and is more flexible than alternatives like Jira Automation, which currently lacks robust support for nested hierarchies What use cases does Epic Clone solve better than Jira’s built-in clone or automation? Epic Clone is designed for scenarios where you need to: Reuse structured epics as templates, including all stories, sub-tasks, and links. Clone multiple issues (including hierarchy) in a single operation, without having to manually copy each item. Clone into other projects while customizing fields like summaries, labels, or assignees per use case. Perform bulk cloning without complex automation rules or scripting. For teams who frequently build similar work packages (product releases, client projects, onboarding flows), Epic Clone streamlines what would otherwise require multiple manual steps or advanced Jira configuration. Do I need to configure any custom fields or automation rules to use Epic Clone? No. Epic Clone works out-of-the-box. It automatically reads your existing field configurations for issues and epics. There’s no need to build automation rules or scripts. You can, however, customize field mappings or apply find-and-replace actions during the clone process to fine-tune the cloned data as needed. Can I use Epic Clone to create project templates? While Epic Clone doesn’t create new Jira projects itself, it allows you to set up a “template epic” (or a set of epics) in a designated project and then clone them into other projects as needed. This is often used as a lightweight alternative to Jira’s native project templates, especially for teams who want more flexible control over issue structure and content. Furthermore, project templates populated with work items is an enterprise only feature at the moment. How does Epic Clone handle custom fields during cloning? Epic Clone supports standard Jira system fields as well as custom fields, as long as: The target project has the same custom fields configured. The user performing the clone has permission to edit these fields. For unsupported or unmapped custom fields, Jira’s default values will apply in the cloned issues. You can review and adjust them during or after the cloning process. Is there a limit to how many issues I can clone at once? As the number of child issues isn't limited in Jira, you can clone as many items at once as are listed in a parent item or the downward hierarchy levels. Do I need to be a Jira Administrator to use Epic Clone? No, you don’t need Jira Admin rights to use Epic Clone. Any user with the following can clone: Create issue permissions in the target project. Access to view and edit the issues you wish to clone. Check out our other apps Project Milestones for Jira Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Deep dive into our approach #### EULA EULA As of November 1 2024, we’re using the Standard Agreement of the Atlassian Marketplace v1.0 from Bonterms that can be found here: Marketplace Transactions - Bonterms. The provider-specific terms and any additions to this agreement are defined in section 21. Additions for our Atlassian Data Center offerings are defined in section 22. Table of Contents Bonterms Standard Agreement for Marketplace Transactions (Version 1.0) Role of Bonterms: Bonterms publishes this Standard Agreement but is not a party to the Agreement created between Provider and Customer and has no responsibility to either for its use. Using this Standard Agreement 1.1 Standard Agreement. This Bonterms Standard Agreement for Marketplace Transactions (Version 1.0) (“Standard Agreement”) sets forth the terms and conditions under which Provider makes available Subscriptions to its Cloud Service or Provider Software (each, a “Product”) offered through a Listing on the Marketplace. Provider may (i) make additions to or modifications of this Standard Agreement (“Additional Terms”) or (ii) add Attachments by stating as such in its Listing. Any Additional Terms and any Attachments are collectively referred to as “Provider-Specific Terms.” Capitalized terms are defined in context or in Section 20 (Definitions).1.2 Entering the Agreement. Customer and Provider agree to this Standard Agreement and any Provider-Specific Terms (collectively, the “Agreement”) upon Customer’s first entry into an Order (“Effective Date”).1.3 Orders. As specified in the Marketplace, an Order may be between Customer and the Marketplace provider (or other reseller or agent of Provider) or directly with Provider. Each Order creates a separate Agreement between Provider and Customer but Orders do not become part of the Agreement.1.4 Order of Precedence. In the event of a conflict between the elements of the terms and conditions making up the Agreement, the order of precedence is: (i) any Amendment, (ii) Provider-Specific Terms and (iii) this Standard Agreement. Products 2.1 Cloud Service. Subject to this Agreement, Customer may use the Cloud Service for its own business purposes in accordance with the Permitted Use.2.2 Provider Software. Subject to this Agreement, Customer may install, copy and use the Provider Software for its own business purposes in accordance with the Permitted Use.2.3 Users. Customer may permit Users to use the Product on its behalf. Customer is responsible for provisioning and managing its User accounts, for its Users’ actions through the Product and for their compliance with this Agreement. Customer will ensure that Users keep their login credentials confidential and will promptly notify Provider upon learning of any compromise of User accounts or credentials. Customer Data 3.1 Use of Customer Data. Subject to this Agreement, Provider will access and use Customer Data solely to provide and maintain the Cloud Service, Support and Professional Services under this Agreement (“Use of Customer Data”). Use of Customer Data includes sharing Customer Data as Customer directs through the Cloud Service, but Provider will not otherwise disclose Customer Data to third parties except as permitted in this Agreement.3.2 Security. Provider will implement and maintain the Security Measures, if any, identified in the Provider-Specific Terms. If no Security Measures are identified, Provider will use appropriate technical and organizational measures designed to prevent unauthorized access, use, alteration or disclosure of Customer Data.3.3 DPA. The parties will adhere to the Data Protection Addendum (DPA), if any, identified in the Provider-Specific Terms.3.4 Usage Data. Provider may collect Usage Data and use it to operate, improve and support the Product and for other lawful business purposes, including benchmarking and reports. However, Provider will not disclose Usage Data externally unless it is (a) de-identified so that it does not identify Customer, its Users or any other person and (b) aggregated with data across other customers. Mutual Compliance with Laws Each party will comply with all Laws that apply to its performance under this Agreement. Support and SLA 5.1 Support. Provider will provide Support for the Product as described in any Support Policy identified in the Provider-Specific Terms.5.2 SLA. Provider will adhere to any Service Level Agreement (SLA) identified in the Provider-Specific Terms. Warranties 6.1 Mutual Warranties. Each party represents and warrants that:(a) it has the legal power and authority to enter into this Agreement, and(b) it will use industry-standard measures to avoid introducing Viruses into the Cloud Service.6.2 Performance Warranty.(a) Scope. Provider warrants that the Product will perform materially as described in the Documentation and that Provider will not materially decrease the overall functionality of the Cloud Service during the Subscription Term (the “Performance Warranty”).(b) Claim Report. Customer must report a breach of warranty in reasonable detail (“Claim”) within 30 days after discovering the issue in the Product (“Claim Period”).(c) Remedy. Within 30 days of receiving a verified Claim during the Claim Period (“Fix Period”), Provider will use reasonable efforts to correct or provide a reasonable workaround (“Fix”) for the Claim. If Provider fails to provide a Fix during the Fix Period, either party may on notice to the other terminate the Subscription as it relates to the nonconforming Product and Provider will refund to Customer any prepaid, unused fees for the terminated portion of the Subscription Term.(d) Exclusive Remedy. The procedures set forth in this Section 6.2 are Customer’s exclusive remedies and Provider’s sole liability for breach of the Performance Warranty.6.3 Disclaimers. Except as expressly set out in this Agreement, each party disclaims all warranties, whether express, implied, statutory or otherwise, including warranties of merchantability, fitness for a particular purpose, title and noninfringement. Provider’s warranties in this Section 6 do not apply to issues arising from Third-Party Platforms or misuse or unauthorized modifications of the Product. These disclaimers apply to the full extent permitted by Law. Usage Rules 7.1 Compliance. Customer (a) will comply with any Acceptable Use Policy (AUP) identified in the Provider-Specific Terms and (b) represents and warrants that it has all rights necessary to use Customer Data with the Cloud Service and grant Provider the rights to Customer Data specified in this Agreement, without violating third-party intellectual property, privacy or other rights. Between the parties, Customer is responsible for the content and accuracy of Customer Data.7.2 High-Risk Activities and Sensitive Data. Customer:(a) will not use the Product for High-Risk Activities,(b) will not submit Sensitive Data to the Cloud Service, and(c) acknowledges that the Product is not designed for (and Provider has no liability for) use prohibited in this Section 7.2.7.3 Restrictions. Customer will not and will not permit anyone else to: (a) sell, sublicense, distribute or rent the Product (in whole or part), grant non-Users access to the Product or use the Product to provide a hosted or managed service to others, (b) reverse engineer, decompile or seek to access the source code of the Product, except to the extent these restrictions are prohibited by Laws and then only upon advance notice to Provider, (c) copy, modify, create derivative works of or remove proprietary notices from the Product, (d) conduct security or vulnerability tests of the Cloud Service or interfere with its operation, (e) circumvent access restrictions to any Product or (f) use the Product to develop a product or service that competes with the Product. Third-Party Platforms To the extent offered by Provider, Customer may choose to enable integrations or exchange Customer Data with Third-Party Platforms. Customer’s use of a Third-Party Platform is governed by its agreement with the relevant provider, not this Agreement, and Provider is not responsible for Third-Party Platforms or how their providers use Customer Data. Professional Services Provider will perform Professional Services as described in a Statement of Work, which may identify additional terms or milestones for the Professional Services. Customer will give Provider timely access to Customer Materials reasonably needed for Professional Services, and Provider will use the Customer Materials only for purposes of providing Professional Services. Subject to any limits in a Statement of Work, Customer will reimburse Provider’s reasonable travel and lodging expenses incurred in providing Professional Services. Customer may use code or other deliverables that Provider furnishes as part of Professional Services only in connection with Customer’s authorized use of the Product under this Agreement. Fees Fees will be as stated in the Order and payment terms are as set forth in the Order or terms of the Marketplace. Suspension Provider may suspend Customer’s access to the Cloud Service and related services due to a Suspension Event, but where practicable will give Customer prior notice so that Customer may seek to resolve the issue and avoid suspension. Provider is not required to give prior notice in exigent circumstances or for a suspension made to avoid material harm or violation of Law. Once the Suspension Event is resolved, Provider will promptly restore Customer’s access to the Cloud Service in accordance with this Agreement. “Suspension Event” means (a) Customer’s account is 30 days or more overdue, (b) Customer is in breach of Section 7 (Usage Rules) or (c) Customer’s use of the Cloud Service risks material harm to the Cloud Service or others. Term and Termination 12.1 Subscription Terms. Each Subscription Term will last for an initial 12-month period unless the Order states otherwise.12.2 Term of Agreement. This Agreement starts on the Effective Date and continues until the end of all Subscription Terms, unless sooner terminated in accordance with its terms. If no Subscription is in effect, either party may terminate this Agreement for any or no reason with notice to the other party.12.3 Termination. Either party may terminate this Agreement (including all Subscriptions) if the other party (a) fails to cure a material breach of this Agreement within 30 days after notice, (b) ceases operation without a successor or (c) seeks protection under a bankruptcy, receivership, trust deed, creditors’ arrangement, composition or comparable proceeding, or if such a proceeding is instituted against that party and not dismissed within 60 days.12.4 Data Export and Deletion.(a) During a Subscription Term, Customer may export Customer Data from the Cloud Service (or Provider will otherwise make the Customer Data available to Customer) as described in the Documentation.(b) After termination or expiration of this Agreement, within 60 days of request, Provider will delete Customer Data and each party will delete any Confidential Information of the other in its possession or control.(c) Nonetheless, the recipient may retain Customer Data or Confidential Information in accordance with its standard backup or record retention policies or as required by Law, subject to Section 3.2 (Security), Section 16 (Confidentiality) and any DPA.12.5 Effect of Termination.(a) Customer’s right to use the Product, Support and Professional Services will cease upon any termination or expiration of this Agreement, subject to this Section 12.(b) The following Sections will survive termination or expiration of this Agreement: 3.4 (Usage Data), 6.3 (Disclaimers), 7 (Usage Rules), 12.4 (Data Export and Deletion), 12.5 (Effect of Termination), 13 (Intellectual Property), 14 (Limitations of Liability), 15 (Indemnification), 16 (Confidentiality), 19 (General Terms) and 20 (Definitions).(c) Except where an exclusive remedy is provided, exercising a remedy under this Agreement, including termination, does not limit other remedies a party may have. Intellectual Property 13.1 Reserved Rights. Neither party grants the other any rights or licenses not expressly set out in this Agreement. Except for Provider’s express rights in this Agreement, as between the parties, Customer retains all intellectual property and other rights in Customer Data and Customer Materials provided to Provider. Except for Customer’s express rights in this Agreement, as between the parties, Provider and its licensors retain all intellectual property and other rights in the Product, Professional Services deliverables and related Provider technology.13.2 Feedback. If Customer gives Provider feedback regarding improvement or operation of the Product, Support or Professional Services, Provider may use the feedback without restriction or obligation. All feedback is provided “AS IS” and Provider will not publicly identify Customer as the source of feedback without Customer’s permission. Limitations of Liability 14.1 General Cap. Each party’s entire liability arising out of or related to this Agreement will not exceed the General Cap.14.2 Consequential Damages Waiver. Neither party will have any liability arising out of or related to this Agreement for indirect, special, incidental, reliance or consequential damages or damages for loss of use, lost profits or interruption of business, even if informed of their possibility in advance.14.3 Exceptions and Enhanced Cap. Sections 14.1 (General Cap) and 14.2 (Consequential Damages Waiver) will not apply to Enhanced Claims or Uncapped Claims. For all Enhanced Claims, each party’s entire liability will not exceed the Enhanced Cap.14.4 Nature of Claims. The waivers and limitations in this Section 14 apply regardless of the form of action, whether in contract, tort (including negligence), strict liability or otherwise and will survive and apply even if any limited remedy in this Agreement fails of its essential purpose.14.5 Liability Definitions.“Enhanced Cap” means three times (3x) the General Cap.“Enhanced Claims” means Provider’s breach of Section 3.2 (Security) or either party’s breach of Section 3.3 (DPA).“General Cap” means amounts paid or payable by Customer to Provider under this Agreement in the 12 months immediately preceding the first incident giving rise to liability.“Uncapped Claims” means (a) the indemnifying party’s obligations under Section 15 (Indemnification), (b) either party’s infringement or misappropriation of the other party’s intellectual property rights, (c) any breach of Section 16 (Confidentiality), excluding breaches related to Customer Data and (d) liabilities that cannot be limited by Law. Indemnification 15.1 Indemnification by Provider. Provider, at its own cost, will defend Customer from and against any Provider-Covered Claims and will indemnify and hold harmless Customer from and against any damages or costs awarded against Customer (including reasonable attorneys’ fees) or agreed in settlement by Provider resulting from the Provider-Covered Claims.15.2 Indemnification by Customer. Customer, at its own cost, will defend Provider from and against any Customer-Covered Claims and will indemnify and hold harmless Provider from and against any damages or costs awarded against Provider (including reasonable attorneys’ fees) or agreed in settlement by Customer resulting from the Customer-Covered Claims.15.3 Indemnification Definitions.“Customer-Covered Claim” means a third-party claim arising from Customer’s breach or alleged breach of Section 7.1 (Compliance) or 7.2 (High-Risk Activities and Sensitive Data).“Provider-Covered Claim” means a third-party claim that the Product, when used by Customer as authorized in this Agreement, infringes or misappropriates a third party’s intellectual property rights.15.4 Procedures. The indemnifying party’s obligations in this Section 15 are subject to receiving from the indemnified party: (a) prompt notice of the claim (but delayed notice will only reduce the indemnifying party’s obligations to the extent it is prejudiced by the delay), (b) the exclusive right to control the claim’s investigation, defense and settlement and (c) reasonable cooperation at the indemnifying party’s expense. The indemnifying party may not settle a claim without the indemnified party’s prior approval if settlement would require the indemnified party to admit fault or take or refrain from taking any action (except regarding use or nonuse of the Product when Provider is the indemnifying party). The indemnified party may participate in a claim with its own counsel at its own expense.15.5 Mitigation. In response to an infringement or misappropriation claim, if required by settlement or injunction or as Provider determines necessary to avoid material liability, Provider may: (a) procure rights for Customer’s continued use of the Product, (b) replace or modify the allegedly infringing portion of the Product to avoid infringement, without reducing the Product’s overall functionality or (c) terminate the affected Subscription and refund to Customer any prepaid, unused fees for the terminated portion of the Subscription Term.15.6 Exceptions. Provider’s obligations in this Section 15 do not apply to claims resulting from (a) modification or unauthorized use of the Product, (b) use of the Product in combination with items not provided by Provider, including Third-Party Platforms or (c) Provider Software other than the most recent release, if Provider made available (at no additional charge) a newer release that would avoid infringement.15.7 Exclusive Remedy. This Section 15 sets out the indemnified party’s exclusive remedy and the indemnifying party’s sole liability regarding third-party claims of intellectual property infringement or misappropriation covered by this Section 15. Confidentiality 16.1 Use and Protection. As recipient, each party will (a) use Confidential Information only to fulfill its obligations and exercise its rights under this Agreement, (b) not disclose Confidential Information to third parties without the discloser’s prior approval, except as permitted in this Agreement and (c) protect Confidential Information using at least the same precautions recipient uses for its own similar information and no less than a reasonable standard of care.16.2 Permitted Disclosures.(a) Personnel. The recipient may disclose Confidential Information to its employees, agents, contractors and other representatives having a legitimate need to know (including, for Provider, the subcontractors referenced in Section 19.9), provided it remains responsible for their compliance with this Section 16 and they are bound to confidentiality obligations no less protective than this Section 16.(b) Required by Law. The recipient may disclose Confidential Information (including Customer Data) to the extent required by Law. If permitted by Law, the recipient will give the discloser reasonable advance notice of the required disclosure and reasonably cooperate, at the discloser’s expense, to obtain confidential treatment for the Confidential Information.16.3 Exclusions. These confidentiality obligations do not apply to information that the recipient can document (a) is or becomes public knowledge through no fault of the recipient, (b) it rightfully knew or possessed, without confidentiality restrictions, prior to receipt from the discloser, (c) it rightfully received from a third party without confidentiality restrictions or (d) it independently developed without using or referencing Confidential Information.16.4 Remedies. Breach of this Section 16 may cause substantial harm for which monetary damages are an insufficient remedy. Upon a breach of this Section 16, the discloser is entitled to seek appropriate equitable relief, including an injunction, in addition to other remedies. Publicity Neither party may publicly announce this Agreement without the other party’s prior approval or except as required by Laws. Trials and Betas Use of Trials and Betas is permitted only for Customer’s internal evaluation during the period designated in the Order (or if not designated, 30 days). Either party may terminate Customer’s use of Trials and Betas at any time for any reason. Trials and Betas may be inoperable, incomplete or include features never released. Notwithstanding anything else in this Agreement, Provider offers no warranty, indemnity, SLA or Support for Trials and Betas and its liability for Trials and Betas will not exceed US$1,000. General Terms 19.1 Assignment. Neither party may assign this Agreement without the prior consent of the other party, except that either party may assign this Agreement, with notice to the other party, in connection with the assigning party’s merger, reorganization, acquisition or other transfer of all or substantially all of its assets or voting securities. Any non-permitted assignment is void. This Agreement will bind and inure to the benefit of each party’s permitted successors and assigns.19.2 Governing Law and Courts.(a) The Governing Law governs this Agreement and any action arising out of or relating to this Agreement, without reference to conflict of law rules. The parties will adjudicate any such action in the Courts and each party consents to the exclusive jurisdiction and venue of the Courts for these purposes.(b) Unless otherwise specified in the Provider-Specific Terms, the “Governing Law” is the laws of the State of California and the “Courts” are the federal and state courts located in San Francisco, California.19.3 Notices.(a) Except as set out in this Agreement, notices, requests and approvals under this Agreement must be in writing to the addresses specified by Provider and Customer and will be deemed given: (1) upon receipt if by personal delivery, (2) upon receipt if by certified or registered U.S. mail (return receipt requested), (3) one day after dispatch if by a commercial overnight delivery service or (4) upon delivery if by email.(b) Provider will specify its notice address through the Listing or Product and Customer will specify its notice address through the Order or other method designated by Provider. Either party may update its notice address with notice to the other. Provider may also send operational notices through the Product.19.4 Entire Agreement.(a) This Agreement is the parties’ entire agreement regarding its subject matter and supersedes any prior or contemporaneous agreements regarding its subject matter. In this Agreement, headings are for convenience only and “including” and similar terms are to be construed without limitation. Terms in purchase orders used by Customer will not amend or modify this Agreement; any such documents are for administrative purposes only. This Agreement may be executed in counterparts (including electronic copies and PDFs), each of which is deemed an original and which together form one and the same agreement.(b) Neither the provider of the Marketplace (except if operating as the Provider) nor Bonterms, the publisher of this Standard Agreement, is a party to this Agreement and neither will have any liability or responsibility to either Provider or Customer in connection with use of this Standard Agreement.19.5 Amendments.(a) Any amendments to this Agreement must be in writing and signed by each party’s authorized representatives (an “Amendment”). Amendments become part of this Agreement.(b) Orders may contain Use Restrictions but do not amend or modify any part of this Agreement.19.6 Operational Changes. With notice to Customer, Provider may modify the AUP, Security Measures, SLA or Support Policy to reflect new features or changing practices, but the modifications may not be retroactive or materially decrease Provider’s overall obligations during a Subscription Term.19.7 Waivers and Severability. Waivers must be signed by the waiving party’s authorized representative and cannot be implied from conduct. If any provision of this Agreement is held invalid, illegal or unenforceable, it will be limited to the minimum extent necessary so the rest of this Agreement remains in effect.19.8 Force Majeure. Neither party is liable for a delay or failure to perform this Agreement due to a Force Majeure. If a Force Majeure materially adversely affects the Product for 15 or more consecutive days, either party may terminate the affected Subscription upon notice to the other and Provider will refund to Customer any prepaid, unused fees for the terminated portion of the Subscription Term. However, this Section 19.8 does not limit Customer’s obligations to pay fees owed.19.9 Subcontractors. Provider may use subcontractors and permit them to exercise Provider’s rights and fulfill Provider’s obligations, but Provider remains responsible for each subcontractor’s compliance with this Agreement and for Provider’s overall performance under this Agreement. This does not limit any additional terms for subprocessors under a DPA.19.10 Independent Contractors. The parties are independent contractors, not agents, partners or joint venturers.19.11 No Third-Party Beneficiaries. There are no third-party beneficiaries to this Agreement.19.12 Open Source. Provider Software may include third-party open source software (“Open Source”) as listed in the Documentation or by Provider upon request. Customer acknowledges that its license to use any Open Source will be the Open Source license applicable to such code and not the license to Provider Software in Section 2.2 (Provider Software) above to the extent required by such Open Source license.19.13 Export. Each party (a) will comply with all export and import Laws in performing this Agreement and (b) represents and warrants that it is not listed on any U.S. government list of prohibited or restricted parties or located in (or a national of) a country subject to a U.S. government embargo or designated by the U.S. government as a “terrorist-supporting” country. Customer will not submit to the Cloud Service any data controlled under the U.S. International Traffic in Arms Regulations.19.14 Government Rights. To the extent applicable, the Product is “commercial computer software” or a “commercial item” for purposes of FAR 12.212 and DFARS 227.7202. Use, reproduction, release, modification, disclosure or transfer of the Product is governed solely by the terms of this Agreement, and all other use is prohibited. Definitions “Acceptable Use Policy” or “AUP” is defined in Section 7.1 (Compliance).“Additional Terms” is defined in Section 1.1 (Standard Agreement).“Agreement” is defined in Section 1.2 (Entering the Agreement).“Amendment” is defined in Section 19.5 (Amendments).“Attachments” means any AUP, Security Measures, SLA, Support Policy or other policies specified in the Provider-Specific Terms.“Cloud Service” means Provider’s proprietary software as a service (SaaS) or cloud service as identified in the applicable Listing.“Confidential Information” means information disclosed by or on behalf of one party (as discloser) to the other party (as recipient) under this Agreement, in any form, which (a) the discloser identifies to recipient as “confidential” or “proprietary” or (b) should be reasonably understood as confidential or proprietary due to its nature and the circumstances of its disclosure. Provider’s Confidential Information includes technical or performance information about the Product, and Customer’s Confidential Information includes Customer Data.“Courts” is defined in Section 19.2 (Governing Law and Courts).“Customer” means the party placing the Order.“Customer Data” means any data, content or materials that Customer (including its Users) submits to its Cloud Service accounts, including from Provider Software or Third-Party Platforms.“Customer Materials” means materials and resources that Customer makes available to Provider in connection with Professional Services.“Data Protection Addendum” or “DPA” is defined in Section 3.3 (DPA).“Documentation” means Provider’s standard usage documentation for the Product. Documentation is included in the definition of “Product” unless otherwise specified.“Force Majeure” means an unforeseen event beyond a party’s reasonable control, such as a strike, blockade, war, pandemic, act of terrorism, riot, third-party Internet or utility failure, refusal of government license or natural disaster, where the affected party takes reasonable and customary measures to avoid or mitigate such event’s effects.“Governing Law” is defined in Section 19.2 (Governing Law and Courts).“High-Risk Activities” means activities where use or failure of the Product could lead to death, personal injury or environmental damage, including life support systems, emergency services, nuclear facilities, autonomous vehicles or air traffic control.“Laws” means all laws, regulations, rules, court orders or other binding requirements of a government authority that apply to a party.“Listing” means Provider’s description of its Product (and any related Support) and Subscriptions in a listing on the Marketplace that designates use of this Standard Agreement.“Marketplace” means the application marketplace or app store on which Provider has published a Listing and made available Subscriptions to their Product.“Open Source” is defined in Section 19.12.“Order” means an order by Customer for a Subscription that is entered into through the Marketplace.“Permitted Use” means use of a Product in accordance with the applicable Subscription, any Use Restrictions and the Documentation.“Product” is defined in Section 1.1 (Standard Agreement).“Professional Services” means training, migration or other professional services that Provider furnishes to Customer related to the Product.“Provider” means the party providing the Product.“Provider Software” means Provider’s proprietary installed software or apps identified in the applicable Listing.“Provider-Specific Terms” is defined in Section 1.1 (Standard Agreement).“Security Measures” is defined in Section 3.2 (Security).“Sensitive Data” means (a) patient, medical or other protected health information regulated by the Health Insurance Portability and Accountability Act (as amended and supplemented) (“HIPAA”), (b) credit, debit, bank account or other financial account numbers, (c) social security numbers, driver’s license numbers or other government ID numbers and (d) special categories of data enumerated in European Union Regulation 2016/679, Article 9(1) or any successor legislation.“Service Level Agreement” or “SLA” is defined in Section 5.2 (SLA).“Standard Agreement” is defined in Section 1.1 (Standard Agreement).“Statement of Work” means a statement of work for Professional Services that is signed by the parties and references this Agreement.“Subscription” means the right for Customer to access the Product and any related Support as described in a Listing and the applicable Order.“Subscription Term” means the term for a Subscription as identified in the Order.“Support” means support for the Product as described in Section 5.1 (Support).“Support Policy” is defined in Section 5.1 (Support).“Suspension Event” is defined in Section 11 (Suspension).“Third-Party Platform” means any product, add-on or platform not provided by Provider that Customer uses with the Cloud Service.“Trials and Betas” mean access to the Product on a free or trial basis or to particular features designated by Provider as “beta” or “early access.”“Usage Data” means Provider’s technical logs, data and learnings about Customer’s use of the Product, but excluding Customer Data.“Use Restrictions” means user, seat, copy, installation, license or other scope of use restrictions for the Product as specified in a Listing or Order.“User” means anyone that Customer allows to use its accounts for the Product, who may include (a) employees, advisors and contractors of Customer and (b) others if permitted in this Agreement, the Documentation or a Listing.“Virus” means viruses, malicious code or similar harmful materials. Provider-Specific Terms 21.1 Replacement of section 19.2 (b): the “Governing Law” is the laws of Germany and the “Courts” are the federal and state courts located in Hamburg, Germany.21.2 The Service Level Agreements (SLA) and the Support Policy mentioned in section 5.1 can be found at the following page: ij-solutions Service Level Agreements21.3 The Acceptable Use Policy of cloud services provided by ij-solutions mentioned in section 7 can be found at the following page: Acceptable Use Policy (AUP)21.4 In addition to section 3.1 of this agreement (“Use of Customer Data”), the Provider may use the company name of the Customer as well as the provided contact email address for the following purposes:(a) The Provider may send emails to the Customer contact with information regarding the Product during an active Subscription or Trial period and a period of 6 months after its end. The Customer can deny this right at the time of the conclusion of this agreement as well as at any time afterward by submitting a request via email to support@ij-solutions.atlassian.net.(b) The Provider may name the company name of the Customer as a referential customer and display the Customer company logo on the website https://ij-solutions.com as of conclusion of this agreement. The Customer can deny this right at the time of the conclusion of this agreement as well as at any time afterward by submitting a request via email to support@ij-solutions.atlassian.net, requesting the references to be deleted. Upon receipt of such a request, the Provider will remove any reference to the Customer within 30 days and make no further reference to the Customer. Amendments for Atlassian Data Center 22.1 Subject matter of the Data Center offering(a) Our Atlassian Data Center solution matches the Cloud services outlined in section 2.1, plus it comes with extra downloadable Software from the Atlassian Marketplace for installation on the Customer's Atlassian Data Center instance.(b) The Customer is entitled to download a previous version from the Atlassian Marketplace instead of the most current version. However, we do not guarantee compatibility with other software and the security of such older versions.22.2 Customer obligations to cooperate(a) The Customer shall be obliged to keep the Software up to date at all times during the term of the agreement, in particular to install upgrades and new versions of the Software immediately after we have notified the Customer accordingly. To be informed by us about the latest upgrades and versions of the Software, the Customer undertakes to log in to the "Watch" function. Without a corresponding registration, a Customer can always view the latest version of a Software under the history version, which can be found for the relevant product on the Atlassian Marketplace under "Versions > See all versions". We inform the Customer about critical security updates in any case without the latter having to take any action; the information is sent to the contact data entered by the Customer on https://my.atlassian.com. We shall only provide our support services if the Software is up to date with the latest version delivered by us.(b) The Customer shall be solely responsible for setting up a functional hardware and Software environment for the Software of a size that is sufficient to take into account the additional load caused by the subject matters covered by the agreement. Same is true for the network environment that allows access to the Cloud services required for the Data Center offering.(c) The Customer shall thoroughly test the Software before use to verify any defects and usability in the existing hardware and Software configuration. This also applies to Software which the Customer receives within the scope of warranty and, where applicable, maintenance.(d) The Customer shall comply with our Company's instructions for the installation and operation of the Software; it shall regularly keep up to date with our company's current instructions published on the documentation website https://docs.ij-solutions.com(e) The Customer shall bear any disadvantages and additional costs resulting from a breach of these obligations.22.3 Data backup by the Customer; Liability for loss of data(a) The Customer shall take appropriate measures for the event that the Software does not work properly in whole or in part (e.g. daily data backup, fault diagnosis, regular checking of data processing results). In particular, the Customer shall carry out a complete backup of all system and application data immediately before each update or installation of a newer version of the Software. The data backups shall be stored in such a way that the backed-up data may be restored at any time.(b) Our company shall not be liable for the loss of Customer data insofar as the damage is due to the Customer failing to carry out data backups and thereby ensuring that lost data can be restored with reasonable effort, contrary to its obligation under section 22.3 (a). In all other respects, section 14 shall apply.22.4 End of Life compatibilityFor a period of two years, we support versions of our Software older than the most current version only by providing security patches for critical security vulnerabilities ("End of Life"). We expressly point out that beyond this period of time, neither compatibility with the current basic Software of Atlassian (e.g. Jira) nor sufficient security of such previous versions is guaranteed. If we provide updates, they will be compatible with versions of Atlassian's Software (e.g. Jira) released within the last two years. #### Global Styles Global Styles Colors Fonts buttons This page previews Global Fonts and Colors for this Kit. Changes made in Site Settings will be displayed here. Global Colors SYSTEM Primary Secondary Text accent custom White BG Accent #2/White Transparent Grey Element/BG Pink Element/BG Blue Element App Store Icon Global Fonts SYSTEM Primaryabcd Secondaryabcd Text #1Looking to change global styles?Click on top left menu in sidebarand then select Site Settings. Accent #1abcd custom Hero/CTA Titleabcd 4rd Level Titleabcd 5th Level Title/Person Nameabcd Accent #2/Nav Menuabcd Text #2 Bigabcd Copyright Text/Person Titleabcd 404 Titleabcd Buttons & Links Buttons and links inherit their style from Global Fonts and Colors settings in Site Settings. Main CTA button 2nd CTA button Underline Accent This is Hyperlink #### Home Atlassian headaches, solved Unleash productivity with Jira project management tools and solutions you’ve always dreamed of. No technical expertise? No problem. Our Solutions Introducing Epic Clone An epic solutionto epic duplication Think starting a new project in Jira shouldn’t involve spending entire days manually recreating Jira issues? We agree. Epic Clone Bulk clone Jira issues across projects with Epic Clone Get projects up and running in the blink of an eye by cloning entire epics—along with child issues and copy custom field values—in minutes, not hours. Learn More Check out our other apps Project Milestones for Jira Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Jira teams love Epic Clone Goodbye repetition, hello precision Bulk clone exactly what you need, and nothing else. Managers and engineers alike get to boost productivity and clarity while focusing on what matters most. Save precious time Eliminate human error Reduce bloat No coding required Learn More We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it’s possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application’s performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It’s a very helpful tool for cloning the whole structure – Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it's possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application's performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It's a very helpful tool for cloning the whole structure - Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace Your solutions are just one call away In need of hands-on Jira consulting services? Have a Jira task management headache you wish we could fix? Let’s talk. Contact Us Deep dive into our approach #### Imprint Imprint Information provided according to Sec. 5 German Telemedia Act (TMG):ij-solutions GmbHSingapurstraße 520457 HamburgGermanyE-Mail: info@ij-solutions.comManaging Director: Jonas Möhringer, Ibrahim FarhanResponsible for content: Jonas Möhringer Register entry Registering court: Amtsgericht HamburgRegistration number: HRB 159376 Sales Tax Identification Number Sales tax identification number subject to §27 a Sales tax law: DE 327 829 977 Consumer Dispute Resolution ij-solutions GmbH does not commit to nor is it obliged to participate in the alternative dispute resolution for consumer disputes in front of a consumer dispute resolution entity. Disclaimer of Liability Liability for Contents As service providers, we are liable for own contents of these websites according to Sec. 7, paragraph 1 German Telemedia Act (TMG). However, according to Sec. 8 to 10 German Telemedia Act (TMG), service providers are not obligated to permanently monitor submitted or stored information or to search for evidences that indicate illegal activities.Legal obligations to removing information or to blocking the use of information remain unchallenged. In this case, liability is only possible at the time of knowledge about a specific violation of law. Illegal contents will be removed immediately at the time we get knowledge of them. Liability for links Our offer includes links to external third party websites. We have no influence on the contents of those websites, therefore we cannot guarantee for those contents. Providers or administrators of linked websites are always responsible for their own contents.The linked websites had been checked for possible violations of law at the time of the establishment of the link. Illegal contents were not detected at the time of the linking. A permanent monitoring of the contents of linked websites cannot be imposed without reasonable indications that there has been a violation of law. Illegal links will be removed immediately at the time we get knowledge of them. Copyright Contents and compilations published on these websites by the providers are subject to German copyright laws. Reproduction, editing, distribution as well as the use of any kind outside the scope of the copyright law require a written permission of the author or originator. Downloads and copies of these websites are permitted for private use only. The commercial use of our contents without permission of the originator is prohibited.Copyright laws of third parties are respected as long as the contents on these websites do not originate from the provider. Contributions of third parties on this site are indicated as such. However, if you notice any violations of copyright law, please inform us. Such contents will be removed immediately. Trademark Notices Bitbucket, Confluence, Jira, Atlassian are registered trademarks of Atlassian Pty Ltd.Microsoft, Edge and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.Chrome is a registered trademark of Google Inc.Firefox is a registered trademark of Mozilla CorporationOracle and Java are registered trademarks of Oracle and/or its affiliatesMac®, OS X®, Safari® and Apple® are registered trademarks of Apple Inc. External Pages This Imprint is also applicable for the following external Pages:https://marketplace.atlassian.com/vendors/1216765https://docs.ij-solutions.com #### Native Jira Cloning vs Epic Clone VS. Epic Clone vs. Native Jira Cloning Create tailored Jira templates, easily clone Jira projects with issues, or clone epics and all their stories to another project—saving you time and energy like never before. See the difference 3 reasons to choose our cloning solution Epic Clone offers a smarter, faster way to clone Jira issues. Unlike the native Jira cloning and other complex apps, Epic Clone is designed to be intuitive for every Jira user, regardless of experience level. Fully Flexible Cloning — Tailor Every Detail With Epic Clone, you’re not just duplicating work — you’re adapting it to your needs. Effortlessly clone Jira epics and all their stories while modifying key fields like summary, assignee, due date, and more. This flexibility ensures your copied issues are perfectly tailored to each project, team, or timeline — saving you from manual edits and keeping your workflow seamless. Effortless Cloning of Entire Work Structures Epic Clone makes it simple to replicate entire issue hierarchies and bulk clone issues in Jira, no matter how complex. With just a few clicks, you can copy full project plans, including all linked stories, tasks, and sub-tasks — while staying in control. Select exactly which items you want to clone and easily skip the ones you don’t need, creating a clean, customized copy every time. Cross-Project Cloning Made Simple Epic Clone lets you seamlessly copy epics and their child issues across different projects. Whether you need to clone a Jira project with issues, move work items from a template project to a live environment, or reuse proven structures for a follow-up project, Epic Clone makes it effortless. Save time, maintain consistency, and set up new projects faster with ready-to-go, tailored issue sets. What is the best cloning option in Jira? While Atlassian has recently enhanced Jira’s native cloning, limitations remain—often raising the question what is not included while cloning an issue in Jira. Epic Clone addresses these gaps, offering a more powerful and complete solution for project setup and template-based cloning with unmatched flexibility, efficiency, and control. Feature Epic Clone Native Jira Cloning Clone work items and direct children in one go ✓ Yes. Copy a parent issue together with its child issues or sub-tasks in one action✓ Yes. Copy a parent issue together with its child issues or sub-tasks in one action Replicate entire work item hierarchies with multiple levels ✓ Yes. Copy issue structures that go beyond just parent and child item level✗ No. Not supported Decide for each child item whether to clone it or not ✓ Yes. Configure each cloned hierarchy individually and include only the items you need✗ No. Not supported, if child item cloning is selected, all child issues are copied along with the parent Edit fields like summary, assignee, or due date for each issue during cloning ✓ Yes. Summary, Assignee, Original Estimate and Due date can be modified for each work item. For Stories, the story point field can be set additionally✗ No. Not supported. Only parent summary and assignee fields can be updated. Decide for each child item whether to clone attachments ✓ Yes. While respecting project permissions, users can individually decide for which work itmes attachments shall be cloned✗ No. Not supported. Only for the parent it can be set whether attachments should be cloned or not Change sequence of child items during cloning and move sub-tasks between parents ✓ Yes. Users can shape the sequence of child items according to their individual needs by a simple drag & drop functionality✗ No. Not supported. The child items will have the same order than in the source issue Decide for each link of parent and child items whether to clone it or copy linked items as well ✓ Yes. Beside replication of the item links, it is also possible to clone the entire linked issues for the parent✗ No. Not supported. It is only possible to clone all item links of the parent or none of them Clone across projects ✓ Yes. With Epic Clone it is possible to copy work item hierarchies from one project to another. Project configuration and permissions are considered for cross-project cloning✗ No. Not supported. Cloning is only possible within the same project Define permissions for cloning ✓ Yes. Jira system administrators have full control to define in which projects Epic Clone should be available and which user groups have access to it. They can easily manage Jira clone permissions to ensure the right teams have access.✗ No. Not supported. Cloning one or multiple issues depends solely on the default create work item permission in a project, not on any specific Jira clone permissions. We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it’s possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application’s performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It’s a very helpful tool for cloning the whole structure – Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it's possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application's performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It's a very helpful tool for cloning the whole structure - Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace See Epic Clone in action Get in touch with our team to find out just how effortlessly Epic Clone helps teams save time and energy. Book a Demo Check out our other apps Project Milestones for Jira Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Deep dive into our approach #### Project Milestones Improve project management in Jira Plan and track milestones and split large projects into smaller phases Learn More Start Free Trial Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Project milestones in every Jira project Split long-running projects into several phases and mark them as completed when done. Map issues automatically based on due date Project issues can be mapped to the milestones - either manually or automatically based on due date. Show project context in issues Display in issue view if issue is mapped to a milestone. Add, edit or remove milestone directly from issue. Ready to track your Project Milestones in Jira? Pick a plan that best suits your needs and get started. Don’t see what you need? Talk to us. Learn More Contact Us See Project Milestones in action Get in touch with our team to find out just how effortlessly Project Milestones helps teams to plan and track their projects. Book a Demo Check out our other apps Epic Clone Clone entire epics in minutes, not hours Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More Projects Insight Edge Overview & KPI Analytics for Jira Gain the edge and boost project success with AI-driven insights, KPI analytics, and performance dashboards—all in one app! Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Deep dive into our approach #### Projects Insight Edge Overview & KPI Analytics for Jira Get an overview of your Jira projects to track important metrics, KPIs, and overall project health. Access analytics and action recommendations to support strategic, data-driven decisions and optimize project performance Learn More Start Free Trial Get an overview of all Jira projects with KPI analytics and key metrics Gain the edge and boost project success with AI-driven insights, KPI analytics, and performance dashboards—all in one app! Project Overview & KPI Dashboard with Insights Get an overview of your Jira projects to track important metrics, KPIs, and overall project health. Access analytics and action recommendations to support strategic, data-driven decisions and optimize project performance Track Trends & Analyze KPIs Over Time Monitor project performance with KPI analysis. Identify trends, compare past data, and track improvements or risks over time. Gain insights to measure progress and make informed decisions to shape your future strategy. Full Control with Admin Settings & Security Administrators have full control over user access, metric thresholds, and scheduled analyses. Manage settings with ease while ensuring security and compliance, keeping your project insights protected within Jira. Ready to boost project success in Jira? Pick a plan that best suits your needs and get started. Don’t see what you need? Talk to us. Learn More Contact Us See Projects Insight Edge in action Get in touch with our team to find out just how effortlessly Projects Insight Edge helps teams to visualize what is going on in their projects. Book a Demo Check out our other apps Epic Clone Clone entire epics in minutes, not hours Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Project Milestones Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More Deep dive into our approach #### Resources Return to Home Blog, Use Cases, and more Latest Insights Other popular articles Blog Consulting Epic Clone Features Forge How to All Search Blog Consulting Epic Clone Features Forge How to Jira Filter by: #### Solutions Unlock the Full Potential of Your Atlassian Tools We’re not just Marketplace app developers — we’re your long-term Atlassian partner. From consulting services and training to custom app development, we help teams streamline workflows, automate processes, and build better software. Book a free Consultation Optimize and Scale Your Atlassian Tools We provide expert consulting services for Jira, Confluence, Bitbucket, and other Atlassian products, both in Cloud and Data Center. Whether you’re just getting started or scaling across teams, we support you with:Initial setup and best-practice configurationProcess automation with Jira Automation and ScriptRunnerMarketplace app selection and integrationCustom workflows, permissions, and schemesMigration and updates for Atlassian productsPerformance tuning and admin support Book a Consulting Call Empower Your Team with Practical Atlassian Knowledge We offer live, hands-on training for all experience levels — from project managers and end users to Jira admins and developers. Our sessions are tailored to your tools, team size, and goals. Topics include:Jira & Confluence essentialsAdvanced administration & user managementAgile project management with JiraForge development training: build your own apps using Atlassian ForgeCustomized training programs for your specific setup Request a Training Session Build Tailored Atlassian Apps That Fit Your Workflow Need functionality beyond what’s available in the Marketplace? We design and develop custom apps that integrate seamlessly into your toolchain, support your unique use cases, and scale with your teams. Our development services include:Forge-based cloud app developmentCustom Data Center pluginsTool-specific integrations (Jira, Confluence, Bitbucket, etc.)Internal apps that fill feature gaps and fit your specific needsLong-term support & maintenance Let's talk about your Idea Why Work With Us? We know the real-world challenges Atlassian admins and users face — and we’ve solved them countless times. You can benefit directly from that experience. As your partner, we bring deep expertise, practical solutions, and a strong customer-first mindset. Verified Atlassian Marketplace Partner Proven success across Atlassian Cloud and Data Center products Experts in Forge and custom app development Fast, flexible, and focused on your outcomes Let’s Solve Your Atlassian Challenges Together In need of hands-on Jira consulting services? Have a Jira task management headache you wish we could fix? Let’s talk. Contact Us Our Apps on the Marketplace Epic Clone Clone entire epics in minutes, not hours Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More Project Milestones for Jira Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Projects Insight Edge Get an overview of all Jira projects with KPI analytics, dashboards, and key metrics Get an overview of your Jira projects to track important metrics, KPIs, and overall project health. Access analytics and action recommendations to support strategic, data-driven decisions and optimize project performance Learn More Duplicate Epic Seamlessly clone Jira epics, saving time and ensuring consistency with one click The perfect solution for Jira users seeking to streamline their workflows. With just one click, replicate entire Epics along with your chosen child issues. Learn More We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it’s possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application’s performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It’s a very helpful tool for cloning the whole structure – Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace We were looking for a plugin to manage our Epics in JIRA and first found the free plugin of the same vendor which is sufficient depending on your use case. However this plugin offers a lot more functions which simplify the cloning a lot. For example it's possible to change many fields, exclude certain sub-tasks etc. during the process per ticket. Support from the vendor is quick and friendly, thanks for providing the plugin. Customer Review Atlassian Marketplace This apps now provides the required functionality our organization needs to duplicate epics and all their children. There was a a couple of features missing initially, but after working with their support team, they quickly turned around the additional features we needed which were to duplicate child issues into their originating source project a nd to expose custom icons. I could not be more please with the application's performance and most of all the kindness, understanding and response to enhancing their product to meet our needs Customer Review Atlassian Marketplace It's a very helpful tool for cloning the whole structure - Epics, with selected Stories and Sub-tasks, all together. It simply does the job, without any unexpected issues. Additionally, it has some extra features, like adding prefix or postfix, which helps identifying cloned items. If you clone a lot of items in Jira, then I recommend using the Epic Clone! Customer Review Atlassian Marketplace Deep dive into our approach #### Use Cases Return to Home Use Cases Latest Insights Other popular articles All Search Filter by: #### User Absence Planner Out of office planning for Jira Schedule absences, automate issue reassignment, track availability and improve absence notices Learn More Start Free Trial Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Streamlined Absence Planning, Setting & Overview Easily define out of office times with start/end date, type (e.g. holiday, business trip) and ooo message. Display your and your team's upcoming absences, set deputy and whether to auto-assign and comment during absence. Smart Issue Assignment Automation Automatically reassign and comment issues during absences. Ensure continuous workflows by setting up an alternate user for your tasks. You decide if issues are automatically commented or assigned during your absence. User Availability Overview in every Jira Issue Instantly see who's available or out of office in every issue. Supports assignee, reporter, and user custom fields for a seamless project management experience. Definition by user or globally which fields to display. Ready to plan your out-of-office times in Jira? Pick a plan that best suits your needs and get started. Don’t see what you need? Talk to us. Learn More Contact Us See User Absence Planner in action Get in touch with our team to find out just how effortlessly User Absence Planner helps teams to plan and track their out of office times in Jira. Book a Demo User Absence Planner FAQ What is User Absence Planner for Jira and when should I use it? The User Absence Planner is a Jira app that helps teams manage employee availability by tracking absences such as vacations, sick days, remote work, and other leave types—all directly within Jira. It’s perfect for improving team planning, resource management, and sprint forecasting. How do I install the User Absence Planner in my Jira instance? As an administrator, you can install the app directly from the Atlassian Marketplace. Go to Apps -> Explore more apps, search for User Absence Planner, and click Try it free. Alternatively, visit the official app documentation for more guidance. Is the app available for Jira Cloud and Jira Data Center? Yes, there are versions available for Jira Cloud and Jira Data Center. Can I define custom absence types (e.g. parental leave, training, work from home)? Yes. You can define unlimited custom absence types to suit your company’s specific needs. The following absence types are available by default and can be modified as needed: Business trip Holiday Sickness Conference Trade fare participation Long term leave Other Does the app offer a calendar view? Currently, only the DC version provides a calendar view. However, we have it on the roadmap for the Cloud version as well. Can I restrict who sees absences? Yes. You can configure visibility settings to control who can view or manage user absences—helping protect sensitive leave information when necessary. Does this app integrate with Jira Projects, Boards, or Issues? Absences are visible in Jira issues, while the appearance is a little bit different for Cloud and DC version: Cloud version: See a comprehensive overview of availability of users in user fields like assignee or reporter. The overview can be accessed via a separate section in the items sidebar DC version: An user availability indication is displayed right next to the user avatar in all user fields or user mentions (e.g. in comment or description). Furthermore, you can see more information when opening the user profile information in an issue. Can I define a colleague who takes over my issues during an absence? Yes, you can define an alternate user for your absences and decided whether you want to have items assigned to you automatically reassigend to that user or commented on. How is user data stored and is it secure? Cloud version: As an Atlassian Cloud app, User Absence Planner complies with Atlassian security and data privacy standards. All data is stored securely and handled according to GDPR compliance and Atlassian app security best practices. The app is built with Atlassian Forge and holds the Cloud Fortified and Runs on Atlassian badges. This means that it runs completely on Atlassian infrastructure and no data leaves your Cloud instance at any time. DC version: The app runs in your Jira Data Center installation and all data is securely stored in your Jira database. What permissions are required to use the app? Users must be authenticated Jira users. App access and permissions can be controlled via specific app settings and controlled for Jira projects, groups or individual users. How much does the app cost? Pricing depends on the number of Jira users and is available on the Atlassian Marketplace listing. A 30-day free trial is also available. Is support included? Yes. All paid versions include support, updates and maintenance. You can reach out at any time through the ij-solutions support portal. Can I try the app before purchasing? Absolutely. A 30-day free trial is available via the Atlassian Marketplace, with no obligation to purchase. Check out our other apps Epic Clone Clone entire epics in minutes, not hours Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More Projects Insight Edge Overview & KPI Analytics for Jira Gain the edge and boost project success with AI-driven insights, KPI analytics, and performance dashboards—all in one app! Learn More Project Milestones Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More Deep dive into our approach ### My Templates #### 3 Posts Template URL: https://ij-solutions.com/?elementor_library=elementor-loop-item-7 #### 404 Page 404 Sorry, we couldn't find the page you are looking for... Return to Home #### All Posts Template URL: https://ij-solutions.com/?elementor_library=elementor-loop-item-4 #### Blog Post Template Return to Home Table of Contents Author Tags Share this Article #### Default Kit URL: https://ij-solutions.com/?elementor_library=default-kit #### Elementor Loop Item #407 URL: https://ij-solutions.com/?elementor_library=elementor-loop-item #### Elementor Loop Item #778 URL: https://ij-solutions.com/?elementor_library=elementor-loop-item-3 #### Footer There is always a solution Quick Links Legal https://ij-solutions.com/ai Linkedin Youtube #### Global Styles Page Global Styles Colors Fonts buttons This page previews Global Fonts and Colors for this Kit. Changes made in Site Settings will be displayed here. Global Colors SYSTEM Primary Secondary Body text accent custom Pale Blue BG1 Pale Blue BG2 White BG/Accent Transparent Semi Transparent Overlay Global Fonts SYSTEM Primaryabcd Secondaryabcd body textLooking to change global styles?Click on top left menu in sidebarand then select Site Settings. accent textabcd custom Hero headlineabcd Accent Underlinedabcd Name Titleabcd Testimonials Textabcd Text Underlinedabcd Bigger Textabcd Buttons & Links Buttons and links inherit their style from Global Fonts and Colors settings in Site Settings. Main CTA button Underline Accent This is Hyperlink #### Header Menu Contact us #### Latest Post Template Read More #### Other articles template URL: https://ij-solutions.com/?elementor_library=elementor-loop-item-6 #### Product Page Template Epic duplication made effortless Create Jira epic templates, copy Jira issues to another project, and save time and energy like never before. Learn More Start Free Trial Clone entire epics in minutes, not hours No self-respecting product manager, project manager, or software engineer should have to duplicate issues in Jira one by one to kick off a new project. Start by creating a Jira epic template Create a Jira epic template with an approved issue structure (Epic - Issue - Sub-Tasks) that you can effortlessly clone and customize for any need. Bulk copy Jira issues in 3 easy clicks Get new projects up and running in the blink of an eye by cloning what you need—including child issues—across projects. Before cloning, modify parent issue fields to ensure consistency. No coding. No automation. No sweat. We believe anyone—not just Jira pros—can go beyond the limitations of Jira. Epic Clone works effortlessly as an enhancement to the Jira interface that you know and love, no technical expertise required. Ready to bulk clone in Jira? Pick a plan that best suits your needs and get started. Don’t see what you need? Talk to us. Learn More Contact Us Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Add Your Heading Text Here Add Your Heading Text Here Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Add Your Heading Text Here Add Your Heading Text Here Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Add Your Heading Text Here Add Your Heading Text Here Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Add Your Heading Text Here Add Your Heading Text Here Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Add Your Heading Text Here Add Your Heading Text Here Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Add Your Heading Text Here Add Your Heading Text Here See Epic Clone in action Get in touch with our team to find out just how effortlessly Epic Clone helps teams save time and energy. Book a Demo Check out our other apps Project Milestones for Jira Define, plan, and schedule agile project milestones Split long-running projects into phases for better project tracking in Jira. Perfect for classic project management, agile software development, and service management projects. Learn More User Absence Planner Don't let absences slow your team down Out of office? Keep your team members informed by adding planned absence times like holidays or business trips to your Jira user profile, and even include a short message. Learn More Deep dive into our approach #### Search Results Template URL: https://ij-solutions.com/?elementor_library=search-results-template #### Testimonials Template Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Lorem ipsum Lorem ipsum