Luka Hummel - codefortynine Atlassian Partner

Hi @Lynda Kho If you are willing to try a third-party tool, our app Deep Clone for Jira can help you in cloning issues with their custom fields. You can also trigger a Deep Clone in a Jira automation with a looping transition.

Understandable. If you still want to give the app a try, you can test the Deep Clone for 30 days, and the app is free for Jira instances with up to 10 users.

Hi @AJ Gilbert and a late welcome to the community! I just want to add that our Quick Filters for Jira Dashboards app also has our own version of the Filter Counts gadget as Quick Filter Counts. I know, not very creative, but we try to provide our customers with the known features of the Atlassian gadgets but with our own…

Hi @Mariam Omran I'm Luka from codefortynine and I think our Deep Clone for Jira app can help you clone your issues from company-managed projects to team-managed projects and back from team-managed projects to company-managed projects. With our Epic/Tree Clone feature, you can easily clone whole issue hierarchies…

Hi @Abhishek Sharma I think our Quick Filters for Jira Dashboards marketplace app can help you in achieving your goal. You can use our Quick Controller gadget to filter your wanted time periods with endOfDay(-3M) and endOfDay(-6M). This way, you have two buttons you can use to quickly change the time period of the data…

Hi @Natasha Felski The Jira CSV export/import function can be quite limited. Our Deep Clone for Jira marketplace app can clone issues from one Jira instance to another instance with its Instance Clone feature.

Hi @Hiti Verma If you are still looking for a solution, our app Dynamic Custom Fields for Jira can probably help you display that information on a dashboard. With the app, you can create custom fields that get automatically filled based on a Jira expression. To have the number of selected options calculated, you first need…

Hi @Samuel Smiles P I think our app Dynamic Custom Fields for Jira would be perfect for your use case. The app allows you to create custom fields that have their values automatically calculated based on a Jira expression you provide. I have quickly thought of an expression that would display the percentage of all completed…

Hi Casper, I'm Luka from codefortynine and I think your use case is an interesting use case for our app Dynamic Custom Fields for Jira. If you want to avoid the limitations of Jira Automations, you could try to add this Jira expression as a Dynamic Custom Field (You need to replace the custom field ID with the…

Hi @Jagdeep Singh and welcome to the community! While Jira does provide native options to move issues between projects, you might find the process more streamlined and efficient by using our Deep Clone for Jira marketplace app. Here's a brief guide on how you can accomplish this: * Using Jira's Native Functionality: a. Go…

Hi @Christina Holmes and welcome to the community! Our app Deep Clone for Jira can help you clone your templates and also make the necessary tweaks for your different clients. You can create your template as a project or just an issue hierarchy (Initiative ⇒ Epic ⇒ Task/Story ⇒ Subtask) and then clone them with Deep…

Hi @Elena-Alexandra Enache If you are willing to use a third-party app, our Deep Clone for Jira can clone whole issue hierarchies. With it, you can create your template hierarchy once and clone it often as you want. My colleague @Marlene Kegel - codefortynine even wrote an excellent community article about that use case.…

Hi @Heba Rezk I'm Luka from codefortynine and escalating support requests is actually a really common use case for our Deep Clone for Jira app. My colleague @Marlene Kegel - codefortynine even wrote an excellent community article on the use case. To quickly escalate an issue, you can create a preset and link that issue to…

Hi @Elango Thiruvengadam If you are willing to use a third-party app, our Deep Clone for Jira can help you in migrating from one Jira Cloud instance to another Jira Cloud instance. You can't clone the whole project with our app, but you can clone all issues between instances. You will need to install and configure Deep…

Hi @Jeri Simpson If you are willing to use a third-party app, you can try our Deep Clone for Jira app. Deep Clone can clone whole template issue hierarchies or even template projects while keeping all the relations between different issues in the clone (and if needed to projects not being cloned) intact. My…

Hi @Michael Horsley and a late welcome to the community! I'm Luka from codefortynine and if you are still trying to migrate issues between a sandbox instance and the production instance and are willing to consider a third-party app our Deep Clone for Jira can clone between Jira Cloud instances including a sandbox instance…

Glad you found the problem. When Deep Clone for Jira clones between team-managed and company-managed projects, it tries to match values like issue type and custom fields by their name. This only works correctly if the names are identical.

Hi @Jason Abofsky and welcome to the Community! I'm Luka from codefortynine and if you are willing to use a third-party app, our Deep Clone for Jira can help you clone your template. It can clone whole issue hierarchies/trees, including subtasks. * Navigate to the issue you want to clone * Click Action menu ••• > Deep…

On my first trip to the US as a kid, we went to Sea World Orlando. That was quite amazing. Although all the animals were great, as a rollercoaster enthusiast I still remember the Kraken being the only rollercoaster ever giving me a bit of an upset stomach. 😆

Hi @Bahia Mezraoui I will try to give a basic overview of the steps. These are of course more complicated if you need additional field values copied or need to create more issue links. * Clone Epic * FOR EACH Most recently newly created issue (Epic): Create issues and add parent field with Advanced fields under More…

Hi @Bahia Mezraoui and welcome to the community! While you can automate this, the set-up is quite tedious and the automation rule can break quickly if there are any changes. If you are willing to use a third-party app, our Deep Clone for Jira can quickly clone whole issue hierarchies (Initiatives → Epics → Tasks/Stories →…

Hi @Paty Souza Although you can achieve your goal with Jira Automations, but if you are willing to use a third-party app, our Deep Clone for Jira can make it a lot easier. With our Epic/Tree Clone feature, you can clone whole issue hierarchies (Initiatives → Epics → Tasks/Stories → Subtasks). The process would look like…

Hi @Patrick Haley If you are willing to use a third-party app, our Deep Clone for Jira can make escalating your issues easier. It will also clone the request type as long as it's available in the target project. My colleague @Marlene Kegel - codefortynine even wrote an article about using Deep Clone to escalate issues from…

Hi, I'm Luka from codefortynine 👋 While it is possible to clone hierarchies with Jira Automation, this can be quite finicky and can break easily if project or issue configurations change. If you are open to use a third-party app, our Deep Clone for Jira can clone whole issue hierarchies, including Initiatives, Epics,…

Hi @Michelle Herschell If you are willing to use a third-party app, our Deep Clone for Jira is able to clone whole hierarchies including Initiatives, Epics, Task, and Subtasks. The app is highly configurable, and you can even set your field values dynamically while cloning with Clone and Edit.

Hi @Rachel Hafley If you are willing to use a third-party app, our Deep Clone for Jira can make it really easy for you to clone your issues from the Jira Service Management to your internal project. The app will also clone your comments, which might be useful for Jira Service Management issues.

Hi @Velkuri Balaji Like @Trudy P Claspill already mentioned, there are also third-party apps on the marketplace that can help you with more complex clones. With our app Deep Clone for Jira, you can use Clone and Edit to clear your "Epic Type" custom field when cloning.

Hi @Roger Mcgregor As @Nic Brough -Adaptavist- has rightly pointed out, deleting issues is a rather bad practice in Jira. I would suggest to clone and close the original issue. If you are struggling with creating a clone automation, you also can use our app Deep Clone for Jira to clone the issues via Jira Automation or…

Hi @Steve Laham If you are still trying to clone your project to another instance and are willing to use a third-party app, our Deep Clone for Jira can clone issues from one instance to another instance. To enable this feature, you need to configure Deep Clone on both of your instances as described here. * Ensure you have…