Customers have installed this add-on in at least 56 active instances.
    by Botron SoftwareAtlassian Verified
    Botron Software is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Server 6.3.4 - 7.3.6
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    Botron Software supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.

    Release and Program Management Platform

    Release and Program Management Platform

    Lifecycle Process

    Release Calendars

    Status, Metrics, Coordination

    Create and manage repeatable and reliable processes for different teams and departments that include stages, gates, milestones, checklists. The release scope can be defines using Projects, Agile boards, Epics and others.

    Release Calendars are the central place where releases are visualized. The user can create multiple calendars and choose which releases are shown. Highly interactive, it allows the user to view and update the release.

    Accurate Status and Risk factor are determined using user defined metrics with historic trends and in-depth analysis of the changes over-time. Deliverables such as quality goals, checklist, approvals allow coordination.

    More details

    Botron's Cycle Control revolutionizes how Agile and traditional organizations manage releases.

    Fully integrated in JIRA, it is the first Release and Program Management platform that provides full control of the release/program process using:

    • stages
    • quality gates
    • milestones
    • checklists
    • approvals
    • status and risk indicators

    The release scope can be defined in a bottom-up fashion to be any combination of multiple JIRA projects, versions, components, JIRA Agile boards, Epics or sprints. Cycle control will automatically roll-up all data from these containers.

    An accurate read of project status and risk indicators is available using:

    • real-time user-defined metrics
    • historic trends
    • in-depth analysis of the changes between two dates provides the user with visibility into the dynamics of the release activities

    Release Calendars are the central place where releases are visualized.

    User reviews

    Sign in to write a review
    by Atlassian Sales on 2017-02-06
    This makes the release control process so much easier for clients to work with. The biggest struggle is knowing when a release cycle starts and who will be the hand off. Status and metrics are easy and the trending feature really works when you have historical data which you will accumulate over time. The calendaring features allows users to be able to plan and visually see what is being release and by whom. Clients like the visibility and they really like the product. I have worked with the founder in my previous life and he has an excellent understanding of release management which brings depth and structure to this product.
    2 out of 3 found this review helpful
    Was this review helpful?YesNo


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on is technically available across the whole JIRA instance. Therefore the above guidelines for the license tier still apply.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    Botron Software is an vendor, committed to providing support for their add-ons at least 8 hours a day, 5 days a week.

    Vendor support resources


    Find out how this add-on works.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.


    Version 2.5.1 JIRA Server 6.3.4 - 7.3.6 Released 2017-05-18


    Bug fixes


    • Fixed bug where agile sprint scope entries are not visible in certain situations.
    • Fixed bug where Cycle internal caches were not correctly updated on data center.

    Release Notes


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Cycle Control via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Cycle Control. You're prompted to log into MyAtlassian. Cycle Control begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Cycle Control versions compatible with your instance, you can look through our version history page.

    Similar add-ons