Installation
Quick start
Template syntax: Basic syntax • Special Keywords • Available fields • Custom fields
Validating templates
Managing templates: Create • Use • Edit • Remove • Import/Export
Examples
Additional features: Bulk operations • Rich text formatting • Dark mode
Frequently asked questions
This guide shows you how to use the Create multiple subtasks in Jira. You will learn the basics in minutes, understand template syntax, and see how dynamic keywords like @inherit, @unassigned, and @now work. In addition, we include validation tips, template management, and inspiring examples.
Installation
Before you can use the app, it must be installed in your Jira instance.
You can find the app on the Atlassian Marketplace.
How to request
If you are not a Jira administrator, you can request the app:
- Go to the app listing page at Atlassian Marketplace.
- Click Try it free.
- Select your Jira installation and click Request app.
- This will send a request to your Jira administrators to approve and install the app.
How to install
You must be a Jira administrator to install the app.
- Go to the app listing page at Atlassian Marketplace.
- Click Try it free.
- Select your Jira installation, click Review and then Start free trial.
- You will be notified via a success message once the app is installed.
Quick start: Create multiple subtasks in 2 minutes
Learn the basics by creating sample subtasks. This example demonstrates:
- Creating multiple subtasks at once
- Setting fields (description, assignee, due date, labels)
- Using special keywords (
@inherit,@unassigned,@now) - How validation errors are displayed
Steps:
1. Open any issue that supports subtasks.
2. Click the Apps -> Create multiple sub-tasks. Wait for a modal window to open.
3. Copy and paste this example:
#Development task / description:"Details [here|https://example.com]."
#Code review / assignee:"@inherit" / dueDate:"@now + 1d"
#Testing task / assignee:"@unassigned" / labels:"manual,automated"
#Failing sample / assignee:"unknown"
What you will see
After processing, the results window shows three tabs:
- Created sub-tasks – all successfully created items with their new Jira keys.
- Invalid sub-tasks – items that failed with clear reasons (for example, an unknown assignee).
- Raw input – exactly what you entered to help you compare and fix issues.
💡Tip: If some lines fail, correct only those lines and run again. This is faster than re-creating everything.
Template syntax for creating multiple subtasks
Templates use a simple, readable format. Each line represents a subtask. Use / to add fields. Separate multiple fields with additional /. Finally, separate subtasks with new lines.
Basic syntax
Start a subtask with # followed by its name, then /:
#I am a subtask name/Add a field after the slash:
#Field example/description:"I am description"Add multiple fields with more slashes:
#Multiple fields example/description:"I am description"/priority:"low"/reporter:"tech.user"Some fields accept multiple values (comma-separated):
#Multi argument field example/labels:"Demo,Discussion"Create multiple subtasks by placing each on its own line:
#Task 1 example/
#Task 2 example/description:"description"
#Task 3 example/dueDate:"2020-10-01"/estimate:"1d 3h 30m"Example: Story template
# Implementation / issueType:"Technical Subtask" / assignee:"[email protected]" / estimate:"3d"
# Code Review / issueType:"Technical Subtask" / assignee:"awaiting assignment" / estimate:"3h"
# Test Preparation / issueType:"Testing Subtask" / assignee:"awaiting test" / estimate:"1d 5h"
# Test case review / issueType:"Testing Subtask" / assignee:"[email protected]" / estimate:"30m"
# Test execution / issueType:"Testing Subtask" / assignee:"awaiting test" / estimate:"1d 3h 25m"Special keywords
Special keywords can be used in field values to create dynamic content or reference parent issue data.
Available keywords
| Keyword | Description | Applicable fields |
|---|---|---|
| @inherit | Copy value from parent issue | All fields except Issue type |
| @unassigned | Leave field unassigned | Assignee only |
| @now | Current date | Date fields only |
Using @inherit
The @inherit keyword copies field values from the parent issue to the subtask.
Examples
Creates a task named the same as parent issue with issue type Technical Subtask and same labels as parent issue. Please note that @inherit in the summary can’t be empty.
#@inherit/issueType:"Technical Subtask"/labels:"@inherit"Creates a task named ‘Task’ with the same labels, priority and custom field CustomDate as parent issue.
#Task/labels:"@inherit"/priority:"@inherit"/CustomDate:"@inherit"Concatenate text
Text fields such as summary, description, or any custom text field can now concatenate given values with parent text values. @inherit can even be used multiple times in the same field value.
Creates a task with some field values concatenated with parent task values.
#Task @inherit/description:"@inherit This is subtask."/CustomTextField:"@inherit - text A, @inherit - text B"Join collections
Collection fields such as fixVersion, components, or any custom collection fields can now join given elements with parent elements.
Creates a task with two specified components (Component1, Component2) and also all parent components.
#Task / components: "Component1, @inherit, Component2"Using @unassigned
The @unassigned keyword explicitly leaves the assignee field empty.
#Code review/assignee:"@unassigned"/description:"Pending assignment"Date field modifiers
Date fields support mathematical modifiers to calculate dates relative to a reference point. You can add or subtract days (d) or weeks (w) from any date value.
Syntax
- [date]+[number][unit]- Add time to a date
- [date]-[number][unit] – Subtract time from a date
Available units
- d – days
- w – weeks
💡Tip: One week equals seven days (1w = 7d).
Examples
| Value | Result |
|---|---|
| @now+5d | 5 days from today |
| @now-2w | 2 weeks ago |
| @inherit+3d | 3 days after parent’s due date |
| @inherit-1w | 1 week before parent’s due date |
| 2025-12-01+7d | 7 days after 1st December 2025 |
💡Tip: When using @inherit with date modifiers (e.g., @inherit+5d), the field will only be set if the parent issue has a due date. Otherwise, the field remains empty.
Available fields
These standard Jira fields can be used when creating subtasks. All fields are optional except for the summary.
| Field | Syntax | Example | Notes |
|---|---|---|---|
| Summary | summary | #Test preparation/ #@inherit/ | Required field. Use @inherit to copy from parent. |
| Description | description:”value” | #Test prep/description:”@inherit and this is a standard test prep subtask.” #Test prep/description:”This is a multiline\n\n description.” #Test prep/description:”This is description with the [link|https://example.com?q1=param1#fragment].” | Supports rich text formatting and multiline content. |
| Assignee | assignee:”value” | #Task/assignee:”[email protected]” #Task/assignee:”@inherit” #Task/assignee:”@unassigned” | Use email, account ID, or full name. Special values: @inherit, @unassigned. |
| Reporter | reporter:”value” | #Task/reporter:”[email protected]” | Use email, account ID, or full name. |
| Issue type | issueType:”value” | #Task/issueType:”Technical Subtask” | Must be a valid subtask type in your project. |
| Priority | priority:”value” | #Task/priority:”High” #Task/priority:”@inherit” | Chosen priority needs to exist. |
| Time estimate | estimate:”value” | #Task/estimate:”2d 3h 30m” #Task/estimate:”1w” | Format: weeks (w), days (d), hours (h), minutes (m). |
| Due date | dueDate:”value” | #Test prep/dueDate:”2025-12-31″ #Test exec/dueDate:”@inherit+5d” #Impl/dueDate:”@now+12″ | Format: YYYY-MM-DD. Supports date modifiers (+/-) with days (d) or weeks (w). |
| Fix versions | fixVersions:”value1,value2″ | #Task/fixVersions:”v2.0,v2.1″ | Chosen fix versions need to exist. Accepts multiple arguments. |
| Labels | labels:”value1,value2″ | #Task/labels:”backend,urgent” #Task/labels:”@inherit,new-feature” | Comma-separated list. Can mix inherited and new labels. |
| Component | components:”value1,value2″ | #Task/components:”UI,Backend” | Comma-separated list. Components must exist in the project. |
| Watchers | watchers:”value1,value2″ | #Task/watchers:”[email protected]” | Comma-separated list of users. Use email, account ID, or full name. |
💡Tip: All Available fields except the Issue Type support the @inherit keyword.
💡Tip: Field names are case-insensitive. Values within quotes preserve their case.
Custom fields
Custom fields must be configured in your Jira space before use.
Check your space settings (⚙️ → Work items → Fields) to verify field availability and configuration.
🚨 Important: Custom field names and values are case-sensitive and must match your Jira configuration exactly.
Supported custom field types
| Field type | Syntax | Examples | Notes |
|---|---|---|---|
| Short text | FieldName:”value” | #Task/Environment:”Production” | Single line text, no formatting |
| Paragraph | FieldName:”value” | #Task/Test Steps: “1. Open application\n2. Click login \n3. Verify result” #Task/Acceptance Criteria:”h3. Criteria\n* Feature is *fully tested*\n* [Docs|https://docs.url.com] updated” | Supports rich text formatting and multiline content |
| Date picker | FieldName: “YYYY-MM-DD” | #Task/Release Date:”2025-12-31″ | Date only, no time component |
| Date time picker | FieldName: “YYYY-MM-DDTHH:MM+ZZZZ” | #Task/Deploy Time:”2025-01-31T14:30+0000″ | Include timezone offset (e.g., +0000 for UTC). Called “Timestamp” in team-managed projects. |
| Number field | FieldName:”number” | #Task/Story Points:”8″ | Whole numbers or decimals |
| Labels | FieldName: “label1 label2” | #Task/Tags:”frontend performance” | Space-separated, no commas |
| Select list (single choice) | FieldName:”option” | #Task/Environment:”Production” | Must match existing option exactly. Called “Dropdown” in team-managed projects. |
| Select list (multiple choices) | FieldName: “option1,option2” | #Task/Affected Systems:”BE,DB,API” | Comma-separated list |
| Checkboxes | FieldName: “option1,option2” | #Task/Features:”Login,Admin,Export” | Comma-separated list. Team-managed projects only. |
| User picker | FieldName:”user” | #Task/Reviewer:”[email protected]” | Use email, account ID, or full name. Supports multiple users with comma separation. Called “People” in team-managed projects. |
| Radio buttons | FieldName:”option” | #Task/Severity:”High” | Single selection only. Company-managed projects only. |
| URL field | FieldName:”url” | #Task/Gallery:”https://img.com” | Must be valid URL format. Company-managed projects only. |
| Group picker | FieldName:”group” | #Task/Team:”developers” | Single or comma-separated for multiple. Company-managed projects only. |
| Project picker | FieldName:”project” | #Task/Related Project:”WEB” | Use project key. Company-managed projects only. |
| Version picker | FieldName:”version” | #Task/Target Version:”2.0″ | Single or comma-separated for multiple. Company-managed projects only. |
| Select list (cascading) | FieldName: “parent,child” | #Task/Category:”Hardware,Laptop” | Parent and child separated by comma. Company-managed projects only. |
| Text field (read only) | FieldName:”value” | #Task/Generated ID:”AUTO-12345″ | Can be set during creation but not edited later. Company-managed projects only. |
💡Tip: Replace “FieldName” with your actual custom field name as configured in Jira. Some field types are only available in specific project types.
Validating templates
Template validation checks your syntax before creating subtasks, helping you identify and fix errors early. Access this feature via the Validate template button in the Create multiple subtasks view, or in the user and project template management views.
What gets validated:
The validator checks the following syntax rules:
| Rule | Description | Example |
|---|---|---|
| Subtask separation | Each subtask must start on a new line | ✅ #Task 1/⛔ #Task 1/ #Task 2/ |
| Subtask format | Each subtask must begin with # followed by a summary | ✅ #Code review/⛔ Code review/ |
| Field separation | Fields must be separated by forward slashes (/) | ✅ #Task/priority:"High"/assignee:"@inherit"⛔ #Task priority:"High" assignee:"@inherit" |
| Field format | Field values must be enclosed in quotes | ✅ issueType:"Technical Subtask"⛔ issueType:Technical Subtask |
When errors are found:
Errors appear in the error log and are highlighted in the template editor. Each error shows the line number or specific issue to help you fix it quickly.
💡 Tip: You can still create subtasks with validation errors by clicking Confirm, but it’s recommended to fix errors first to ensure subtasks are created as expected.
Validation notes:
- Whitespace: Extra spaces and blank lines are ignored during validation
- URLs in fields: URLs containing slashes (/) are handled correctly when enclosed in quotes
- Field names: The validator checks that field names match those available in your project
Managing templates
The app supports two types of templates to help streamline your workflow. These templates are essential for standardizing how you create multiple subtasks for common issue types:
Project templates are shared across all team members within a specific project. These are ideal for standardizing common workflows and ensuring consistency across your team. Only project administrators can create or modify project templates, but all project members can use them.
User templates are personal templates visible only to you. These are perfect for your individual workflows or frequently used task structures that may not apply to the entire team. You have full control to create, edit, and delete your own user templates.
Accessing template management
Project templates
- Go to space settings (you need project admin permissions to do that).
- On the left-hand side menu select Apps -> Sub-tasks templates.
User templates
- On the top right corner click on your profile icon.
- Select the Sub-tasks templates from the menu. Wait for a modal window to open.
Creating templates
Templates can be created in two ways:
From the template management view
- Go to the project or user templates page.
- Fill in the required fields:
– Template ID: Unique identifier of your template.
– Template content: Your subtasks (see syntax guide below).
– Template description (optional): A descriptive name to help you identify this template later (max 500 characters). - Click the Save template button.
💡Tip: if you have a template already selected and want to create a new template, click the New template button to clear the form.
Save as template while creating subtasks
When you’re in the Create multiple subtasks view, you can save your current work as a template by clicking the Save template button. This will save the template as a user template for your personal use. Enter a Template ID and optional Template description when prompted.
Using saved templates
Saved templates are accessible from both your profile and the Create multiple subtasks view. The Saved templates dropdown in the Create multiple subtasks view includes:
- Your user templates
- Project templates (if available in your project)
- Recent templates section showing the three most recently used templates
Editing templates
- Go to the project or user templates page.
- Select a template from available templates.
- Change the id or content of the selected template.
- Click the Save template button and confirm your template override decision.
Removing templates
- Go to the project or user templates page.
- Select a template from available templates.
- Click the Remove template button. On the popup confirm your template removal decision.
Importing and exporting templates
Templates can be exported from and imported to different Jira projects via the template management view. The system supports both individual and bulk operations using CSV files.
Exporting templates
Click export with no template selected for a full export.
Export a particular template by selecting it from the Saved templates dropdown
Importing templates
Ensure your CSV file has headers: Template ID, Template description, and Template content (comma-separated).
Export a template first for an example of correct .CSV syntax for successful imports.
Examples: templates for creating multiple subtasks
Sprint planning template:
#Backend Development / assignee:"@inherit" / estimate:"5d" / labels:"backend"
#Frontend Development / assignee:"@inherit" / estimate:"3d" / labels:"frontend"
#API Documentation / assignee:"@unassigned" / estimate:"4h" / labels:"documentation"
#Code Review / assignee:"@unassigned" / estimate:"1d" / dueDate:"@now+7d"
#QA Testing / assignee:"@unassigned" / estimate:"2d" / dueDate:"@now+9d"
#Deploy to Staging / assignee:"@inherit" / estimate:"2h" / dueDate:"@now+10d"
#User Acceptance Testing / assignee:"@unassigned" / estimate:"1d" / dueDate:"@now+11d"
#Deploy to Production / assignee:"@inherit" / estimate:"2h" / dueDate:"@now+14d"Bug fixing workflow:
#Reproduce Issue / assignee:"@inherit" / priority:"@inherit" / estimate:"2h"
#Root Cause Analysis / assignee:"@inherit" / priority:"@inherit" / estimate:"3h"
#Implement Fix / assignee:"@inherit" / priority:"@inherit" / estimate:"1d"
#Write Unit Tests / assignee:"@inherit" / estimate:"4h"
#Code Review / assignee:"@unassigned" / estimate:"2h"
#QA Verification / assignee:"@unassigned" / estimate:"3h"
#Update Documentation / assignee:"@inherit" / estimate:"1h" / labels:"documentation"Feature development template:
#Technical Design / issueType:"Technical Subtask" / assignee:"@inherit" / estimate:"1d" / labels:"design"
#Database Schema / issueType:"Technical Subtask" / assignee:"@inherit" / estimate:"4h"
#Backend Implementation / issueType:"Technical Subtask" / assignee:"@inherit" / estimate:"3d"
#API Development / issueType:"Technical Subtask" / assignee:"@inherit" / estimate:"2d"
#Frontend Implementation / issueType:"Technical Subtask" / assignee:"@unassigned" / estimate:"3d"
#Integration Tests / issueType:"Testing Subtask" / assignee:"@unassigned" / estimate:"1d"
#End-to-End Tests / issueType:"Testing Subtask" / assignee:"@unassigned" / estimate:"1d"
#Performance Testing / issueType:"Testing Subtask" / assignee:"@unassigned" / estimate:"4h"
#Security Review / assignee:"@unassigned" / estimate:"4h" / labels:"security"
#Documentation / assignee:"@inherit" / estimate:"4h" / labels:"documentation"Release checklist:
#Merge Feature Branches / assignee:"@inherit" / dueDate:"@now+1d"
#Update Version Numbers / assignee:"@inherit" / dueDate:"@now+1d"
#Run Full Test Suite / assignee:"@unassigned" / dueDate:"@now+2d"
#Update CHANGELOG / assignee:"@inherit" / dueDate:"@now+2d"
#Create Release Notes / assignee:"@inherit" / dueDate:"@now+3d" / labels:"documentation"
#Deploy to Staging / assignee:"@inherit" / dueDate:"@now+3d"
#Smoke Test Staging / assignee:"@unassigned" / dueDate:"@now+4d"
#Backup Production Database / assignee:"@inherit" / dueDate:"@now+5d" / priority:"Highest"
#Deploy to Production / assignee:"@inherit" / dueDate:"@now+5d" / priority:"Highest"
#Production Verification / assignee:"@unassigned" / dueDate:"@now+5d" / priority:"Highest"
#Update Status Page / assignee:"@inherit" / dueDate:"@now+5d"
#Notify Stakeholders / assignee:"@inherit" / dueDate:"@now+5d"QA testing cycle:
#Test Plan Creation / assignee:"@inherit" / estimate:"4h" / dueDate:"@now+1d"
#Test Data Preparation / assignee:"@inherit" / estimate:"2h" / dueDate:"@now+1d"
#Functional Testing - Core Features / assignee:"@inherit" / estimate:"1d" / dueDate:"@now+3d"
#Functional Testing - Edge Cases / assignee:"@inherit" / estimate:"4h" / dueDate:"@now+4d"
#Cross-browser Testing / assignee:"@unassigned" / estimate:"4h" / dueDate:"@now+4d" / labels:"compatibility"
#Mobile Testing / assignee:"@unassigned" / estimate:"4h" / dueDate:"@now+4d" / labels:"mobile"
#Performance Testing / assignee:"@unassigned" / estimate:"3h" / dueDate:"@now+5d"
#Security Testing / assignee:"@unassigned" / estimate:"3h" / dueDate:"@now+5d" / labels:"security"
#Regression Testing / assignee:"@inherit" / estimate:"4h" / dueDate:"@now+5d"
#Bug Report Compilation / assignee:"@inherit" / estimate:"2h" / dueDate:"@now+6d"
#Test Report Documentation / assignee:"@inherit" / estimate:"2h" / dueDate:"@now+6d"Epic breakdown template:
#Research & Discovery / issueType:"Story" / estimate:"1w" / labels:"research"
#Technical Spike / issueType:"Spike" / estimate:"3d" / labels:"technical"
#UI/UX Design / issueType:"Story" / estimate:"1w" / labels:"design"
#Backend Architecture / issueType:"Story" / estimate:"3d" / labels:"backend,architecture"
#Frontend Architecture / issueType:"Story" / estimate:"2d" / labels:"frontend,architecture"
#Phase 1: Core Functionality / issueType:"Story" / estimate:"2w" / labels:"phase1"
#Phase 2: Advanced Features / issueType:"Story" / estimate:"2w" / labels:"phase2"
#Phase 3: Polish & Optimization / issueType:"Story" / estimate:"1w" / labels:"phase3"
#Testing & QA / issueType:"Story" / estimate:"1w" / labels:"testing"
#Documentation / issueType:"Story" / estimate:"3d" / labels:"documentation"
#Deployment & Release / issueType:"Story" / estimate:"2d" / labels:"deployment"Employee onboarding template:
#IT Setup - Request Equipment / assignee:"@unassigned" / dueDate:"@now-7d" / labels:"IT,hardware"
#IT Setup - Create User Accounts / assignee:"@unassigned" / dueDate:"@now-3d" / labels:"IT,accounts"
#IT Setup - Configure Email / assignee:"@unassigned" / dueDate:"@now-2d" / labels:"IT"
#IT Setup - Grant System Access / assignee:"@unassigned" / dueDate:"@now-1d" / labels:"IT,security"
#HR - Prepare Paperwork / assignee:"@unassigned" / dueDate:"@now-3d" / labels:"HR"
#HR - Schedule Orientation / assignee:"@unassigned" / dueDate:"@now" / labels:"HR"
#HR - Benefits Enrollment / assignee:"@unassigned" / dueDate:"@now+3d" / labels:"HR"
#Workspace - Assign Desk / assignee:"@unassigned" / dueDate:"@now-1d" / labels:"facilities"
#Workspace - Order Business Cards / assignee:"@unassigned" / dueDate:"@now+5d" / labels:"admin"
#Team - Welcome Meeting / assignee:"@inherit" / dueDate:"@now" / estimate:"1h"
#Team - Introduction to Team / assignee:"@inherit" / dueDate:"@now" / estimate:"30m"
#Team - Assign Buddy / assignee:"@inherit" / dueDate:"@now"
#Training - Company Overview / assignee:"@unassigned" / dueDate:"@now+1d" / estimate:"2h" / labels:"training"
#Training - Product Training / assignee:"@unassigned" / dueDate:"@now+3d" / estimate:"1d" / labels:"training"
#Training - Tools & Systems / assignee:"@unassigned" / dueDate:"@now+5d" / estimate:"4h" / labels:"training"
#Training - Security Training / assignee:"@unassigned" / dueDate:"@now+7d" / estimate:"2h" / labels:"training,security"
#Project - First Task Assignment / assignee:"@inherit" / dueDate:"@now+10d"
#Check-in - One Week Review / assignee:"@inherit" / dueDate:"@now+7d" / estimate:"30m"
#Check-in - 30 Day Review / assignee:"@inherit" / dueDate:"@now+30d" / estimate:"1h"
#Check-in - 90 Day Review / assignee:"@inherit" / dueDate:"@now+90d" / estimate:"1h"Additional features
Bulk operations
Create up to 200 Jira subtasks simultaneously. For optimal performance and reliability, large batches are automatically split into multiple requests (4 requests of 50 subtasks each), but this happens seamlessly in the background.
💡 Performance tips:
- Templates with 50+ subtasks may take a few seconds to process
- The results window will show all created subtasks once complete
- If any subtasks fail, you can copy the failed items and retry
Rich text formatting
Subtask descriptions and paragraph fields support Jira’s wiki markup for rich text formatting:
Common formatting:
| Format | Syntax | Example | Result |
|---|---|---|---|
| Bold | *text* | *important* | important |
| Italic | _text_ | _emphasis_ | emphasis |
| Link | [text|URL] | [link text|https://example.com] | link text |
| New line | \n | first line\nsecond line | first line second line |
| Bullets | * text | * bullet\n* bullet | • bullet • bullet |
| Monospace | {{text}} | {{code}} | code |
| Headers (h1 to h6) | h1. text | h1. Header | Header |
| Deleted | -text- | -deleted text- | |
| Inserted | +text+ | +inserted text+ | inserted text |
| Citation | ??text?? | ??citation text?? | — citation text |
| Superscript | ^text^ | superscript ^text^ | superscript text |
| Subscript | ~text~ | subscript ~text~ | subscript text |
Dark mode
Enjoy a fully accessible dark theme for a comfortable and stylish experience. Dark mode is automatically enabled when your Jira theme is set to dark.
Dark mode features:
- Automatically matches your Jira theme settings
- Reduces eye strain during extended use
- Maintains full accessibility standards
- All UI elements properly styled for optimal contrast
Frequently asked questions
Why do I get “Field cannot be set” errors?
Error message: “Field ‘field’ cannot be set. It is not on the appropriate screen, or unknown.”
This happens when a field isn’t configured for your project’s screens. To fix this, ask your project administrator to:
- Go to either:
– Space settings → Work types (for project-specific configuration)
– Jira settings → Work types (for global configuration) - Select the relevant work type (such as Task or Subtask)
- Add the missing field to the appropriate screen section
💡 Tip: Common fields that may need to be added include Story Points, Sprint, or custom fields specific to your organization.
Why can’t I see error details when creating many subtasks?
When creating large batches of subtasks, if none of them are valid, the system may not be able to provide specific error details due to technical limitations.
Solution: Break your template into smaller chunks of 1-2 subtasks to identify which lines are causing issues. Once you’ve identified and fixed the problematic lines, you can run the full template.
Example approach:
- Test the first 2 subtasks
- If they work, test the next 2
- Continue until you find the problematic subtask
- Fix the issue and combine back into your full template
The dialog doesn’t open on the first click and the page scrolls down. Why?
This occurs due to platform limitations in Atlassian Connect. The button is implemented as a content panel, which causes Jira to scroll when clicked. During this scroll, the dialog creation can fail.
Quick fixes:
- Try clicking the button again – it usually works on the second attempt
- Scroll to the top of the issue before clicking the button
- Wait for the page to finish loading completely before clicking
Can I use this app in team-managed projects?
Yes! The app works in both company-managed and team-managed projects. However, some field names may differ:
- “Timestamp” in team-managed = “Date time picker” in company-managed
- “Dropdown” in team-managed = “Select list” in company-managed
Why doesn’t @inherit work for some fields?
The @inherit keyword copies values from the parent issue, but the parent must actually have a value in that field. If the parent’s field is empty, the subtask field will also remain empty. Issue Type is the only field that doesn’t support @inherit.
Can I create subtasks on multiple parent issues at once?
No, subtasks can only be created for one parent issue at a time. However, you can save your template and quickly reuse it on different parent issues.