2
Customers have installed this add-on in at least 2 active instances.
    by Broken Buildfor JIRA Server 7.0.0 - 7.2.5
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Broken Build supports this add-on.

    Get support

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

    Define and enforce which subtask types users can create for parent issue

    Define and enforce which subtask types users can create for parent issue

    Define subtask types for issues

    Check issue types mapping in a project

    Enforce only valid subtask type selection

    Select which subtask types are allowed for particular standard issue type (e.g. Epic, Story or Bug). Each standard issue type can have a unique set of subtask types. The mapping works for custom issue types too.

    Check how issue types mapping affects a particular project. Some of the subtask types can be enabled in the mapping, but may be absent in project issue types.

    Based on the issue types mapping user would be able to create only those subtask types which are enabled for the parent issue

    More details

    When in your JIRA project there are a lot of different issue types are enabled you might want to reduce the list of subtask types which are available for the parent issue to simplify user experience with subtasks.

    Issue Subtask Types add-on enables you to define a mapping between parent issue type and it's subtask types and enforce user to select the type of subtask from the configured options only.

    This add-on joins the family of Issue Type Resolutions and Project Priorities add-ons in order to extend JIRA configuration of issue types, resolutions and priorities.

    Contact us via support@brokenbuild.net or service desk if you need help or have any questions.

    User reviews

    (1)Sign in to write a review »

    There are no reviews yet. Be the first to review this add-on.

    Pricing

    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.

    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

    Support

    Broken Build supports Issue Subtask Types for JIRA. You can visit the support site to get help.

    Get support

    Versions

    Version 1.0.1 JIRA Server 7.0.0 - 7.2.5 Released 2016-08-03

    Summary

    public release

    Installation

    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 Issue Subtask Types for JIRA 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 Issue Subtask Types for JIRA. You're prompted to log into MyAtlassian. Issue Subtask Types for JIRA 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.

    Similar add-ons