--- language: "en" --- # Easy Issue Templates for Jira Cloud ## Easy Issue Templates for Jira Cloud Easy Issue Templates for Jira is an app for Jira Cloud and Data Center that streamlines Jira issues creation from saved Jira Templates. Get Started You're viewi... [Get Started](https://help.appliger.com/easy-templates-for-jira/get-started.md) ### Release Notes * #### [2026-08-30](https://help.appliger.com/easy-templates-for-jira/2026-08-30.md) August 31, 2026 * #### [2026-08-27](https://help.appliger.com/easy-templates-for-jira/2026-08-27.md) August 27, 2026 * #### [2026-07-10](https://help.appliger.com/easy-templates-for-jira/2026-07-10.md) July 10, 2026 ### Featured * #### [Dynamic Fields: Automate Calculations with Expressions](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md) Use Dynamic Fields to calculate field values automatically instead of entering fixed values manually. In Easy Templates, this is done with Expressions. An expr... * #### [Using Templates](https://help.appliger.com/easy-templates-for-jira/working-with-templates.md) Create Issue from Template Apply Template to existing issue Automation \& REST API For any questions or feature requests contact us via Customer Portal * #### [Managing Templates](https://help.appliger.com/easy-templates-for-jira/manage-templates.md) Here you will learn how to Manage Jira Issue Templates in Easy Templates for Jira app You must be a System Administrator or Project Administrator to perform th... ### Documentation * #### [Get Started](https://help.appliger.com/easy-templates-for-jira/get-started.md) * [Key features \& Benefits](https://help.appliger.com/easy-templates-for-jira/key-features-benefits.md) * [Installation](https://help.appliger.com/easy-templates-for-jira/install.md) * [Permissions](https://help.appliger.com/easy-templates-for-jira/permissions.md) * [Promotions](https://help.appliger.com/easy-templates-for-jira/promotions-cloud.md) * [Supported Products \& Projects](https://help.appliger.com/easy-templates-for-jira/supported-products-projects.md) * [1 more pages](https://help.appliger.com/easy-templates-for-jira/get-started.md) * #### [Creating Templates](https://help.appliger.com/easy-templates-for-jira/creating-templates.md) * [Create Template](https://help.appliger.com/easy-templates-for-jira/create-save-template.md) * [Epic Templates](https://help.appliger.com/easy-templates-for-jira/epic-templates.md) * #### [Using Templates](https://help.appliger.com/easy-templates-for-jira/working-with-templates.md) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template.md) * [Apply Template to existing issue](https://help.appliger.com/easy-templates-for-jira/apply-template.md) * [Automation \& REST API](https://help.appliger.com/easy-templates-for-jira/automation-rest-api.md) * #### [Dynamic Fields: Automate Calculations with Expressions](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md) * [Employee onboarding with Dynamic Fields](https://help.appliger.com/easy-templates-for-jira/employee-onboarding-with-dynamic-fields.md) * [Marketing Campaign with Dynamic Fields](https://help.appliger.com/easy-templates-for-jira/marketing-campaign-with-dynamic-fields.md) * [Compliance and audit preparation with Dynamic Fields](https://help.appliger.com/easy-templates-for-jira/compliance-and-audit-preparation-with-dynamic-fields.md) * [New Client Onboarding with Dynamic Fields](https://help.appliger.com/easy-templates-for-jira/new-client-onboarding-with-dynamic-fields.md) * [Project delivery / implementation with Dynamic Fields](https://help.appliger.com/easy-templates-for-jira/project-delivery-implementation-with-dynamic-fields.md) * #### [Managing Templates](https://help.appliger.com/easy-templates-for-jira/manage-templates.md) * [Set Template scope](https://help.appliger.com/easy-templates-for-jira/set-template-scope.md) * [Variables \& Forms](https://help.appliger.com/easy-templates-for-jira/variables.md) * [Configure Template fields](https://help.appliger.com/easy-templates-for-jira/enabling-template-fields-cloud.md) * [Copy Template](https://help.appliger.com/easy-templates-for-jira/copy-template-cloud.md) * [Delete Template](https://help.appliger.com/easy-templates-for-jira/delete-template.md) * #### [Release Notes](https://help.appliger.com/easy-templates-for-jira/release-notes.md) * [2026-08-30](https://help.appliger.com/easy-templates-for-jira/2026-08-30.md) * [2026-08-27](https://help.appliger.com/easy-templates-for-jira/2026-08-27.md) * [2026-07-10](https://help.appliger.com/easy-templates-for-jira/2026-07-10.md) * [2026-04-19](https://help.appliger.com/easy-templates-for-jira/2026-04-19.md) * [2026-04-15](https://help.appliger.com/easy-templates-for-jira/2026-04-15.md) * [27 more pages](https://help.appliger.com/easy-templates-for-jira/release-notes.md) * #### [Integrations](https://help.appliger.com/easy-templates-for-jira/integrations.md) * [Smart Checklist for Jira](https://help.appliger.com/easy-templates-for-jira/smart-checklist-for-jira.md) * [Checklists for Jira by HeroCoders](https://help.appliger.com/easy-templates-for-jira/issue-checklist-for-jira.md) * [Checklist for Jira \| Enterprise](https://help.appliger.com/easy-templates-for-jira/checklist-for-jira-enterprise.md) * [Tempo Timesheet](https://help.appliger.com/easy-templates-for-jira/tempo-timesheet.md) * [Power Custom Fields](https://help.appliger.com/easy-templates-for-jira/power-custom-fields.md) * [1 more pages](https://help.appliger.com/easy-templates-for-jira/integrations.md) * #### [FAQ](https://help.appliger.com/easy-templates-for-jira/faq.md) * [Setting the Parent Field After Issue Creation](https://help.appliger.com/easy-templates-for-jira/setting-the-parent-field-after-issue-creation.md) * #### [Agreements](https://help.appliger.com/easy-templates-for-jira/agreements.md) * [AppLiger Apps: Cloud Security Policy](https://help.appliger.com/easy-templates-for-jira/appliger-apps-cloud-security-policy.md) * [Service Level Agreement (SLA)](https://help.appliger.com/easy-templates-for-jira/service-level-agreement-sla.md) * [End User License Agreement](https://help.appliger.com/easy-templates-for-jira/end-user-license-agreement.md) * [Privacy Policy](https://help.appliger.com/easy-templates-for-jira/privacy-policy.md) * [Terms of Service (ToS)](https://help.appliger.com/easy-templates-for-jira/terms-of-service-tos.md) * [1 more pages](https://help.appliger.com/easy-templates-for-jira/agreements.md) * #### [Support](https://help.appliger.com/easy-templates-for-jira/support.md) * [Troubleshooting](https://help.appliger.com/easy-templates-for-jira/troubleshooting.md) * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition.md) * [Server/DC to Cloud Migration](https://help.appliger.com/easy-templates-for-jira/server-dc-to-cloud-migration.md) * [Cloud to Cloud Migration](https://help.appliger.com/easy-templates-for-jira/cloud-to-cloud-migration.md) * [Cloud vs Server/Data Center version difference](https://help.appliger.com/easy-templates-for-jira/cloud-vs-server-data-center-version-difference.md) * [3 more pages](https://help.appliger.com/easy-templates-for-jira/support.md) --- language: "en" --- # 2023-07-10 ## 3.0.1 Jira Cloud. 2023-07-10 **UI/UX Improvements**๐ŸŽ‰ * Simplified template selection when creating new issues * Added creation of sub/child tasks after pre-filling new issues * Added tree of created issues * Moved template variables to a separate step * Added ability to move back to each step or start over when creating issues * Added ability to navigate to any of created issues of any hierarchy level * Added ability to Apply templates of various issue types * Other minor UI/UX improvements --- language: "en" --- # 2023-07-14 ## 3.0.6 Jira Cloud. 2023-07-14 **Onboarding and zero-state improvements** Added ability to create templates: * On the Templates Management page * On the Get Started page * In the New Issue and Apply Template dialogs when there are no templates --- language: "en" --- # 2023-07-20 ## 3.0.10 Jira Cloud. 2023-07-20 **Template Management page UI/UX improvements** * Ability to find templates by name and/or issue type * Sorting templates by Issue Type ## 3.0.9 Jira Cloud. 2023-07-19 **UI/UX improvements** * Ability to find templates by name and type, filter matching the issue type in the Apply Template dialog * Improved Project and Template search in the New Issue dialog --- language: "en" --- # 2023-11-07 ## 3.0.20 Jira Cloud. 2023-11-07 * Implement support of label selection through the Manage Template form * Support of Hierarchy Level 2 (Initiative) for Advanced Roadmap integration --- language: "en" --- # 2023-11-28 ## 3.0.21 Jira Cloud. 2023-11-28 ### What's new in version 3.0.21-AC Enhanced scoping for templates, allowing them to be limited to specific projects ### Release notes * Various UI/UX improvements in template editing and form functionality. * Enhanced scoping for templates, allowing them to be limited to specific projects. * Filtering templates according to context and scope when applying them. * Set minimum page height (workaround for the "AP.sizeToParent() doesn't take the entire page" bug ) * Library updates --- language: "en" --- # 2024-01-30 ## 3.0.25 Jira Cloud. 2024-01-30 ### What's new Description field preview **Release Notes** * When editing a Template, you can now preview the Description field. This feature allows users to see the actual appearance of the Description in the created issue, rather than just the basic markup format. * Also, we've included a handy link to the Formatting Notation Help for your convenience. --- language: "en" --- # 2024-03-19 ## Easy Issue Templates for Cloud. 2024-03-19 **Platform:** Cloud **Version:** 3.0.28-AC **Release notes:** New Variable Description attribute . Example:`<>` Fixed Support "Tempo Account" field on the Create flow Improved Infrastructure and storage robustness --- language: "en" --- # 2024-08-20 ## Easy Issue Templates for Jira Cloud. 2024-08-20 **Platform**: Cloud **Version**: 3.0.43 **Release notes**: * NEW Implement support of Custom Label field * NEW Implement support of User Picker field --- language: "en" --- # 2024-08-30 ## Easy Issue Template for Jira Cloud. 2024-08-30 **Platform:** Cloud **Version:** 3.0.45-AC **Release Summary:** Variable defaults **Release notes**: * New Introducing the ability to set default values for template Variables * Improved Fixed search and user representation in the Reporter template field * Fixed Various issues fixed --- language: "en" --- # 2024-09-17 ## Easy Issue Template for Jira Data Center. 2024-09-17 **Platform:** Data Center **Version:** 2.5.0 **Release Summary:** Extend Variable Types for Templates We've extended the functionality of Easy Issue Templates by adding new variable types to enhance flexibility and control in template creation. **Release notes**: * New Added a few new variable types * **Long Text Variable** Allows users to add large text blocks for detailed descriptions or comments. * **Number Variable** Enables users to input numeric values, providing better control for data entry (e.g., budget, effort estimation). * **Date Variable** Users can now select specific dates, which is ideal for due dates, first working days, project deadlines, and other date-related fields. ![image-20240917-160026.png](https://help.appliger.com/__attachments/a_e063e05d7190cf1998bc130d7492ab19bee6d795a7a10129a446333a543052dc/image-20240917-160026.png?cb=238bce4bee423c7107a8a13fd9109d05) * IMPROVED **Show Template Creator** Now, template managers can see who created templates so that they can address proper feedback or questions to the template owner. ![image-20240917-155449.png](https://help.appliger.com/__attachments/a_b38058e57891721009e369fcdf1e7a468908bcce28f241fb2aafd282439bde83/image-20240917-155449.png?cb=1073838115f40c8b052ffb7a409df194) --- language: "en" --- # 2024-10-18 ## Easy Issue Templates for Jira Cloud. 2024-10-18 **Platform:** Cloud **Version:** 3.0.50-AC **Release Summary:** Preview Template Structure before issue creation * NEW Introduced a new "Review" step in the issue creation flow, showing the template structure * Users can select/unselect specific issues (child or sub-tasks) from the template. * This step appears only for hierarchical templates. * Variables step is only shown for selected issues and skipped if not needed. * IMPROVED Renamed issue creation steps for clarity: * old: Template โ†’ Variables โ†’ Creation * new: Select โ†’ Review โ†’ Fill โ†’ Result * Fixed Variables icons do not reflect types while adding them to a custom field ## Easy Issue Templates for Jira Data Center. 2024-10-18 **Platform:** Data Center **Version:** 2.6.1 **Release Summary:** Resolved the issue where the Manage Template screen appeared blank --- language: "en" --- # 2024-10-24 ## Easy Issue Templates for Jira Cloud. 2024-10-24 **Platform:** Cloud **Version:** 3.0.54-AC **Release Summary:** New variable types * NEW Added a few new variable types * **Number Variable** Enables users to input numeric values, providing better control for data entry (e.g., budget, effort estimation). * **Date Variable** Users can now select specific dates, which is ideal for due dates, first working days, project deadlines, and other date-related fields ![image-20241024-111525.png](https://help.appliger.com/__attachments/a_0c8998061183b929dda06f6f94642303dae81af8bae836ae297ff58e7ae16255/image-20241024-111525.png?cb=2daea403b4efd9aa18b790f7bbb89795) --- language: "en" --- # 2024-10-28 ## Easy Issue Templates for Jira Cloud **Platform:** Cloud **Version:** 3.0.58-AC **Release Summary:** New variable types: Single Select, Multi-Select * NEW Added a few new variable types * **Single Select Dropdown Variable** It allows users to choose a single option from a predefined list, ideal for setting specific statuses, categories, departments, or other exclusive options in issue templates. * **Multi-Select dropdown** It enables the selection of multiple options from a list, perfect for adding tags, applicable teams, or custom labels to issues where multiple values may be relevant. ## How it works? * [Add Variables](https://help.appliger.com/easy-templates-for-jira/variables) in the Manage Templates section. ![image-20241028-175629.png](https://help.appliger.com/__attachments/a_c16a7df9911bb394cd6ef4d149f9914dd5eb7f7b4fdc6d3dc747e50428992874/image-20241028-175629.png?cb=13bb9084010780168b119040270cb50d) * Set values for select variables types ![image-20241028-181727.png](https://help.appliger.com/__attachments/a_96fd0d10959d84236619e53c3de34a3e4473c491b25ea293ab342fc1af38c400/image-20241028-181727.png?cb=8c92a801eb3021bcb66c62a787d6b226) * [Choose Variables](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template)' values while issues creation ![image-20241028-175527.png](https://help.appliger.com/__attachments/a_7e9a729bbcde72c9f0934afb6763647b20cd0950fbd459683c95af244604b694/image-20241028-175527.png?cb=d678ab7046b1c4a0929336638de091e7) * Get selected values filled in ![image-20241028-182202.png](https://help.appliger.com/__attachments/a_624b621f273a7ab7507d78049d602b7fc7de11f5550771fb320ebfb9726a4e28/image-20241028-182202.png?cb=151d922967cf2739cdaf87a02841ec6e) --- language: "en" --- # 2025-04-15 Following our [previous announcement](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition), we're thrilled to introduce the first version of **Easy Issue Templates for Jira** on**the Atlassian Forge** platform**!** ๐ŸŽ‰ This release makes template usage smoother than ever, bringing deeper **Jira UI integration** and paving the way for even bigger improvements. ## **โœจ** What's New? NEW **Automated Prefilling:** Configure **default templates** by **Project** and **Issue Type** for automatic field population on **Jira issue creation screen** saving you time and ensuring consistency. ![Template. Default section.png](https://help.appliger.com/__attachments/a_aaee827a79b78280a93d3dac18424321c989a98ef31b0ef1d70f58f69fc5fd79/Template.%20Default%20section.png?cb=1e3b5f570d5909f4715974d7c3bd4803) ![DefaultTemplate.gif](https://help.appliger.com/__attachments/a_d8260460bb8d91190edda32d61db7d552f2a51bf64e8db32655e22c65623b2a1/DefaultTemplate.gif?cb=c000281aac023e9dc4560ce332f4cd29) **Direct Selection:** Select and apply your templates directly from **Jira's issue creation screen** . **Simple** and **Epic** hierarchy templates and variables are supported! ![Template. Create Screen.png](https://help.appliger.com/__attachments/a_d534ba1ae972dc542ed67170543bfcf628345b60a904ab83d51aeddeb3f47f14/Template.%20Create%20Screen.png?cb=8e70232579486e129eaaa645edf10caf) ## ๐Ÿ› ๏ธ Improvements \& Changes Improved * [**Supported fields**](https://help.appliger.com/easy-templates-for-jira/supported-fields)**' set is extended** per view and issue creation flow * **Scope configuration moved** to the dedicated section of the template. ![Template. Scope section.png](https://help.appliger.com/__attachments/a_86da98d795b9b9878da1f9e51061f7916889b8b41d57cd499653c25926d4972f/Template.%20Scope%20section.png?cb=1634c2e4d028f25ee19ec06b77b81acf) * **Popup is Now a Page:**When you click on the Templates menu item from the Apps or Projects sidebar, you'll be redirected to a dedicated page instead of the previous popup used in the Connect app. This change is due to the Forge architecture, and it cannot be modified. ![New page.png](https://help.appliger.com/__attachments/a_a30dccda7dac10a8c381ed993d9de2fd60af7bbaa9e10bbb3735d5e11625e7d1/New%20page.png?cb=ebba796c3e912000099bb3c0474cf73b) * **Launching Issue Creation** from the Template Dialog**via the 'X' Button** is Deprecated. * **Compatibility with** [**new Jira UI**](https://www.atlassian.com/blog/announcements/the-new-jira)**:** put the **Templates** menu item in the project navbar for convenient access ![MoveTemplatesToolbar.gif](https://help.appliger.com/__attachments/a_0e25987dcd5c12f4df05dc4480c2ef349c13f5abdbc54de2db525aa688549131/MoveTemplatesToolbar.gif?cb=73a46b1985c6009d476d91c9979bc729) * **Stricter Template Administration:** Project Admins can now view only global templates and those scoped specifically to their own projects. * **Default Template:** Set a default template per project -- it will be auto-selected on the Easy Templates "Create Issue" page and on the Jira Create Issue screen. Projects that have templates designated as default will be highlighted with a purple background on the Templates Manage page. ![image-20250416-114333.png](https://help.appliger.com/__attachments/a_70f045eb0b490365eb8f381bbe8e0f6c540de012259b40ad6ab2383b80b2fc7e/image-20250416-114333.png?cb=e31104defa6303f055a451c6b7411f05) With seamless **integration** into the **Jira Create Issue screen**, the current issue creation flow using the Easy Templates popup and screens is now considered legacy and outdated and will be deprecated in the future. We encourage users to **adopt the new issue creation flow** using the native Jira **Create** **screen**. ## ๐Ÿž Bug Fixes FIXED * The Template Scope change won't submit on the first attempt ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) ## **โš ๏ธ Important to know** These changes might affect your usual template workflows. If you notice any discrepancies, [++**let us know**++](https://appliger.atlassian.net/servicedesk/customer/portal/1)! We're dedicated to ensuring a smooth transition for you and your team ## **๐Ÿ”ฎ What's Next?** We're not stopping here! Here's a sneak peek at what's coming **next month** : โœ… **Forge-based storage for templates** -- Say goodbye to third-party storage! All templates will soon live **inside your Jira instance.** โœ… **Gradual migration** -- We'll ensure a smooth transition to the new storage system without disrupting your workflows. โœ… **Better Security \& Compliance** -- No external storage means **better privacy, data residency support, and no egress concerns.** More details in the **next release notes**---stay tuned! --- language: "en" --- # 2025-08-03 ## **โœจ** What's New? NEW **Automation \& REST API:** Set up **Jira Automation rules** to use templates based on triggers like issue creation, status changes, project-specific rules, or scheduled events. Integrate with other tools via **REST API**. This functionality ensures that your workflows remain interconnected and efficient. ๐ŸŽ‰ When enabled, admins can configure webhooks and payloads from the template's **Automation** tab. Follow the instructions and example **Use Cases** to set-up effective Automation integration [Automation \& REST API](https://help.appliger.com/easy-templates-for-jira/automation-rest-api.md) * [**Scheduled time-based Issues creation:** Create monthly Financial tasks](https://help.appliger.com/easy-templates-for-jira/scheduled-time-based-issues-creation) * [**Sub-tasks creation:**Apply QA subtasks on the User Story transition](https://help.appliger.com/easy-templates-for-jira/sub-tasks-creation-for-existing-issue) * [**Bulk templates usage:** Create issues when a New Project created](https://help.appliger.com/easy-templates-for-jira/create-issues-when-new-project-created) * [**Create issues once a Service Desk ticket is raised**: New employee onboarding process](https://help.appliger.com/easy-templates-for-jira/create-issues-once-a-service-desk-ticket-is-raised.md) ## ๐Ÿ› ๏ธ Improvements \& Changes Improved System Admin navigation improved. We've introduced separate menu items for **Template** **Management** , app **Settings,** and improved the **Get Started** page. ![image-20250801-201431.png](https://help.appliger.com/__attachments/a_bf01d347eac21ee73fd46368a6a331ab79e82997d263f79d9349063cfb8aca88/image-20250801-201431.png?cb=e3b5cfa2b00fb21a34ab429ac5bbcbe0) ## ๐Ÿž Bug Fixes FIXED Now the **Original Estimate** custom field could be set in Template Management. ## **โš ๏ธ Important to know** * Test automation rules before publishing for production use * Review documentation and educate users ## **๐Ÿ“– Helpful Docs** * [Automation \& REST API](https://help.appliger.com/easy-templates-for-jira/automation-rest-api) * [Using Templates](https://help.appliger.com/easy-templates-for-jira/working-with-templates) * [Get Started](https://help.appliger.com/easy-templates-for-jira/get-started) ## **๐Ÿ”ฎ What's Next?** * [Full storage migration to Atlassian Forge](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * Audit Log * Improved Permissions settings --- language: "en" --- # 2025-09-16 **๐Ÿ“ฆ Easy Templates:** **v5.8.0** With this version, **Easy Templates** now fully leverages **Forge backend and storage** as its sole infrastructure - no more 3rd-party AWS. One step closer to **Runs on Atlassian**! ๐ŸŽ‰ This release continues our [Forge Remote migration](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) and supports the overall [Connect to Forge transition plan](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition). ## **โœจ** What's New? NEW * **Project-Scoped Templates (default)** Templates are now automatically scoped to the project where they're saved. This improves security, avoids clutter in the template library, and makes templates easier to manage. * **Checklist Items in Descriptions** Add and track action items directly inside issue descriptions. * **User Mentions in Descriptions** Mention team members in your templates for faster collaboration. * **Series Issue Creation** Create multiple issues in sequence while preserving unique issue keys. ## ๐Ÿ› ๏ธ Improvements \& Changes Improved * **Forge Storage Enhancements** * [Forge-hosted storage is utilized](https://developer.atlassian.com/platform/forge/storage/) * [Data residency support](https://developer.atlassian.com/platform/forge/data-residency/) * [28-day retention period](https://developer.atlassian.com/platform/forge/storage/#data-recovery-for-apps-with-hosted-storage) * Better consistency when working with project-scoped templates ## ๐Ÿž Bug Fixes FIXED * Fixed minor issues related to template saving and rendering * Improved error handling during issue creation ## **โš ๏ธ Important to know** With[**Forge hosted storage**](https://developer.atlassian.com/platform/forge/storage/#forge-hosted-storage), the process for app uninstalling and data retention is changed: * Uninstalling the app will **unlink your templates from the app**. * Reinstalling the app will **not automatically restore your templates**. * You can still recover your templates, but it will require assistance from the **Atlassian support team** and must be done **within 21 days** of the uninstall. * Submit your recovery request [via our Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) * Then we'll follow up with Atlassian to make the recovery possible This is an Atlassian legal requirement to keep data retention consistent. Reference: * Atlassian Forge ticket: "[Option to relink data after app reinstallation](https://ecosystem.atlassian.net/jira/polaris/projects/ROADMAP/ideas/view/5120994?selectedIssue=ROADMAP-107&issueViewSection=comments)" * [About data recovery for Forge Storage](https://developer.atlassian.com/platform/forge/runtime-reference/storage-api/#data-recovery-for-apps-with-hosted-storage) * These changes might affect your usual template workflows. If you notice any discrepancies, [++**let us know**++](https://appliger.atlassian.net/servicedesk/customer/portal/1)! We're dedicated to ensuring a smooth transition for you and your team * The app is not yet eligible for "Runs on Atlassian." Remote storage remains enabled for Connect customers who have not migrated. We plan to achieve "Runs on Atlassian" status within 1 to 2 months. ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) --- language: "en" --- # 2025-09-29 **๐Ÿ“ฆ Easy Templates:** **v5.21.0** Introducing smarter template handling and usability improvements. ## **โœจ** What's New? NEW * **Numbered Columns in Tables** You can now add numbered columns when creating tables inside issue descriptions. * **Template Filtering by Issue Type** The Jira Create screen now shows only templates for the selected issue type, making selection faster and more relevant. You can show all templates by unchecking "Only matching the issue type". * **Updated Help Links** "Help" links have been replaced with direct links to relevant documentation for quicker guidance in Jira Create screen and Easy Templates create page. ## ๐Ÿ› ๏ธ Improvements \& Changes Improved * Linked issues are no longer created if links are disabled in the template. ## ๐Ÿž Bug Fixes FIXED * Fixed an issue where used variables were not displayed in the Jira Create screen. ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) --- language: "en" --- # 2025-10-17 **๐Ÿ“ฆ Easy Templates: v7.1.0** Introducing [Audit Log](https://help.appliger.com/easy-templates-for-jira/audit-log), usability improvements, and fixes. ## **โœจ** What's new? NEW * **Audit Log** Track and troubleshoot actions related to template usage, such as creating work items and applying templates. [Read more](https://help.appliger.com/easy-templates-for-jira/audit-log) * **Config Page** Navigate to the app config page from the system admin management board. ## ๐Ÿ› ๏ธ Improvements \& changes Improved * Impersonation: the app now creates issues on the user's behalf, reducing Jira notifications and preventing the app from being added as an issue watcher automatically. ## ๐Ÿž Bug fixes FIXED * Remove variables from template content after deleting them from the template. * Fix variable ID references when copying templates. ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) --- language: "en" --- # 2025-11-14 **๐Ÿ“ฆ Easy Templates: v7.31.0** ## **โœจ** What's new? NEW * **"Create Screen Integration" setting** This setting lets system admins control whether the "Templates" field appears automatically on the "Create" screen after saving an issue template. [Learn more](https://help.appliger.com/easy-templates-for-jira/use-jira-native-create-issue-screen-integration) about Jira Create Screen usage ![image-20251114-225715.png](https://help.appliger.com/__attachments/a_f83d7859ac089a84150e386a07b2896752bc7b2cec31064eb6e025f6a75c2e6b/image-20251114-225715.png?cb=6862d6b878909b47a941424ea6e3ad5d) ## ๐Ÿ› ๏ธ Improvements \& changes Improved * Refine logic to identify unlicensed tenants ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) --- language: "en" --- # 2025-11-27 **๐Ÿ“ฆ Easy Templates: v7.33.0** ## ๐Ÿ› ๏ธ Improvements \& changes Improved * **Issue Reordering for Templates:** Now you can reorder Template's issues in Manage Templates You can now **reorder issues inside any Template** directly from **Manage Templates** . This lets you structure tasks exactly how you want them to appear during issue creation. Go to **Easy Templates โ†’ Manage Templates โ†’ Issues** and simply drag items to reorder. ![image-20251127-132101.png](https://help.appliger.com/__attachments/a_41767c8092adec58068c5043634ec9e95aa7901d484a9e0b13cd8cc6a928a8a5/image-20251127-132101.png?cb=488084c38eceb8afa72fe3937f59ce2b) You can now expand or collapse hierarchical issues for better visibility. ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) --- language: "en" --- # 2026-01-14 **๐Ÿ“ฆ Easy Templates:**Atlassian Government Cloud (AGC) Support ## **โœจ** What's new? NEW We are excited to announce that **Easy Issue Templates for Jira** is now fully compatible with the Atlassian Government Cloud (AGC) environment. Government agencies can now leverage the full power of **Easy Issue Templates for Jira** while meeting strict federal security standards. ## **๐Ÿ“– Helpful Docs** * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # 2026-01-27 **๐Ÿ“ฆ Easy Templates: v8.0.0** Permissions improvements for **Easy Issue Templates for Jira** ๐Ÿš€ ## **โœจ** What's new? NEW We've introduced a new global permission and clarified who can **use** vs. **manage templates**: More info: [Permissions](https://help.appliger.com/easy-templates-for-jira/permissions.md) * New global permission: **"Easy Templates -- Manage Templates"** * Lets admins grant **Template Manager** rights via Jira groups (without Site/Project Admin). * Template Managers can create/edit/delete/clone templates, use **"Save as template"** , and manage global \& project templates (where they have **Browse Projects**). * Who can do what * **Template Users (any Jira user)** can: * Apply templates to issues\* * Create issues from templates\* * **Template Managers** (Site Admins, Project Admins, or users with the new global permission) can also manage templates. Use "Manage Templates" tab in **Apps** โ†’ **Templates** view ![image-20260127-160452.png](/__attachments/a_26fd59e567f7a6ea2163c623c2a5a5236e75f93976492916f4ff6492a679b94d/image-20260127-160452.png?cb=39c88be690d5412719ada5a51783a378) * Required Jira project permissions * **Apply a template** โ†’ needs **Edit Issues** and (currently) **Create Issues** when child issues are created * **Create issues from template** โ†’ needs **Create Issues** **\***Always subject to Jira project permissions above ## ๐Ÿ› ๏ธ Improvements \& changes Improved * **Usage analytics**: We implemented analytics using PostHog. This helps us learn from users and improve the app. Admins can disable analytics in the admin console โ†’ app details ## **๐Ÿ“– Helpful Docs** * [Permissions](https://help.appliger.com/easy-templates-for-jira/permissions.md) * [Easy Templates: Connect to Forge transition](https://help.appliger.com/easy-templates-for-jira/easy-templates-connect-to-forge-transition) * [Best Practices](https://help.appliger.com/easy-templates-for-jira/best-practices) * [Supported Fields](https://help.appliger.com/easy-templates-for-jira/supported-fields) * [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template) --- language: "en" --- # 2026-03-13 **๐Ÿ“ฆ Easy Templates: v8.13.0** Introducing **Expressions** for Dynamic Fields and small editor usability improvements. ![Banner. Expressions.png](https://help.appliger.com/__attachments/a_b10ccbf1fa4f0490ed24b5dbd033e9ea052ae18b0f329369078d2e9001f79e32/Banner.%20Expressions.png?cb=2896f9c3cf1e26fd56d2f2b629a8b49f) ## **โœจ** What's new? NEW * **Expressions** Calculate field values dynamically during issue creation using dates, variables, and values from current, parent, or root issues. This helps build smarter templates without relying only on fixed values. [**Read more**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md) ## ๐Ÿ› ๏ธ Improvements \& changes Improved * **Field actions moved to the** `...`**menu** We replaced the toggles shown next to each field with a cleaner `...`**actions menu** . ![image-20260313-202139.png](https://help.appliger.com/__attachments/a_91c04197d9063e7ef7b8b4b5ae120c528dd076eff1862bddac270f96279ed819/image-20260313-202139.png?cb=e4d87eea7b358912086fd6e9542a2967) * **Enable / disable fields from one place** You can now use the menu to quickly **Enable** or **Disable** a field. ![image-20260313-202105.png](https://help.appliger.com/__attachments/a_f65b2160a3ee6d67ca83d7266b7eafeac2f55d74c9c9075930b2f934e4346751/image-20260313-202105.png?cb=bd446ef3b96f832b9994594d46e1a95b) * **Switch between value and expression mode** Supported fields can now be switched between **Use value** and **Use expression** directly from the same menu. ![image-20260313-202224.png](https://help.appliger.com/__attachments/a_e772939a12cdd700261fac83b21577b49ee6dd101f53bfc09ab3bb0767a22b6c/image-20260313-202224.png?cb=7a8afbd8771e32aef9a10ab21572a57c) * **Expression editor replaces the standard input** When a field is set to use an expression, the regular field input is replaced with a compact expression editor with validation feedback. ![image-20260313-201946.png](https://help.appliger.com/__attachments/a_9724c6171af1ec3ef537fb96fffaca70b2c196baa79b074e1702749b3104ba3b/image-20260313-201946.png?cb=932fed7eb508844f3b12be0918703017) ![image-20260313-201834.png](https://help.appliger.com/__attachments/a_0a5feeda7d0ab97fd9f499de9f0b80ccb652db9650063b42f4335c0fe5f06997/image-20260313-201834.png?cb=02ad7579d13408849fe5d968e330e345) ## ๐Ÿž Bug fixes FIXED * Remove variables from template content after deleting them from the template. * Fix variable ID references when copying templates. ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-04-06 **๐Ÿ“ฆ Easy Templates: v8.20.0** Global templates compatibility with Create Issue screen ## **โœจ** What's new? NEW Use global templates in GIC (Cglobal Issue Create screen). Issues will prefill without problems. Previously, only [Project-scoped templates](https://help.appliger.com/easy-templates-for-jira/set-template-scope.md) worked there. ## ๐Ÿ› ๏ธ Improvements \& changes Improved * Enhanced app-to-user communication during template creation and issue generation from templates * Improved performance and responsiveness in template management ## ๐Ÿž Bug fixes FIXED * Various fixes ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-04-08 **๐Ÿ“ฆ Easy Templates: v8.23.0** Include an "actor" in the Automation payload. ## **โœจ** What's new? NEW Add the "actor" to the payload to set the **Reporter** on issues created via the [Automation/REST API webhook](https://help.appliger.com/easy-templates-for-jira/automation-rest-api.md). By default, when issues are created from a template through Automation or REST API, the Reporter is set to the Easy Issue Templates for Jira app. With this new setting, you can override the Reporter. Example payload: JSON { "operation": "create-issues", "actor": "account ID or email", "project": "{{project.id}}" } ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-04-12 **๐Ÿ“ฆ Easy Templates: v9.0.0** Easy Templates ROVO agent released! ## **โœจ** What's new? NEW The first version of the Easy Templates ROVO agent is live. Create new Issue Templates directly from ROVO chat. ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-04-15 **๐Ÿ“ฆ Easy Templates: v9.1.0** [Audit Log](https://help.appliger.com/easy-templates-for-jira/audit-log.md)now includes actions from the Global Issue Create screen and the Easy Template Prefill flow. ## **โœจ** What's new? NEW Track additional template usage events. See the "Source" parameter. Source: * GIC - template used in the [Global Issue Create screen](https://help.appliger.com/easy-templates-for-jira/use-jira-native-create-issue-screen-integration.md) * Manual - template used in [App โ†’ Easy Template Flow screen](https://help.appliger.com/easy-templates-for-jira/use-easy-templates-app-s-screen-flow.md) * Prefill - template used in [App โ†’ Easy Template Flow screen โ†’ Prefill option](https://help.appliger.com/easy-templates-for-jira/use-easy-templates-app-s-screen-flow.md) ![image-20260415-182553.png](https://help.appliger.com/__attachments/a_b31a51d6d233c3c4bf2476563ef5ca82cc98d4ac7226505fe435f538732dda13/image-20260415-182553.png?cb=9ca44219a0c982ec20b3f383c103cc4b) ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-04-19 **๐Ÿ“ฆ Easy Templates: v9.2.0** The Manage Templates interface now includes a "Last used" column. ## **โœจ** What's new? NEW The new "Last used" column simplifies the process of tracking template usage, making it easier to identify and remove templates that are no longer needed. ![image-20260420-211346.png](https://help.appliger.com/__attachments/a_332adf9d09859d173a58397fc4ea65677a5940c9ea6b67b532ae43beff4091be/image-20260420-211346.png?cb=420c5b1c65bc714aac03a09af81f46a7) ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-07-10 **๐Ÿ“ฆ Easy Templates: v9.9.0** Architectural and UI improvements, bugfixes. ## **โœจ** What's new? NEW **Audit logging**: added comprehensive logs for all template management operations, including variable IDโ†’label mapping. **Progress reporting:** added detailed states and asynchronous progress definitions. ## ๐Ÿ› ๏ธ Improvements \& changes Improved **UI improvements** * Renamed app menu item from "Templates" to "Easy Templates" in the Apps menu and Project/Space board menu for consistency. * Added "Easy Templates" page header. * Added breadcrumbs on the template edit page. * Improved loading state and dynamic empty message for audit log. ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-08-27 **๐Ÿ“ฆ Easy Templates: v11.36.0** Template links management ## **โœจ** What's new? NEW You can now manually link Jira issues within a template or outside its structure directly from the template management screen ### Before ![Links before.png](https://help.appliger.com/__attachments/a_039216e56017eef820f255ff1f247478f8e9a41c58ca3c49bcb2e979c10c2704/Links%20before.png?cb=4d0b9de8ac37c306aa716e8e30cf8001) ### After ![Links after.png](https://help.appliger.com/__attachments/a_4985392fbec0d54c155491ee4665add76b1348452caf1f5a3730fb3fbfc924a9/Links%20after.png?cb=47e03ce246c269123f4270a246f6cf5e) If you add a new relation to an existing work item in the template, the relation appears only in that issue. The correct link is created when new issues are generated from the template. E.g. * Setting up "Task 1" blocks "Task 2". * The "blocks" section appears in "Task 1". * It does not appear in "Task 2". * The actual link still exists. This is known behavior. ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # 2026-08-30 **๐Ÿ“ฆ Easy Templates: v11.39.0** Support Cross-project templates ## **โœจ** What's new? NEW Epic templates with child issues in different projects are now supported. ### Example Assume the template with the following structure: `Proj A Epic` * `Proj A task 1` * `Proj A task 2` * `Proj B task 1` * `Proj C task 1` When creating an issue from this template, the user chooses a destination project (for example, Proj Y). Work items from Proj A are created in Proj Y; items from Proj B and Proj C remain in their original projects. This addresses a long-standing request and is useful for onboarding: administrative tasks can remain in HR, while hardware and software setup tasks stay in DevOps. ## **๐Ÿ“˜ Helpful Docs** * [**Dynamic Fields and Expressions**](https://appliger.atlassian.net/wiki/spaces/ET/pages/edit-v2/3714121729) * [**Expression examples and limitations**](https://help.appliger.com/easy-templates-for-jira/dynamic-fields-automate-calculations-with-expressions.md#Example-expressions) --- language: "en" --- # Advanced Roadmaps If you are using Advanced Roadmaps on Jira Software Premium or Enterprise - you can get additional benefits from using Easy Issue Templates for Jira. Once you set "Advanced Roadmaps hierarchy levels" and create Hierarchy Level 2 (e.g. Initiative) structure - you can save the whole Initiative structure with child Epics, tasks, and subtasks as a Template: ![image-20240419-122525.png](https://help.appliger.com/__attachments/a_27269d2fe35518c0ea33ce7ecd64dcf19793f2b629ee3929042a842a7f5de7b4/image-20240419-122525.png?cb=f0bd68b69c13f3b20eb0741ab556f76e) Please note that we currently don't support N issues levels, e.g. level +3 of the Advanced roadmaps issue hierarchy that goes beyond Initiative. Though, It's in our roadmap. If you need that hierarchy support - [let us know](https://appliger.atlassian.net/servicedesk/customer/portal/1)๐Ÿ“ง ! --- language: "en" --- # Agreements * [AppLiger Apps: Cloud Security Policy](https://help.appliger.com/easy-templates-for-jira/appliger-apps-cloud-security-policy.md) * [Service Level Agreement (SLA)](https://help.appliger.com/easy-templates-for-jira/service-level-agreement-sla.md) * [End User License Agreement](https://help.appliger.com/easy-templates-for-jira/end-user-license-agreement.md) * [Privacy Policy](https://help.appliger.com/easy-templates-for-jira/privacy-policy.md) * [Terms of Service (ToS)](https://help.appliger.com/easy-templates-for-jira/terms-of-service-tos.md) * [AppLiger AI Usage Policy](https://help.appliger.com/easy-templates-for-jira/appliger-ai-usage-policy.md) *** ** * ** *** For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # AppLiger AI Usage Policy Effective Date: 2026-06-01 **Last updated:** September 2026 AppLiger uses artificial intelligence functionality only where it supports specific product features and provides a clear benefit to users. This policy explains how AI-enabled functionality is used in AppLiger products and how customer data is handled. ## AI functionality in AppLiger apps Easy Issue Templates for Jira includes limited AI-enabled functionality through **Atlassian Rovo**. The Rovo functionality may assist users with actions such as working with templates through conversational interactions. AI features are supplementary to the core functionality of the app and are not required to use Easy Issue Templates. Customers can disable Rovo functionality where supported by Atlassian and AppLiger configuration. ## How AI processing is provided AppLiger's current Cloud apps are built on **Atlassian Forge** and run on Atlassian infrastructure. AI functionality provided through Rovo uses Atlassian's AI platform and associated controls. AppLiger does not operate separate AI infrastructure for this functionality. ## Data used by AI features AI functionality may process information necessary to complete the action requested by the user, subject to the user's Jira permissions and the capabilities provided by Atlassian Rovo. AppLiger follows data-minimization principles and does not intentionally provide AI features with access to data that is not required for the requested functionality. Access to Jira data remains subject to applicable Atlassian authentication and authorization controls. ## Customer control Use of AI-enabled functionality is limited to the features where it is explicitly provided. Customers remain in control of whether AI functionality is available within their Atlassian environment, subject to Atlassian's administrative controls and applicable AppLiger configuration. Core Easy Issue Templates functionality does not depend on AI. ## Security and privacy AI-enabled functionality is subject to AppLiger's existing security, privacy, and access-control practices. AppLiger does not use AI functionality as a substitute for authentication, authorization, or security controls. For more information about AppLiger's security and privacy practices, see: **Security** **Trust Center** **Agreements, Privacy and Security Documentation** ## Responsible use AppLiger aims to use AI functionality in a transparent and proportionate manner. AI-generated responses or actions may not always be complete or accurate, and users should review AI-assisted outputs where appropriate before relying on them for important decisions or workflows. AppLiger may update or expand AI-enabled functionality over time. Material changes to how AI is used or how customer data is handled will be reflected in this policy and other applicable documentation. ## Contact Questions about AppLiger's use of AI can be submitted through: **Email:** [security@appliger.com](mailto:security@appliger.com) **Support portal:** --- language: "en" --- # AppLiger Apps: Cloud Security Policy Effective Date: 2026-07-01 ## Introduction This document outlines the security practices for all recent versions of AppLiger applications, listed on the Atlassian Marketplace, when used on Atlassian Cloud, including * **Easy Templates for Jira** * **Easy Progress -- Hill Charts for Jira** * **Easy Action Items -- Checklist Templates \& Automation** * **Easy Markdown Exporter** All AppLiger cloud apps are built using the **Atlassian Forge framework** and **Runs on Atlassian**. This means: * The app execution environment is **fully hosted and secured by Atlassian.** * App data is stored **inside the customer's Atlassian tenant**, not on AppLiger servers. * AppLiger does **not host customer environments**, nor do we store or access sensitive Atlassian user data such as passwords or payment information. To understand what data Atlassian stores and processes, refer to Atlassian's official documentation: * Atlassian Cloud Security: * Forge Security \& Architecture: * Atlassian Privacy Policy: Your Personal Information's security is important to us, but no method of digital transmission or storage can be 100% secure. We rely on Atlassian's industry-leading security standards and continuously improve our applications to ensure maximum safety. ## Data Storage ### All AppLiger cloud apps Runs on Atlassian This includes: * **Easy Templates for Jira** * **Easy Progress -- Hill Charts for Jira** * **Easy Action Items -- Checklist Templates \& Automation** * **Easy Markdown Exporter** ### Storage Architecture * All processing occurs inside Atlassian's secure Forge runtime. * All data is stored directly in the customer's Atlassian Jira Cloud tenant, using: * Forge Storage (encrypted at rest) * Entity Properties (scoped to project, issue, or app) ### No AppLiger External Storage AppLiger does **not store**: * Jira issue data * Usernames or emails * Project or space content * Jira Account IDs (outside of Forge) Our infrastructure (AWS/Cloudflare) is used only for: * Serving the marketing website * Optional documentation or onboarding content Not for storing customer app data This applies to all recent Cloud app versions available on the Atlassian marketplace. ### Data Residency Because our apps use only Forge storage, data residency automatically follows the customer's Atlassian site residency: * Atlassian Data Residency Overview: ## Backups App data stored via Forge Storage or Entity Properties is backed up as part of the customer's Jira Cloud environment. Backups and disaster recovery are fully managed by **Atlassian** under their cloud platform guarantees: * Atlassian Cloud Reliability: AppLiger does not perform separate or external backups of customer data. ## Development \& Security Practices AppLiger follows modern software engineering and security practices: * Regular peer code reviews * Static code analysis and automated testing * Security testing aligned with Atlassian Marketplace requirements * Least-privilege permissions (Forge Scopes) * Secure app signing \& deployment via Atlassian Forge * Participation in Atlassian Marketplace Security Programs Relevant links: * Forge Permissions (Scopes): * Atlassian Marketplace Security Requirements: * AppLiger Trust Center: [https://trust.appliger.com](https://trust.appliger.com/) ## Data Access AppLiger can only access data explicitly granted by the customer via the app installation: * Access is always scoped to the selected Jira site * All access happens through Atlassian's secure APIs * No direct database access or external data export occurs * AppLiger cannot view or access customer Jira content unless the customer intentionally shares it via a support ticket ## Data Transmission All communication between the app and Atlassian Cloud uses HTTPS/TLS 1.2+ encryption. Forge-hosted code executes within Atlassian-controlled infrastructure and does not send data outside Atlassian's environment. ## Contact For questions regarding this document or security practices: **AppLiger sp. z o.o.** Dajwรณr 14/17, 31-052 Krakรณw, Poland [Contact Us](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # Apply Template to existing issue Applying pre-defined templates to existing issues in Jira can significantly streamline your workflow. The [Easy Templates for Jira app](https://marketplace.atlassian.com/apps/1219112/easy-templates-for-jira-issues?hosting=cloud&t) simplifies this process, allowing you to quickly update issues with standardized information. Follow these steps to apply a template to an existing issue in Jira Cloud! ## Instructions **Step 1:**Accessing the Apply Template Feature * **Locate the Issue**: Navigate to the issue you wish to update. * **Open the Issue Menu:** Click on the "โ€ขโ€ขโ€ข" (More) icon at the top-right of the issue view. * **Select "Apply Template":** From the dropdown menu, find and click on "Apply template". This opens the template application interface. ![Apply Template.png](https://help.appliger.com/__attachments/a_050da9a8134b6fa58abe42854f8373df501d1d75489ccded0399936e34de1bbd/Apply%20Template.png?cb=ee033dc75d78483bb0a9d050760022e4) **Step 2:**Choosing the Right Template * **View Available Templates:**A list of templates will be displayed. These templates are based on the scope you or your team have set---either global or specific to your project. * **Select a Template:** Browse through the available templates and select the one that fits your needs for the current issue. * **Apply the Template:** After selecting the appropriate template, click on the "Apply" button. This action will start the process of updating the issue with the template's predefined fields and data. ![2. Choose Template.png](https://help.appliger.com/__attachments/a_560dad4a2ea03e51d464d35b6adb9f27e4be0c1141b7932c99afeba379154c85/2.%20Choose%20Template.png?cb=6107f15ac2d53f16c27dfe8372f4db8e) **Step 3:** Confirming the Update * **Review the Changes:** Once you click "Apply", the issue will be automatically updated with the data from the chosen template. Take a moment to review the changes to ensure that all information is accurate and relevant to the issue. * **Finalizing the Update:** If the updated information is correct, no further action is needed. If adjustments are required, you can edit the issue manually as usual. ![image-20211026-105613.png](https://help.appliger.com/__attachments/a_bd705d2c004e2bd521bf486e5f6792339b248dd3e8b65d2c22c6b745943753f4/image-20211026-105613.png?cb=da42dc47f2a2aabd1d44d50fca56bd76) ### Additional Tips * **Customize Templates**: Consider customizing your templates to better suit different types of issues. * **Frequent Review**: Regularly review and update your templates to ensure they remain effective and relevant. * **Training**: Ensure your team is familiar with how to use templates for maximum efficiency. By utilizing the [Easy Templates for Jira app](https://marketplace.atlassian.com/apps/1219112/easy-templates-for-jira-issues?hosting=cloud&t) effectively, you can enhance the functionality and efficiency of your Jira instance, leading to smoother project management and team collaboration. *** ** * ** *** For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # Archive - Release Notes ## 1.8.26 Jira Cloud. 2022-09-09 * Fixed order of child/sub-tasks * Improved order of Variables display ## 1.8.21 Jira Cloud. 2022-08-05 * Added: Ability to copy a template issue in order to extend the existing template instead of making a new one * Fixed: Hide unsuccessful issue creation error messages on the next try ![image-20220805-164025.png](https://help.appliger.com/__attachments/a_0030d34062683025c1ff15ea1e8b1051f53dc29ab87b58c567d48cc46a1639d7/image-20220805-164025.png?cb=64c66556f7789bf81c6127f0327ce995) ## 1.8.18 Jira Cloud 2022-05-27 * Added child tasks' tree for better navigation while managing templates * Added an ability to Edit/Delete child/subtasks in Manage Template tree ![image-20230111-083911.png](https://help.appliger.com/__attachments/a_f86331f60385e26029178ac2cf4d3499f61cafe1dbf6a188ce5e610224ddd2c3/image-20230111-083911.png?cb=e665571f8c9832e45421fbf0c3783d1c) ## 1.8.13-AC Jira Cloud 2022-03-13 Project Admins now can manage the templates! If you are Project Administrator - go to Project Settings โ†’ Apps โ†’ Easy Templates Manage templates: change templates' fields, scope, delete, copy templates from there. ![image-20220313-002306.png](https://help.appliger.com/__attachments/a_5ec07c68897bdd11fa9db94d5ad306fc5e79dd7030425e743a4bff98833840c1/image-20220313-002306.png?cb=c32d8e6018e05a2cf924fd6ec9eb1d0f) ## 1.8.10-AC Jira Cloud 2022-01-25 * Added ability to fill Variables while Applying template and various improvements. Now, after while choosing a template in [Apply Template to existing issue](https://help.appliger.com/easy-templates-for-jira/apply-template.md) flow - you can fill variables. ![image-20220125-100936.png](https://help.appliger.com/__attachments/a_a13ff30b5c21b4f395479468cbc132b1148c045e5aa15b87b270a8fefd3b7c93/image-20220125-100936.png?cb=55711de516b4e15e6c012aa0a0070f4e) ## 1.8.2-AC Jira Cloud 2021-10-26 * Implemented [Variables \& Forms](https://help.appliger.com/easy-templates-for-jira/variables.md) functionality ## 1.8.1-AC Jira Cloud 2021-04-08 * implemented [Copy Template](https://help.appliger.com/easy-templates-for-jira/copy-template-cloud.md) functionality ## 1.8.0-AC Jira Cloud 2021-01-21 * Fixed: Epic Template structure was not complete * Fixed: Child items were saved in reversed order * Improved: Pre-select current project when creating a template ## 1.6.0-AC Jira Cloud 2020-10-01 ### Epic Templates support * Implemented support for Epic โ†’ Task โ†’ Subtask template hierarchy (aka deep Epic Clone) * Improved Templates \& scope management * Fixed a few minor issues Available on Jira Cloud only! ### Details Create a structure with Epic with child Issues and related Subtasks. Save it as a template. Now you are able to create a new Epic from the Template having all child Issues \& Subtasks automatically created! ![Epic Templates Banner.png](https://help.appliger.com/__attachments/a_95536456a8985abd3af2b6ab8e475ffd5978c8d83915db5cffadd7080171bb3f/Epic%20Templates%20Banner.png?cb=af674872223901f40f2f2e06b2e1d13f) ## 1.1.1 Jira Server and Data Center 2020-05-09 * โ€‹Fix error "Number value expected as the Sprint id error" while saving a template from Scrum related issue ## 1.1.0 Jira Server and Data Center 2020-04-12 * Fixed an issue with using Easy Templates and DEISER Profields addon on the same instance ## 1.5.17-AC Jira Cloud 2020-03-01 โ€‹Skip disabled template fields while applying a template. ## 1.5.16-AC Jira Cloud 2020-01-07 โ€‹Fixed typeahead on Template selection form ![Projects - Jira 2020-01-07 11-33-03.png](https://help.appliger.com/__attachments/a_4bec83bdf6f705d2c580854a0573ced19229082223be2b826b270204ac6e308c/Projects%20-%20Jira%202020-01-07%2011-33-03.png?cb=6bd131642de1a4bf448238de99cb779c) ## 1.5.15-AC Jira Cloud 2019-12-18 Improved Templates Management 1. Removed selection of optional fields while template saving 2. Added ability to Edit more than "Summary" and "Description" 3. Added ability to switch fields on/off 4. 1. While new issue creation - disabled fields will be ignored 2. Check "Understanding of disabling Template field" section 5. Added validation on New Issue creation 6. Fixed saving of Subtasks assignees Check the [Enabling template fields. Cloud](https://help.appliger.com/easy-templates-for-jira/enabling-template-fields-cloud.md) for a better understanding of the new template editing functionality! **Note:** this is a beta feature. Please [report any problems](https://appliger.atlassian.net/servicedesk/) you may encounter while templates management and issue creation. ## 1.5.14-AC Jira Cloud 2019-09-25 Allow Closing New Issue dialog with a button when nothing is selected ![image (16).png](https://help.appliger.com/__attachments/a_4d71dccf1b6a47fc4a8aa9ccccc2ecf21676571e39894aab8e76f931ffc5e293/image%20(16).png?cb=0ee6bfea392ec519b19aa43d44735bff) ## 1.5.11-AC Jira Cloud 2019-09-22 * Fixed 32KB limit on Template creation that was caused by big list of subtasks * Introduced own backend to work with templates faster * Template editing will be limited as currently, it lacks the validations required to guarantee its integrity and causes issues in some situations. * This limitation is not related to storage changes. It's a temporary, improved version will be released as soon as possible. * Removed Easy Templates actions under Glance View and Quick Access button as Atlassian has fixed an issue why we had to introduce that view in version v1.5.8-AC Jira Cloud **17 Aug 2019** * Check [Reason For changes](https://community.developer.atlassian.com/t/problem-with-context-parameters-used-in-url-in-app-descriptor-value-always-being-empty-in-some-jira-instances/30631) ## v1.5.8-AC Jira Cloud 2019-08-17 After previous release we've decided to change "Easy Templates Actions" location so they don't take central panel space. * Templates Actions moved to Issue Glance View (for New Jira UX) * "Save Template", "Apply Template" actions available on a right side bar ![ET_v2.png](https://help.appliger.com/__attachments/a_3895480650819cf8eff8ea802f5406902b6e38666051dbc6602abe9c25cb3e1a/ET_v2.png?cb=5dd39d5fc5d7fc3478f48255d55b9ecf) ![ET_v2_Save.png](https://help.appliger.com/__attachments/a_6f8689647f60530c9beb489ca81a1435c3c0b18c20cabafb87fa3540ebead9d4/ET_v2_Save.png?cb=47d9f1cea25e855db31ee44ec73fca39) We stiil going to keep "Save" and "Apply" actions as a part of Issue Menu items. So on A JSD (Jira Service Desk) Projects is won't be shown on Glance view, which is simply not available there, but on a menu ![ET_v2_Save Menu.png](https://help.appliger.com/__attachments/a_456f09edf92ff502754b3230fca55804c595d431dd2e669da0a2599834c5472f/ET_v2_Save%20Menu.png?cb=f8163212d1cd6f9c975d98a1ff11e9b2) **Reason for the changes**: recent regression issues found in Jira functionality ## v1.5.6-AC Jira Cloud 2019-08-13 * Change "Save/Apply templates flow" to fix the issue of not receiving context parameters from Jira * Use the quick add menu in Jira Issue to show "Easy Templates" action buttons. ## v1.0.22 Jira Server 2019-05-17 * Added support of [PCF-Single Autocomplete Fields](https://confluence.cprime.io/display/KCF/PCF+-+Single+Autocomplete) from Power Custom Fields add-on * Fields can be saved in a template * Fields will be filled automatically while new issue creation from template ## v1.0.21 Jira Server, v1.5.4-AC Jira Cloud 2019-05-05 * Added: Set the current user as a reporter when creating from a template. Ignore reporter value saved in template ## v1.5.3-AC Jira Cloud 2019-04-30 * Compatibility with Jira Cloud REST API GDPR changes ## v1.0.20 Jira Server 2019-04-10 * Fixed issue creation from the template on IE * Fixed navigation from the dashboard on IE ## v1.0.19 Jira Server, v1.5.1-AC Jira Cloud 2019-03-24 * Fixed saving Templates in Service Desk projects * Fixed applying Account from Tempo Timesheet add-on to the created issue ## v1.0.16 Jira Server 2019-03-22 * Fixed showing Apply dialog on Issues Search ## v1.5.0-AC Jira Cloud 2019-03-21 * Minor bugfixes * removed not required permission scope ## v1.4.0-AC Jira Cloud 2019-03-20 * Minor bugfixes * Added ability to create subtasks via Apply flow ## v1.0.14 Jira Server 2019-03-12 * Fixed creation of subtasks which contains required fields ## v1.0.10 Jira Server 2019-03-04 * Added ability for non-admins to create a new issue from the template * Fixed issue with subtasks creation via Apply flow Known issue: non-admin Users have access to Manage Templates section but can't save the changes ## v1.0.4 Jira Server 2019-02-25 Minor bugs fixed and bundle size optimized. ## Jira Server Released! v1.0.0 . 2019-02-10 ## 1.3.8 Apply Template 2019-01-14 Read more: [Apply Template](https://help.appliger.com/easy-templates-for-jira/apply-template.md) ## 1.3.7 Prefill "Create Issue" form with Template's data 2019-01-12 Use this flow if you need to correct or add more details to your issue prior to creation! **Please note**: sub-tasks won't be auto-created with this approach **Step 1.** Open "**Templates** " from sidebar and click "**Prefill New Issue** " **Step 2.** Go to "**Create Issue** " screen and add necessary details **Step 3.** Click "**Create**" and get to the new item! Read more on [Create Issue from Template](https://help.appliger.com/easy-templates-for-jira/create-issue-from-template.md) ## 1.3.6 Save Component per sub-task View 2019-01-08 ## 1.3.5 Support next-gen projects 2019-01-07 ## 1.3.4 Minor version update 2019-01-07 ## 1.3.3 Pre-select project while new issue creation 2019-01-06 ## 1.3.2 Minor bugfixes 2018-12-09 ## 1.3.1 Select optional fields to save 2018-12-01 ## 1.3.0 Required Scope Changes 2018-11-22 --- language: "en" --- # Audit Log Use **Audit Log** to track and troubleshoot template actions like creating work items and applying templates. ![image-20251020-214850.png](https://help.appliger.com/__attachments/a_99f7d5ef5e5d6937fd7944d89792b92884cda865752acadf10966faaf3013397/image-20251020-214850.png?cb=24f0a0b6e9ee129dc3defca14c38080e) Fields available: * Date and Time (local) * Status: SUCCESS or FAIL * Operation: `Create work items` or `Apply Template` * Template: link to the used template * Details (expandable) * Actor * Project * Result * Params: like variables, project id * Source: * GIC - template used in the [Global Issue Create screen](/easy-templates-for-jira/use-jira-native-create-issue-screen-integration.md) * Manual - template used in [App โ†’ Easy Template Flow screen](/easy-templates-for-jira/use-easy-templates-app-s-screen-flow.md) * Prefill - template used in [App โ†’ Easy Template Flow screen โ†’ Prefill option](/easy-templates-for-jira/use-easy-templates-app-s-screen-flow.md) * Error (if applicable) ๐Ÿ’ก **To see exact items created from the template:** expand the log entry and click the Result link (e.g., ++5 issues processed++ ). You will navigate to the **All Work** view with the relevant issues selected. ![image-20251020-213926.png](https://help.appliger.com/__attachments/a_1fa241d88f3ad8384fabd5ff66dae3dd0f74269b0b3dbeaae938884042267200/image-20251020-213926.png?cb=db6cff65d470cb233bf3ee23169f809c) --- language: "en" --- # Automation & REST API Easy Issue Templates for Jira enables you to use Issue Templates through [Jira Automation](https://www.atlassian.com/software/jira/features/automation) by leveraging specific triggers or integrating with other tools via REST API. This functionality ensures that your workflows remain interconnected and efficient. ## Use Cases * [**Scheduled time-based Issues creation:** Create monthly Financial tasks](https://help.appliger.com/easy-templates-for-jira/scheduled-time-based-issues-creation.md) * [**Sub-tasks creation:**Apply QA subtasks on the User Story transition](https://help.appliger.com/easy-templates-for-jira/sub-tasks-creation-for-existing-issue.md) * [**Bulk templates usage:** Create issues when a New Project created](https://help.appliger.com/easy-templates-for-jira/create-issues-when-new-project-created.md) * [**Create issues once a Service Desk ticket is raised**: New employee onboarding process](https://help.appliger.com/easy-templates-for-jira/create-issues-once-a-service-desk-ticket-is-raised.md) ## โœ… Enable the Automation feature You must have **System Admin** permissions 1. Make sure **Easy Issue Templates** is installed. 2. Navigate to **Apps โ†’ Manage Apps โ†’ Easy Templates โ†’ Settings**. 3. Enable **Automation toggle**. ![Group 15(2).png](https://help.appliger.com/__attachments/a_81960f267e4da7b944a767443a3551df4a156a2645d0c0bfe0aa0d7d30065a16/Group%2015(2).png?cb=c91d10d2d2d011fae2d81744dc75413f) Once enabled, Project Admins can configure template-specific webhooks and payloads. ## ๐Ÿ”ง Set-up Automation per Template You must have **Project Admin** or **System Admin** permissions ### Generate Web Request URL and Payload 1. Go to **Manage Templates** โ†’ choose a Template โ†’ **Automation**. 2. Toggle **Enabled**. 3. Click **Generate new URL** to create a unique webhook URL for that template. This URL will be used in your Jira Automation rule or other external tools. ![Automation ON(1).png](https://help.appliger.com/__attachments/a_83659d4abd86ee73ad733e3c8ce8a9147e24142b8207aace24df64391818430f/Automation%20ON(1).png?cb=8e29cc101b23f098572055cdce801261) ### Prepare Payload 1. Choose **Operation**: 1. **Create Issues** -- Generates new issues from the template. You'll need the target Project ID, which you can set dynamically using a smart variable (e.g., `{{project.id}}`) in Jira Automation or choose from the list provided. 2. **Apply Template** -- Applies the template to an existing issue, including sub-tasks or child issues creation 2. Review**Variables** If your template uses variables, check and prepare their values. 3. Review**Payload:** You'll use this payload when configuring the webhook action. ![Automation Payload(2).png](https://help.appliger.com/__attachments/a_36ab07b077d51bc507e1f3a90328fbedd117b3450c9471d0e4b68b85d74b5258/Automation%20Payload(2).png?cb=a1e3d8cc7155af0f16ebe72834bc11f9) ## โš™๏ธ Creating a Jira Automation rule You must have **Project Admin** or **System Admin** permissions 1. Go to **Jira Automation** (Project or Global settings). 2. Create a new **Automation Rule**. 3. Select any **Trigger** you need. 4. Add an **Action** โ†’ **Send web request**. 5. Paste the **Web Request URL** generated in your template's Automation settings. ( 6. Use **POST** as the HTTP method. 7. Choose **Custom Data** as the **Web request body**. 8. Paste your prepared **Payload** into the **Custom Data** field. 9. Save and enable the **Rule** NEW: add the "actor" to the payload to set the **Reporter** of the created issues Example: JSON { "operation": "create-issues", "actor": "put account ID or email here", "project": "{{project.id}}" } ![Automation Jira Setup.png](https://help.appliger.com/__attachments/a_9b58c70263ef7e7a17feb7683d7daea63a732ae7b2347eedbbbc0b4689e00025/Automation%20Jira%20Setup.png?cb=20b7832f1f27a801b8c566fbdba0786e) --- language: "en" --- # Best Practices Follow these best practices to maximize efficiency, maintain clarity, and ensure a smooth experience when using Easy Issue Templates in Jira. 1. **Define Only the Relevant Scope** * Keep templates focused on specific use cases to avoid clutter. * Although our app supports global templates, it's best to create tailored templates for specific projects, issue types, or teams to ensure relevance and improve usability. * Enable Only Needed template Fields to keep issues concise, reliable, and fault-free. 2. **Use Clear and Consistent Naming** * Name templates in a way that clearly describes their purpose (e.g., "Bug Report - Critical" instead of just "Bug Template"). * Use prefixes or categories if managing multiple templates (e.g., "Dev - Feature Request" vs. "Support - Incident Report"). 3. **Leverage Dynamic Variables for Flexibility** * Use dynamic variables `<>` for templates that require contextual data instead of static values. * Ensure templates remain adaptable to different users and scenarios. 4. **Keep Descriptions Clear and Actionable** * Write clear instructions in the issue description to guide assignees. * Use Markdown formatting to highlight key details, steps, or links. 5. **Regularly Review and Update Templates** * Audit templates periodically to remove outdated ones and improve clarity. * Adjust fields and content based on evolving team needs and feedback. 6. **Manage Access and Permissions Wisely** * Restrict template editing rights to prevent unwanted modifications. * Share relevant templates with the right teams or users to maintain efficiency. 7. **Train Your Team for Maximum Adoption** * Provide documentation or internal guides on how to use templates effectively. * Organize short training sessions to onboard team members. * Ensure team members know where to find templates and how to apply them. * Share our (AppLiger's) contact details for support in case of questions or issues. --- language: "en" --- # Checklist for Jira | Enterprise This instruction applies to the following app: [Checklist for Jira \| Enterprise](https://marketplace.atlassian.com/apps/1211562/checklist-for-jira-enterprise?hosting=cloud&tab=overview) by Herocoders By integration, we consider an ability for users to save Checklist app values as a part of Easy Template's issue template and then restore/add checklist value to the created Jira issue. There are two types of integrations that are possible: * Option 1. Using `Checklist Text` custom field * Option 2. Using issue labels ## Option #1. Integrate Checklist for Jira with Easy Templates using `Checklist Text` custom field ### How to save the issue checklist as part of the Issue Template 1. First of all, make sure to enable the custom fields integration within the Issue Checklist for Jira "Global Settings". 1. Go to *Jira settings* โ†’ *Apps* โ†’ Checklist for Jira \| Enterpriseโ†’ *Global Settings* 2. Enable***Save local checklist items to Jira custom fields*** ![image-20240911-200109.png](/__attachments/a_0ad56fd87fca597c9ebd042dc12e9d2c761c30b1810c120c03dff2b235c8091c/image-20240911-200109.png?cb=2f0ff4f6de84aac8516bd379a95a9df4) 2. Make sure `Checklist Text` is added to Jira Issue Edit screen in Screens configuration 3. To make Jira issue screens less cluttered - you may hide the custom field using "Configure" option in Issue screen 4. Add checklist items 5. You can see if an issue has been updated by showing the "Checklist Text" field as a column in the advanced issue search. ![image-20240911-201020.png](https://help.appliger.com/__attachments/a_80ddcfd172610b1a22ce9f9c1ece637d7250ef9b370cf247a72cc8a3595153de/image-20240911-201020.png?cb=eb7b92a1bb2f56f6b1e376951bb77006) 6. Save an issue template [via Easy Templates app.](https://help.appliger.com/easy-templates-for-jira/create-save-template) `Checklist Text` field values would be saved into the template as well. ### How to restore saved checklist from Issue Template 1. That's it! Now, when you create a new issue from the Template - Checklist would be populated with the saved checklist automatically! ๐Ÿš€ ### How to see and manage saved checklists in Issue Template 1. Make sure, the `Checklist Text` field is added to the global Create Issue Jira screen 2. Go to Apps โ†’ Easy Templates for Jira 3. Open Template and you'll see the saved template as Custom fields in the checklist app's text format ![image-20240911-202135.png](https://help.appliger.com/__attachments/a_f594a14a4af6d40850aa3d613f63d2136e050b7b4bbbffe6ed5c4b04abdbc906/image-20240911-202135.png?cb=9d7c57d118ca00eb60aedff3e83ea84b) **Mind the formatting!** Since **Easy Templates** moved to Forge and Atlassian uses API v3, the "Checklist Text" field now uses Rich Text format. Manually typing text values corrupts checklist items generated from the template. To fix this, preserve**Issue Checklist** markup and properly enter its value into the **Checklist Text**field by following these steps: * Go to the existing Jira issue * Open the issue checklist app * Enter checklist edit mode (pen) * Copy text and markup * Return to the template management * Find the "Checklist Text" field * Paste the value into the "Checklist Text" field using **CMD(CTRL)+SHIFT+V** * so that the markup format is preserved ## Option #2. Integrate Checklist for Jira with Easy Templates using issue labels In short - consider using an approach, described in an article . 1. Save Checklist template 1. assume you need to create Definition of done checklist 2. add checklist to an issue 3. Save as template ![image-20240912-114103.png](/__attachments/a_ffd4d260523401f173c1225e6308f33b3ca966995c52827df4a090169dbe669d/image-20240912-114103.png?cb=44a7d326de96b3de24f35d80b09dba11) 4. Give it the name "defninition_of_done" 2. Create an Issue label called "definition_of_done" ![image-20240912-114014.png](https://help.appliger.com/__attachments/a_6862afc8324245bfb274e86180cf32f124532560e130614f8305889a0d1da130/image-20240912-114014.png?cb=3313869040317bdb5ee4cdb8d965e2f2) 3. [Save Jira issue as a template](https://help.appliger.com/easy-templates-for-jira/create-save-template) via the Easy Issue Template app ![image-20240912-114323.png](https://help.appliger.com/__attachments/a_6a3e5d6a44b6cb092ec8f6e4c2109aa31f162e39b59f385f37808b36c9ccad82/image-20240912-114323.png?cb=098046a606922af7d14004344dffed11) 4. The issue Template should look like Having label added ![image-20240912-114615.png](https://help.appliger.com/__attachments/a_8ffd2fc2746fb3df2484fd36a284b46d3052e8029c0f2f5dafabf3ea813e2a01/image-20240912-114615.png?cb=3ea698e8017dd8b1f5648d84f88b5bc9) 5. Now, when creating a new issue from that template, the checklist template will be automatically applied based on the defined issue label per[checklist functionality](https://docs.herocoders.com/checklist/adding-templates-to-issues) ๐ŸŽ‰ --- language: "en" --- # Cloud to Cloud Migration In this article, you will learn how to migrate Templates content created with Easy Templates app from one Cloud instance to another. There's no automatic migration path available for now. We already have a proper feature request in our backlog. ## How to migrate Easy Templates to Cloud from another Jira Cloud instance * While on a source Jira Cloud instance - create Jira issues and it's related structures from existing templates on your selected Jira project(s) 1. Use all the Templates you want to migrate to Cloud * Proceed with your Jira migration path according to the defined plan using selected tool * Install Easy Templates for Jira Cloud on target instance * Once your Projects and Jira issues migrated to Cloud - re-save tickets (=re-create) as the new Templates on Cloud. * Now you can use your Easy Templates for Jira Cloud again! For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # Cloud vs Server/Data Center version difference In this section, we will explore the distinctions between Easy Templates for Cloud and Easy Templates for Server/Data Center versions. | **Feature**โญ | **Cloud**โ˜ | **Data Center**๐Ÿ  | |--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| | Issue Template | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Issue Template with sub-tasks | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Epic Template with child tasks | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Create issue from Template | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Prefill Templates (use Jira Create Issue Screen) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![cross mark](https://help.appliger.com/__attachments/a_649f24d4303c2c4ab0afb0734a836850fe192829b6c761f0c3a1613a8ceeb4f1/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | Apply Templates | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Manage Template | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Use Variables | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Enable/Disable template fields | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Support of Assets/Object field type | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![cross mark](https://help.appliger.com/__attachments/a_649f24d4303c2c4ab0afb0734a836850fe192829b6c761f0c3a1613a8ceeb4f1/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | Manage Template by Project Admin | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://help.appliger.com/__attachments/a_8de20659ba82ac3a87b49a0c22719f5927b8e1263a4eaf32789478ca04acacb3/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # Compliance and audit preparation with Dynamic Fields The Compliance and audit preparation work is usually similar each time, but the timeline depends on the audit window or reporting deadline. With **Easy Templates for Jira** , you can create one reusable template and calculate all task dates automatically from a single **Audit Date** variable. Expressions can use template variables, parent fields, root fields, and supported date functions such as `plusDays()`, `minusDays()`, and `minusWorkingDays()`. This is useful for planning evidence collection, policy reviews, control checks, internal reviews, and final submission --- without manually updating every issue for each audit cycle. Dynamic Fields are calculated during issue creation, so every new audit run starts with a ready-to-use timeline. ## Example audit template structure Example parent issue: **Compliance audit preparation** Example child issues or subtasks: * Define audit scope * Review policies and procedures * Collect evidence * Validate control ownership * Internal readiness review * Remediate missing items * Final audit package review * Submit evidence to auditor * Track auditor follow-up items ## How to set it up ### 1. Create your audit template Create a template with the issue structure you want to reuse for each audit or compliance review. For example, add one parent issue and a set of child issues or subtasks for the main preparation steps. ### 2. Add an `Audit Date` variable Create a template variable called: `Audit Date` This variable will be filled in when the template is applied and used to calculate dates across all audit tasks. Easy Templates supports variable references using `variables()` or the shorter `var()` form. Use this syntax to reference it in expressions: var("Audit Date") ### 3. Switch date fields to Expression mode For each task where the date should be calculated automatically: 1. Open the field `...` menu 2. Choose **Use expression** 3. Enter your expression 4. Save the template That field becomes a Dynamic Field, and its value is calculated automatically during issue creation. ## Example expressions for audit tasks ### Define audit scope 30 days before the audit date: var("Audit Date").minusDays(30) ### Review policies and procedures 20 days before the audit date: var("Audit Date").minusDays(20) ### Collect evidence 15 working days before the audit date: var("Audit Date").minusWorkingDays(15) ### Validate control ownership 10 working days before the audit date: var("Audit Date").minusWorkingDays(10) ### Internal readiness review 7 days before the audit date: var("Audit Date").minusDays(7) ### Remediate missing items 5 days before the audit date: var("Audit Date").minusDays(5) ### Final audit package review 2 days before the audit date: var("Audit Date").minusDays(2) ### Submit evidence to auditor On the audit date: var("Audit Date") ### Track auditor follow-up items 5 days after the audit date: var("Audit Date").plusDays(5) ## Expression syntax used in this example ### Reference the variable var("Audit Date") ### Add time var("Audit Date").plusDays(5) var("Audit Date").plusWeeks(1) ### Subtract time var("Audit Date").minusDays(7) var("Audit Date").minusWorkingDays(10) Easy Templates supports date adjustments including `plusYears()`, `minusYears()`, `plusMonths()`, `minusMonths()`, `plusWeeks()`, `minusWeeks()`, `plusDays()`, `minusDays()`, `plusWorkingDays()`, and `minusWorkingDays()`. ## Optional: calculate child tasks from the parent issue Instead of using the variable in every child issue, you can set a date on the parent issue and calculate child task dates from that field. Example: parent.fields("Due Date").minusDays(5) You can also use the short form: parent.duedate This is useful when all audit preparation tasks should depend on the main audit issue timeline. Easy Templates supports both `parent.fields("Due Date")` and `parent.duedate` references. ## Result With one **Audit Date** variable, you can generate a complete compliance or audit preparation plan with dates calculated automatically. This makes recurring audit work faster to launch, easier to maintain, and more consistent across different audit periods. --- language: "en" --- # Copy Template You can easily copy a Jira issue template to adapt it for new use cases in [Easy Templates for Jira app](https://marketplace.atlassian.com/apps/1219112/easy-templates-for-jira-issues?hosting=cloud&t). You must be a **System Administrator** or **Project Administrator** to perform these actions. ## To Copy Template 1. Go to [Manage Templates](https://help.appliger.com/easy-templates-for-jira/manage-templates) 2. Find the template in the list and click on "..." 3-dot menu ![image-20210408-062827.png](https://help.appliger.com/__attachments/a_cca752f1b91911d736c5636e54165643e0226d7c46d0486b9569ee699f767282/image-20210408-062827.png?cb=5555c38c985b512bec5484e9f52d0249) 3. Click "Copy, enter new Template's name and click "Copy" ![image-20210408-062916.png](https://help.appliger.com/__attachments/a_8fc90311ee2b1d5b31166be9c063cd19fc5c86e093b530046c02b10cdf03c9c9/image-20210408-062916.png?cb=ea00a9b8d16c5c1288d160b9adfb4e27) 4. You'll see a success message 5. Press "Edit" and you'll be navigated to a newly created Template 6. You're done! Edit your template and use it for a new Jira issue creation ๐ŸŽ‰ *** ** * ** *** For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # Create Issue from Template **Easy Issue Templates app** offers various methods for creating Jira issues through the use of templates: 1. [Use Jira native Create Issue Screen integration](https://help.appliger.com/easy-templates-for-jira/use-jira-native-create-issue-screen-integration.md) 2. [Use Easy Templates app's Screen flow](https://help.appliger.com/easy-templates-for-jira/use-easy-templates-app-s-screen-flow.md) We encourage users to adopt the new issue creation flow, which features a seamless **integration** of template selection directly within the [**Jira Create Issue screen**](https://help.appliger.com/easy-templates-for-jira/use-jira-native-create-issue-screen-integration.md). ## Getting started with creating issues from the Template 1. Make sure the [**Issue Template is created**](https://help.appliger.com/easy-templates-for-jira/creating-templates) 2. Configure **project scope** and **integration with Jira native Create issue screen** 3. **Train your team** and**start templating with ease! ๐Ÿš€** ### Read more * [Use Jira native Create Issue Screen integration](https://help.appliger.com/easy-templates-for-jira/use-jira-native-create-issue-screen-integration.md) * [Use Easy Templates app's Screen flow](https://help.appliger.com/easy-templates-for-jira/use-easy-templates-app-s-screen-flow.md) *** ** * ** *** For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) --- language: "en" --- # Create issues once a Service Desk ticket is raised **Use Case:** Create an Employee Onboarding ticket when HR requester raise a Service Desk ticket **Automation Trigger:** Issue (Work item) Created **Description:** Assume you have a Service Desk project where team members can submit HR-related tickets. The goal is to establish tasks for a new employee onboarding process in a different project. 1. **Prepare Templates:** Use the same approach as in the [general example](https://help.appliger.com/easy-templates-for-jira/automation-rest-api.md#Generate-Web-Request-URL-and-Payload). Enable **Automation** , and prepare the payload using **Payload Builder**: 1. Add (optional) [**Variables**](https://help.appliger.com/easy-templates-for-jira/variables) to consistently track the Employee-related data, like: Name, Department, StartDate. Assume that the Service Desk request form has a separate field for every requested value. 2. Choose "**Create Issues**" as the operation 3. Choose the **Project** where you want to create issues ![EmplOn_Tpl.png](/__attachments/a_819af614ae6f9476431edb657dd3363efb2156f1e268e05b1e3253978b90681e/EmplOn_Tpl.png?cb=ac569eac6844ade570175b97f3905145) 4. Repeat for every template you want to use in the Automation Rule 2. **Create Automation Rule** 1. **Trigger**: Issue (Work item) Created 2. **Action**: Send Web Request 3. Use **Web Request URL** specified in the Template's automation settings 4. **HTTP method**: POST 5. **Web Request Body**: Custom Data 6. Use **Payload** as **Custom data** copied from the Template's automation settings 7. Add [**Smart Values**](https://support.atlassian.com/cloud-automation/docs/what-are-smart-values/) to get information dynamically from the created issue custom fields 8. Save and Enable **Automation Rule**: ![EmplOn_rule.png](/__attachments/a_6d9ca12e72f4793da66ebb0a7aa93940c946def29a1c8acf9c77f4785dd46f15/EmplOn_rule.png?cb=c2e50da2568b8b181a99b26c12637dff) Code: JSON { "operation": "create-issues", "projectId": "10002", "variableValues": { "department": "{{issue.department}}", "employee name": "{{issue.employee.displayName}}", "job role": "{{issue.role}}", "manager name": "{{issue.manager.displayName}}", "start date": "{{issue.startDate}}" } } 3. Test **Automation Rule** --- language: "en" --- # Create issues when New Project created **Use Case:** Bulk templates usage. Trigger issues creation from multiple templates when a New Project is created **Automation Trigger:** Project Created 1. **Prepare Templates:** Use the same approach as in the [general example](https://help.appliger.com/easy-templates-for-jira/automation-rest-api.md#Generate-Web-Request-URL-and-Payload). Enable **Automation** , and prepare the payload using **Payload Builder**: 1. Add (optional) [**Variables**](https://help.appliger.com/easy-templates-for-jira/variables) 2. Choose "**Create Issues** " as the operation ![a new proj autom.png](/__attachments/a_7a284496a8e8819806c32b771e9546b1b56b717cff2eabf5c6f61f6be2df3bd0/a%20new%20proj%20autom.png?cb=542b48c75fa76ba69d0c6c5a5682c129) 3. Repeat for every template you want to use in the Automation Rule 2. **Create Automation Rule** 1. **Trigger**: Project Created 2. **Action**: Send Web Request 3. Use **Web Request URL** specified in the Template's automation settings 4. **HTTP method**: POST 5. **Web Request Body**: Custom Data 6. Use **Payload** as **Custom data** copied from the Template's automation settings 7. Save and Enable **Automation Rule** : ![NewProject_BulkTemplates.png](/__attachments/a_b0fd341f7918f532f453e0ddabebfe32fb41a382c1560452551472bfc25e8c92/NewProject_BulkTemplates.png?cb=813e0e9258bd6b62a2322c3893df74ba) Code: JSON { "operation": "create-issues", "projectId": "{{project.id}}" } 3. Test **Automation Rule** --- language: "en" --- # Create Template Creating a Jira Issue Template is a straightforward process with the [Easy Issue Templates for Jira](https://marketplace.atlassian.com/apps/1219112/easy-templates-for-jira-issues?hosting=cloud&tab=overview) app. This guide provides detailed instructions for Jira Cloud and Data Center users on how to save existing issues as templates, including setting the template scope and incorporating various fields. ## Instructions ### ๐Ÿ“ฉ Part 1: Saving a Template from Jira Issue 1. **Start with an Existing Issue**: * Ensure you have a Jira issue already created, as this will form the basis of your new template. 2. **Access the Save Template Feature**: * Navigate to your selected Jira issue. * Open the top right menu by clicking on the "โ€ขโ€ขโ€ข" (More) icon. * Select "Save Template" from the dropdown menu. ![Save issue as template.png](/__attachments/a_9d35f2bec6c9d3f750b6f9a9138a97ef49581d74f371acac7804dac844065472/Save%20issue%20as%20template.png?cb=837e36acdda8c4424fb3b2ebb130415f) 3. **Configure the Template**: * Set the template name in the prompted field. * Click "Create" to save the template. * This new template will include the issue's summary, description, and any subtasks (with their summaries and descriptions). ### โžก๏ธ Part 2: Creating a Template by Importing Jira Issue 1. **Find the Create Template Button**: * The "Create template" button is available in various locations including: * Manage Templates screen. * Create from template popup (zero-state). * Apply issue popup (zero-state). * Get Started page. 2. **Create the Template**: * Click "Create Template" in any of the above locations. ![image-20230714-140008.png](/__attachments/a_a3b6c9ad4caa441a1612eded81dd615c530dbfd5464d241c6413a8e926c1e134/image-20230714-140008.png?cb=acb3fff7cdb9a84f45ee70a0f47ee9ff) * Select a Jira issue as the source for your template. ![image-20230714-135940.png](/__attachments/a_b123508a450b691d4f45fd99cb5a35bce167a16b6332da215fb4353deba501c4/image-20230714-135940.png?cb=1799a5cd92e51e0ed09f805896cf385e) * Set a name for your template. * Click "Create" to finalize the new template. ๐ŸŽ‰ ![templates list. single 2.png](/__attachments/a_daf6fb70f43287a33614fea81b8a90df6b5e890e67331327d862c9e180ac7105/templates%20list.%20single%202.png?cb=1c681ff5f82cf051a5aacd1457724d16) ## Understanding Template Scope The created templates will have a broad scope, capturing essential elements of the issue. For more detailed control over which fields are included or excluded in your template, refer to the "Enabling template fields" feature in Jira. [Configure Template fields](https://help.appliger.com/easy-templates-for-jira/enabling-template-fields-cloud.md) **Check Video** ## Conclusion By following these steps, you can efficiently create Jira Issue Templates in Jira with Easy Templates app, enhancing your project management and workflow automation. These templates can save time and ensure consistency across similar tasks and issues. ## Additional Resources * **Enabling Template Fields** : [Learn how to define what template fields](https://help.appliger.com/easy-templates-for-jira/enabling-template-fields-cloud) should be used during new issue creation and what should be ignored. * **Support Material** : Check out the [instructional video on creating templates](https://www.youtube.com/watch?v=AaCNAomU2fw). By utilizing these features, you can tailor your Jira environment to better suit your project management needs, ensuring a more streamlined and efficient workflow. *** ** * ** *** For any questions or feature requests contact us via [Customer Portal](https://appliger.atlassian.net/servicedesk/customer/portal/1) [Next Page](https://help.appliger.com/llms-full.txt/1)