Olga Cheban _TitanApps_ Atlassian Partner

Hi, @f_tramnitzke ! I can recommend another option to solve this. In our team, we use our solution Smart Templates for Jira to handle recurring work items. The idea is simple: you create a template from any work item(s) - with all the fields, descriptions, and child tasks you need - and then set up a schedule for it. The…

Bonjour @Judicael Kabore ! C'est une très bonne question. Nativement, Jira ne propose pas vraiment de fonctionnalité de modèle pour les User Stories ou tout autre type de work item. Cependant, c'est possible avec une application du Marketplace. Je peux vous recommander notre solution, Smart Templates for Jira. Elle vous…

hi @Ben Scott @Michelle Albanese ! There's another approach worth considering for acceptance criteria. Instead of a custom text field, you can use a checklist - it turns your acceptance criteria into a trackable, structured list right inside the work item. With our solution, Smart Checklist for Jira, you can list each…

hi @bala katabathuni The other answers cover the Premium approach well, so I'll share a practical workaround that works on any Jira plan. Instead of trying to insert a level between Epic and Story, you can gain an extra level by shifting everything down: * Create a "Feature" work type at the same level as Story/Task/Bug. *…

hi @Holly Scott ! Adding a Feature level between Epics and Stories is one of the most common requests in Jira - and unfortunately, it's not straightforward. Even on Premium, you can only add levels above Epic, not below. That said, there's a practical workaround that gives you the extra level you need. Here's the idea: *…

hi @sathish moorthy ! Honestly, limited hierarchy visualization was one of our frustrations too. You open a work item in Jira, and you can see its direct parent and children - but that's it. There's no way to see the full picture in one place. Where does this task sit in the bigger initiative? What's happening with the…

Hi @Abilash ! Yes, it's absolutely possible to run vendor security risk assessments in Jira. Here's how you can set it up. The idea is to create a structured assessment process where each vendor gets a dedicated Jira work item with a checklist of security criteria to evaluate. This keeps everything in one place and makes…

Hi @Jordan Collins ! We recently went through a DC-to-Cloud migration ourselves for Smart Checklist (our own solution for Jira), and we documented the whole experience in a case study. There are the real challenges we hit, how we solved them, and a reusable migration playbook. Might be worth a read as a hands-on complement…

hi @Kush Sharma ! Overall, Jira doesn't allow you to insert additional hierarchy levels below Epic. With Jira Plans (Premium subscription required), you can add custom levels above Epic, but not below. So your options are workarounds with renaming work types. One option is what Marc described: to rename the Epic to Feature…

@Eduardo Garcia Posadas hi! I'm not sure if I understand your grouping logic correctly, but I would suggest trying our solution, Smart Hierarchy for Jira. It shows your complete work hierarchy in a nested view along with progress details. It works with custom hierarchies as well. Here's what it looks like: I hope this…

hi @Si Scott ! Indeed, that's not the most exciting task to do manually. This can be handled with Jira work item templates - save once, reuse multiple times. Jira doesn't offer such a feature natively, but there are third-party apps that can do the trick. I can recommend our solution Smart Templates for Jira. Here's how…

hi @rworkman ! I would suggest using checklists instead of subtasks. This will make things much simpler and not so cumbersome. Here's what this can look like for your specific flow: I made this checklist with our solution Smart Checklist for Jira. As you can see, it allows you to tag responsible people, add deadlines, and…

hi @Yasmina Rodriguez ! If you're open to exploring a third-party solution, there's an alternative way to handle this. It allows you to avoid the complexity of automation altogether. Here's what you could do: 1) Replace subtasks with a checklist. Each subtask you now have will essentially become a checklist item inside the…

hi @Starman ! In Jira, adding child work items to subtasks is not possible. However, I can suggest a workaround. You can use checklists to add one more hierarchy level below the subtask. As a result, your hierarchy will look like this: Epic (1) -> Story / Task / Bug (0) -> Subtask (-1) -> Checklist items (-2) Here's an…

hi @Joan.collantes.ext ! Jira Plans (formerly Advanced Roadmaps) are only available to users with a Jira Premium or Enterprise plan. A trial for those tiers will work too. Visit the Jira Pricing page and click "Start Free Trial" for Jira Premium (not Standard). Once active, you should be able to create a custom hierarchy.…

hi @Md_ Abrarul Huda ! I can suggest another workaround if you are open to trying out third-party tools. Here's what you could do: 1) Use a checklist instead of subtasks. In this setup, what was a subtask becomes a checklist item. You can use our solution Smart Checklist for Jira - it allows you to tag responsible people,…

hi @Shubha Khamparia ! You can apply a checklist template in bulk in different ways, depending on what exactly you need to do. Could you please share more details about your use case? * If you want to apply a checklist template to new stories that meet certain criteria, you can do this with our solution Smart Checklist for…

hi @Carlin Scott ! I see you've already found an elegant workaround for this issue, but I still wanted to add a couple of things. Native checkboxes work well when you are taking notes during the meeting, but they are not very helpful for organizing processes step-by-step. They have many limitations. To name just a few -…

hi @jrmorrison ! As you need 30 templates that should be copied 50 times, I would recommend using a dedicated issue template management app + Automation for Jira. Here's how it can work. 1) Save your 30 "model" work items as templates with a third-party app. You can use our solution, Smart Templates for Jira. It allows you…

Hi @Timi Falusi ! I would recommend solving this with the help of templates rather than Jira automation rules. Although Jira doesn't allow you to create issue templates with a pre-set description and other details, this can be done with third-party tools, such as our solution Smart Templates for Jira. It enables you to…

Hi @Soumitra Dutta ! Welcome to the community! Automation in Jira is a broad topic, and there are many tips and best practices that can make your work more efficient. I cover the most useful of them in my new article Top 10+ Most Common Use Cases For Jira Automation in 2026. I recommend taking a look - it will give you a…

hi @Ben Arundel ! I'm glad to see your issue is already resolved! From my side, I can recommend our solution that allows you to view Jira hierarchies of any complexity in a nested list - Smart Hierarchy for Jira. It helps you to see everything at a glance and easily track progress. Here's what it looks like: I hope this…

hi @Marigona Alimi ! As the others noted, Jira's native cloning option only works with the 1-level-of-hierarachy depth (Epic + Task/Story/Bug, but not subtasks). To do this with Jira automation rules, you will need two separate rules: for the parent tasks and for subtasks. This setup of two automations doesn't always work…

hi @Diego Arturo Bustos Aponte ! If you are open to using third-party tools, I can recommend an alternative option. If each Story must contain Acceptance Criteria, you can approach this a bit differently. Instead of verifying if a Story includes a subtask, you can organize your Acceptance Criteria as a checklist and…

hi, @Alex Cook ! I looked into your requirements, and I think I can suggest a viable option. Although it's not a 100% fit, but maybe this information will be useful to you. I would say the most straightforward way to handle this case would be the following: 1) Use a dedicated app to create Jira issue templates, such as our…

hi @Sonika Chitral ! Welcome to the community! This is a Jira limitation rather than a configuration issue. By default, Jira’s standard hierarchy is Epic → Standard issue (Story / Task / Bug) → Sub-task. This hierarchy can be partially customized if you’re using Jira Premium or Enterprise with Jira Plans (Advanced…

@Kenny Chan as the others already answered, this type of hierarchy in Jira is not possible. Even if you have a Jira Premium or Enterprise plan with access to a custom hierarchy, it's still not possible to insert new hierarchy levels below Epic. However, I can suggest a workaround. You can use checklists to add one more…

hi @Olga Mello ! This cannot be done natively, but I can recommend a good data integration solution, Coupler.io. It can Export data from Jira (among other sources) and load it to spreadsheet apps, data warehouses, or BI tools. You can select data types to export, set filters and sorting, etc., so that you only export what…

hi @Brijesh Jain ! As Trudy mentioned, you can set up any work types above Epic with Jira Plans, and it's also possible to have multiple custom work types at the same level. If you need additional information on this process, you can take a look at my article Advanced Roadmaps Hierarchy Configuration Guide 2026. It…

hi @Okey Onyeokoro ! As the others mentioned earlier, JQL is used for search/filtering rather than ticket creation. However, there are other ways to automate the creation of offboarding tickets. If you are open to using third-party tools, I can recommend our solution, Smart Templates for Jira. It allows you to create a…