Olga Cheban _TitanApps_ Atlassian Partner

hi @Alexis Therier ! If you are open to trying out marketplace solutions, I can recommend the Scheduler available in our app, Smart Templates for Jira. It works well for standard or recurring tasks. It lets you save any set of work items as a reusable template and then generate new work items from that template on a…

hi @John Izquierdo ! It, indeed, looks like using checklists would be a better solution here. However, I wouldn't go with the Checkbox field for this, as it's not exactly well-suited for this purpose, for many reasons. If you are open to trying third-party tools, I would recommend our solution, Smart Checklist for Jira. It…

hi @Genevieve Riffe ! Indeed, Jira's native hierarchy can feel a bit inflexible. as it was already mentioned, you can only change the default hierarchy with Jira Plans (you will need to have Jira Premium or Enterprise to access this feature). then, you will be able to add other hierarchy levels above Epics, such as…

hi @Riyas Khareem ! I see you already found a workaround for your issue, even if not a perfect one. As an additional tool for viewing complex work hierarchies, I can recommend our solution, Smart Hierarchy for Jira. It shows you all your work items in a compact view with a progress bar and details for each task. Currently,…

hi @Ward Schwillens_ Schwillie ! Short answer: Jira Cloud does not have native templates for full epic → task → sub-task hierarchies or for stand-alone work items either, for that matter. So your current options are: 1) Cloning a “model” epic when you need the same structure again 2) Using Automation for Jira to create a…

Hi @Dan Allenby ! There's also a more straightforward way to achieve this. You can save your standard set of onboarding tasks as a reusable template - and then set up one Jira Automation rule that will create a full set of tasks from that template. (You will need to create separate rules for separate templates, though).…

hi @Rajesh Vaidya ! To change the default hierarchy, you need to have a Jira Premium or Enterprise plan. In this case, you will have access to Jira Plans, where you can add custom levels and build the hierarchy that you want. However, you still won't be able to add Feature below Epic as additional hierarchy levels can only…

hi @Jerome Soucy ! Unfortunately, Jira doesn't allow you to insert custom levels between the default hierarchy levels (Epic (1) -> Task/Story/Bug (0) -> Subtask (-1)). However, you can add custom levels above Epic if you have access to Jira Plans (you do if you have a Premium or Enterprise plan). So maybe you can achieve…

hi @Nicola Miori ! To include a new work type into your Jira hierarchy, you need to complete three steps: Create custom work item types (in your case, it's Master Epic) Add them to the schemes Assign them to the corresponding hierarchy levels. Only after this, your custom work type will function as a new hierarchy level…

hi @Pratik Acharya ! In our organization, we use our own solution, which is available on the Atlassian Marketplace - Smart Productivity & Team Activity Dashboard. This dashboard gathers data from Jira, Confluence, and GitHub, and visualizes it in a single view. It enables you to track key productivity metrics, including…

hi @Nancy Stankovich ! As it was mentioned in earlier replies, Jira doesn’t support creating work items under subtasks. So, unfortunately, you can’t add a bug directly beneath a subtask, even if you use Jira Plans and set up a custom hierarchy. But there’s a practical workaround that can be helpful in your case: using…

hi @keerthi_guntupalli ! It's understandable that your team needs traceability without cluttering Jira with dozens of granular subtasks. However, you are right, Jira doesn't allow you to add custom work types below subtasks, so this can't be done natively. Here's a workaround I can suggest. While you can’t add "official"…

hi @Jan L ! Welcome to the community! Unfortunately, Jira doesn't allow you to insert custom levels between the default hierarchy levels (Epic (1) -> Task/Story/Bug (0) -> Subtask (-1)). It also doesn't allow you to add any custom levels below level -1. So, basically, in Jira Plans, you can only add new levels above Epic.…

Hi @Timothy McKay ! In my organization, we manage onboarding in Jira with checklists. We create them with the help of our solution, Smart Checklist for Jira. It allows you to list all the onboarding steps, group them with headers, and tag responsible people. Here's an example - an onboarding ticket for the new employee. It…

hi @Maarten Verreck ! I see you already got the answer to your question, but I'd like to add that there is a simpler and more straightforward way to create a set of parent tasks + subtasks in another backlog / project. If you are open to trying out third-party apps, I can recommend our solution, Smart Templates for Jira.…

hi @Deepali Dabholkar ! Creating a Jira roadmap is not difficult, but it's true that one needs some guidance when doing this for the first time. The process involves 3 main steps: 1) First, create custom work types matching your custom levels 2) Then, add the new work types to your work scheme 3) And finally, assign your…

hi @Bernhard ! I'm not sure how exactly you manage your acceptance criteria checklists (with Jira action items in the task description or with a specialized app). But I can recommend a solution - you can filter out work items where you are assigned to checklists, but are not a work item assignee. This can be done with the…

Hi @arti_b_patil ! It's not possible to move a Task under a Story in the hierarchy. However, you can eliminate Task and add Checklists to your Subtasks. As a result, your custom hierarchy will look like this: Level 1 - Epics |-- Level 0 - Stories |-- Level -1 - Subtasks |-- Level -2 - Checklist items In this case, Subtasks…

Hi, @Timo Greimel ! As Valerie already noted, unfortunately, changing the basic hierarchy like that is not possible. So the only way to address this is to find a workaround that would help you accomplish what you are looking for. A workaround I can suggest is adding checklists inside subtasks - in this case, checklist…

hi @Nicolas Shinozaki ! I would say that creating an actual Epic template would be a simpler and more reliable solution than setting up two automation rules or cloning. Jira doesn't allow you to create work item templates natively, but you can do so with our solution, Smart Templates for Jira. You can create an epic with…

Hello @Hermundur Sigurðsson ! If you mean the "To Do" column on the Jira board, then this is a natively available feature. If you refer to a checklist, Jira has action items that you can use inside a work item, but they have very basic functionality. I can also recommend our solution, Smart Checklist for Jira. It allows…

Hi @Kathy Dickason ! I can recommend our solution, Smart Templates for Jira. It works both with Jira Data Center and Jira Cloud. It enables you to save any work item hierarchy as a reusable template. Then, you can generate a complete hierarchy of identical work items from this template. The details of each work item in the…

Hi @Kathy Dickason ! For Jira Data Center, I can recommend our solution, Smart Templates for Jira (it works with Jira Cloud as well). The app allows you to save any work item hierarchy as a template and then generate work items from this template. Issue creation can be triggered manually or occur fully automatically on a…

Hi @Kevin Sweeney! In my team, we use checklists to track progress on multiple-step tasks. Different stages can be organized with headers. In this example, it's "1st week" and "1st month" -> in your case, this would be headers + checklists for "Requirements", "Development", and "Testing": This checklist was created with…

hi @Dirk Ronsmans ! thank you for your comment! Playbooks only seem to work with Jira Service Management. and I would say they make most sense if you want to experiment with their automation features. as for using them as a type of checklist - I would say they are similar, but, still, what you get isn't exactly a checklist…

hi @Roeland Grutterink ! if you want to group subtasks under certain phases, I would recommend a slightly different approach to work item hierarchy. You can set up a main task (customer onboarding), add one subtask for each onboarding phase, and add a checklist with the actual steps for each phase to every subtask. The…

Hi, @Haile, Eskinder ! as you already see from Trudy's answer, the native functionality has some limitations. maybe third-party tools can offer you a more convenient way to view your Jira issues. If you’d like to check the hierarchy of tasks outside the timeline view, I can recommend our free app - Smart Hierarchy. With…

hi @Calvin ! If you also need to view issue hierarchy in other contexts, apart from the timeline, I can recommend a free app, Smart Hierarchy (my team works on it). It shows you the full parent–child hierarchy directly inside an issue. In your case, it will be everything you have above Epic, plus the standard Epic -> Task…

hi @Julia Cox ! I agree with Walter, from your screenshot it's clear you are using an add-on. I'm quite certain Jira doesn't have such checklists out of the box. if you are having issues with that checklist add-on, I can recommend you another app, Smart Checklist (my team works on it). It allows you to set custom statuses,…

hi @Nicolae Victor Rusu ! By default, the top level of the work hierarchy is Epic. However, you can set up a custom work structure, such as your Business Outcomes > OKRs > Initiatives > Epics. This can be done via Jira Plans - functionality that is only available to Jira Premium and Enterprise users. So, if you have a…