Dorota Popowska - Vilisoft Atlassian Partner

Hi @mith sams, Have you considered trying a dedicated cloning app, such as Clone Expert for Jira? Depending on how your recurring tasks are organized, you have a couple of options: Epic cloning: If your tasks are grouped under an Epic, you can clone the entire Epic together with its child work items. Bulk Clone: If your…

Hi @Charli Parker, The others have already covered the solutions available natively in Jira, so let me suggest an alternative using an Atlassian Marketplace app. Depending on your needs, you can choose either Clone Expert for Jira and Advanced Template Cloner for Jira. With either app, you can create a bookmark that takes…

Hi Olivia, I’d be happy to share how we manage recurring operational work in Jira. We maintain a library of reusable templates, but we try to keep the setup as close to native Jira as possible. Most of our templates use standard Jira structures, mainly Epics and child work items, to group all tasks related to one recurring…

Hi Paulo, Jira's native Clone feature copies the entire content of the Description field, including tables. This means you can use an existing work item with a predefined table as a template for creating new ones. I think the key here is to verify how issue templates are handled in your Jira instance, specifically whether…

Hi @Mark Revely, Another option is Clone Expert for Jira with its Scheduler feature. You can use each maintenance ticket as a template and schedule it to be cloned automatically according to its own recurrence, date, time, and time zone. The scheduler also lets you define an end condition and customize what should be…

Hi @Shivani Saran If you prefer to handle this with an app, you can use either Clone Expert for Jira or Advanced Template Cloner for Jira to clone a single work item to another project and link the clone with the original. Both apps let you select the destination project and enable “Create a link between cloned work…

Hi @Andy Wan Alternatively, to clone a Story together with its linked Stories, you can use Advanced Template Cloner for Jira. It does exactly what you need: creates a new independent structure while preserving the relationships between the newly created work items. Before cloning, you can review and adjust the content in…

Hi @King_ Lee As others mentioned, Jira does not currently provide bulk cloning as a standard bulk operation. I recommend the Marketplace app Clone Expert for Jira, which includes a Bulk Clone feature. Before creating the clones, you can preview the selected work items, adjust their fields individually or in bulk, choose…

Hi @Ggy Without knowing the exact structure of your company teams and Jira setup, I cannot recommend a precise Jira configuration based only on the information in your post. However, let me share a general concept that you could adapt to your needs. Let’s assume you have one group of compliance activities that must be…

Hi @Negar Jalalian , Before switching to CSV import, you may want to try Clone Expert for Jira. It allows you to clone an Epic together with its tasks and subtasks while preserving the hierarchy. This means that cloned subtasks are created under the corresponding cloned task, rather than remaining linked to the original…

Planting trees? I’m in! 🌳 I love trees and already have quite a few of them around me, although apparently there is always room for much more. Jira appeared right at the beginning of my professional life, and Atlassian products have been with me ever since. At this point, it is less of a journey and more of a long-term…

Hi @Kathryn Lee Let me share my approach to managing work item templates in Jira that would be close to your current approach. I would recommend creating a small template library and applying a few simple rules: * Add a clear prefix to each template’s Summary, for example: * [TEMPLATE] Weekly report A * [TEMPLATE] Weekly…

Hi Stefán, You may have already found a solution, but if not, you could also try Clone Expert for Jira. You can create a reusable master Epic with its tasks and subtasks, and then clone the entire structure whenever you need to start a similar project or process. Before creating the cloned work items, you can preview the…

Hi @Kristy I would also recommend keeping the deliverables in an agreed-upon company repository, such as SharePoint, OneDrive, Google Drive, or another document management system, and using Jira mainly to reference them. The team should define: * one authoritative location, or a clearly defined set of locations, for…

Hi @mkurdi If you're looking for more control over what gets cloned, you might want to try Clone Expert for Jira. During cloning, you can choose exactly what should be copied, including whether attachments should be included or not. This makes it easy to adjust the cloning behavior to your specific use case. In addition,…

Hi @Kristy , Have you had a chance to look at Clone Expert for Jira? Based on your description, it seems to match what you’re trying to achieve when cloning work items from one project to another. Clone Expert preserves the full hierarchy, so the cloned work items remain linked to each other rather than to the original…

Hi @James Bond and @Olga Cheban _TitanApps_ That’s a great point about using structured checklists inside tickets 👍 To build on that, once you have a well-defined incident structure (like an epic with tasks and checklists), cloning can be a very effective way to reuse it across multiple incidents or teams. With tools like…

Bonjour @Judicael Kabore (Version française – traduction automatique) Le clonage n’est pas forcément une mauvaise approche, à condition que le contenu puisse être modifié facilement et de manière transparente avant la création du clone, comme dans Clone Expert. Dans la fenêtre de clonage, vous pouvez visualiser et modifier…

Hi @Ahmet Fatih Ayyıldız If you want to avoid writing JQL filters each time, I’d suggest looking at Clone Expert for Jira. It lets you clone a template Epic with its hierarchy and then decide in the preview which child items or subtasks should actually be included in the clone. It gives you a much more user-friendly way to…

Hi @Kyra Mayock If I understand your case correctly, you need to clone a hierarchy of work items starting from different levels, either above Epic level, such as Project / Initiative, or from the Phase at the Epic level. For this setup, I’d recommend using a dedicated cloning app, such as Clone Expert for Jira. It supports…

Hi @jrmorrison Since you expect to reuse the same set of ~30 work items many times, I’d strongly consider using a dedicated cloning app instead of CSV. In Clone Expert, you can keep those work items in Jira as a reusable template structure and bulk clone them into a new project/space whenever needed. A key advantage is the…

@Wurm Peter Try on team-managed space. It seems not to work on company-managed. Or try a bit later - maybe your instance is not yet updated, as it seems to be a very fresh feature. I have the same - currently, I can't see this hierarchy on company-managed spaces.

@Yatish Madhav In Jira, business spaces are spaces created for non-IT teams (marketing, HR, finance, ops, etc.). Think “work management” use cases rather than software/IT service projects. Impact: you can group multiple tasks under one parent work item. Example (Campaign template): Campaign: Marketing campaign for…

@Dirk Ronsmans I did the test on my instance, and I can see the mentioned hierarchies only in team-managed spaces/projects. In company-managed, I have the hierarchy as before.

Do you plan to introduce it for company-managed spaces as well?

Hi @Jiregna Tesfaye Ayana Jira was created by Atlassian (Mike Cannon-Brookes & Scott Farquhar) and first released in 2002. Quick history overview here.

@Rich Scire - the link is active now, you can read the article without any issue.

Update: @Rohit Utukuri - the link is active now, and the article is available for readers. Hi @Rohit Utukuri The article has been published, but got an "In moderation" status. I hope the Community admin will unblock it quickly.

Hi @Dan Allenby This is a great use case, and it’s actually very similar to the scenario described in this Community article about building reusable task structures with Jira’s native features: https://community.atlassian.com/forums/App-Central-articles/Why-repetitive-work-deserves-better-than-manual-effort/ba/p/3145891 .…

Hi @Ward Schwillens_ Schwillie For this kind of repeatable Epic → Task → Sub-task structure, the approach I usually recommend is creating templates using Jira’s native functionality, exactly as described in this Community article:…