119
Customers have installed this add-on in at least 119 active instances.
    by Redmoon Software Ltdfor JIRA Cloud
    Supported
    Redmoon Software Ltd supports this add-on.

    Get support

    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Create multiple Sub Tasks or Epic Issues easily. Define and use templates for commonly create sets of Sub Tasks / Issues

    Create multiple Sub Tasks or Epic Issues easily. Define and use templates for commonly create sets of Sub Tasks / Issues

    Templates can be defined for common Sub Task sets

    Adding or Editing Template

    Create templates in workflow transitions

    If you have common sets of Sub Tasks then these can be defined for a Project and easily reused.

    Sub Task Templates can be added or edit as required

    Add workflow transition post functions to automatically create sub tasks / Epic issues when transitioning an Issue

    More details

    This plugin allows you to easily create multiple Sub Tasks for a JIRA Issue or multiple Issues for an Agile Epic. Commonly created sets of Sub Tasks or Epic Issues can be created by defining Templates.

    .

    Features include:

    • Allow for the easy creation of multiple Sub Tasks
    • Defne templates for commonly used sets of Sub Tasks
    • Templates are defined for each Project or globally
    • Pre-specify Sub Task field values
    • Allow entry of additional information during the bulk Sub Task creation
    • Automatically copy fields from the parent Issue to the Sub Tasks (includes custom fields)
    • Specify values for summary, assignee, description, due date, original estimate, reporter and a custom field value
    • Easily create Issues for an Agile Epic using predefined templates.
    • Sub tasks or Epic Issues can be created as part of a workflow transition.
    • Easily create bulk linked issues using a template. This can be done in the issue or by workflow post function
    • Delete bulk Sub Tasks for a single screen.

    User reviews

    (10)
    Sign in to write a review »
    by Art Mack on 2016-08-23
    Seemed to be a very useful plugin but soon after installing it brought our system to a grinding halt with OOME. Had to get Atlassian support to disable it. OK so maybe it was a coincidence the first time I installed it and our system cratered. Having been convinced that that was the case I gave it a 2nd try. As soon as I installed it (takes a long time for this plugin) and tried to edit a template our system ground to a halt and rebooted.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Redmoon Software Ltd

    Investigating, waiting on information from customer.

    UPDATE: After talking to the user they said they it occurred when they were trying to edit the a template. Cloud plugins have no code that runs on the JIRA instance, just in the web browser and on our servers. At the time of editing a template the users browser will ask for a list of field values (Issue Types, priorities etc), custom fields and a list of fields shown on the Create Issue screen. I can see no way that getting this information could possibly break JIRA but I have Atlassian to look into this anyway.

    UPDATE: I have copied the template that caused the problem to my own cloud environment and tried editing it there. Everything worked fine. The fact that this plugin has over 100 installs that have never caused this problem leads me to believe it is a problem with the JIRA instance, otherwise everyone would be having this problem

    UPDATE: There is a bug in JIRA (JRA-42282) that doesn't place limits on data retrieved when getting create screen information for all projects. If there are hundreds of projects and not enough memory then it will crash JIRA. Currently making a work around to stop this happening.

    UPDATE: Changed the plugin workaround the JIRA issue

    by Elung Wu on 2016-06-16
    I am using this to create bulk sub-tasks and also bulk stories. This is great for site deployments where you have a set of tasks that need to be done per site. Instead of copy/clone, we use this template. The developer is also very quick to respond.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Danielle Owens on 2016-02-04
    Since JIRA Cloud has a small amount of plugins compared to the Server version, I wasn't able to find anything to help me create subtasks in bulk. We started using this plugin a few weeks ago so far it's been able to help us create subtasks in bulk. The developer has been quick to fix any small issues as well which is amazing! Things you can do with this plugin: SUBTASK TEMPLATES * Create a template list of subtasks. * Make a copy of the template, alter it and then save it for future use. * In the templates you can add summary, description, priority, due date * In the templates you can add dues dates that auto populate depending on when you actually create the subtasks. Example, the due date would be entered as 5d so when the subtasks are created the due date will be five days from now. * In the templates you can add a description for each subtask and it supports JIRA Text Formatting * You can have many different templates saved. OTHER FEATURES * Create a bulk list of subtasks under a parent issue type with a few clicks. * What's nice is you can have the subtasks inherit the summary of the parent task, plus you can add your own text to the subtask summary.
    5 out of 5 found this review helpful
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does cloud add-on pricing work?

    Cloud pricing is subscription based. You are eligible for support and automatic version updates as long as your subscription is active.

    When your subscription renews each month, your pricing tier for host products and add-ons is automatically adjusted (as necessary) based on the number of users in your instance.

    If you've opted for annual billing for your host product, add-ons are also billed annually. Annual subscriptions for this add-on include a discount (12 months for the price of 10).

    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 cloud pricing tier?

    The cloud add-on tier is set automatically based on the maximum tier of the licensed JIRA applications on your instance. For example, if you have JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, your add-on tier is 50 users.

    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 cloud add-ons, you cannot extend your free evaluation period. All cloud add-ons are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the add-on.

    Support

    Paul Clark supports Sub Task Manager. You can visit the developer's homepage to get help.

    Go to the developer's site

    Versions

    JIRA Cloud Released 2016-11-22

    Summary

    Added bulk delete sub tasks, required scopes changed

    Details

    Added bulk delete sub tasks, required scopes changed:

    • Added: PROJECT_ADMIN, DELETE

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Find new add-ons screen loads.
    3. Locate Sub Task Manager.
    4. Click Free trial to download and install your add-on.
    5. You're all set! Click Close in the Installed and ready to go dialog.

    Similar add-ons