Luka Hummel - codefortynine Atlassian Partner

I'm not using any API key. I'm just using publicly available endpoints.

@Yassine Jebbar They changed the underlying software, and it's now a completely different API. I could get it working with https://success.vanillaforums.com/kb/articles/1842-api-v2-endpoints.

@Aditya Mani I saw the new in-app migration explainer(s). Looks good :) Huge props for implementing feedback so quickly.

Hi @Ggy, and welcome to the Atlassian community! Manually creating the same compliance tasks every month is time-consuming. You can automate this using our app Deep Clone for Jira in combination with Jira's native automation: * Create template work items: Set up a "Template" space, epic, or work item containing all the…

Hi @Ekra Hossain and welcome to the community! If your goal is to duplicate these issues rather than just copying their text, our app Deep Clone for Jira provides a robust Bulk Clone feature. You can select up to 100,000 issues from a search or a filter and clone them all at once, including comments, attachments, and…

Hi @Paulo_Cerqueira As others already mentioned, it is currently a limitation in Jira that you cannot natively include a table in the Description field. However, there are a couple ways to achieve this depending on your workflow: 1. Use Jira Automation You can create an automation flow that triggers when an issue is…

Hi @Negar Jalalian To achieve your goal of cloning a list of work items with specific labels when an Epic transitions and linking them back to that Epic, you can use Jira Automation in combination with our app Deep Clone for Jira. You can change your JQL query to only include tasks and use the Deep Clone Automation Action…

Hi @Aditya Mani I appreciate the update and your open communication in this article. My criticism of the communication is about the transparency rather than the timing (though later is definitely not the way, especially with "bigger" changes like this). It's fantastic that Atlassian uses phased rollouts. A small bug that…

Hi @Dominik Boehm If you are struggling with cloning via Jira Automations and are willing to use a Marketplace app, you can use a purpose-built app like our Deep Clone for Jira. For more advanced scenarios, you can also create a Deep Clone Preset to define via the Field Editor feature exactly which fields (like Assignee)…

@Rune Rasmussen Support confirmed that it is a phased rollout, but Atlassian should communicate the period clearly. I already got burned once by such a rollout that never happened because it was blocked by some arcane settings Atlassian was unable to fix from their end. Now I'd rather open a support ticket. Worst case, it…

@david_dousa Same here. I opened a support ticket with Atlassian because I already experienced silent failures of feature rollouts multiple times, and often they don't get fixed by Atlassian on their own. You might want to do the same.

Hi @Aditya Mani Great update! I was using Compass almost exclusively to provide additional data for linked assets. Now I'm only missing the capability to provide the Affected services or Custom Asset Fields to anonymous users in JSM. It's already available in CSM forms.

I don't know where else to report this bug, but after I linked my personal and company profile I see a different lozenge/badge just under the All Posts view. Very strange. https://www.loom.com/share/43c15ab9118d4b68afaf70db5610b421

Hi @Nina Gerke welcome to the community! I’m sorry to hear you’re having trouble implementing your use case. Unfortunately, I can’t find any tickets you’ve opened in our system. Please create a request in our support portal.

Hi @Sandeep Kumar While it is possible to build this with native automation, it can be quite complex to maintain and prone to errors like the "swapping" you mentioned. If you are willing to use third-party marketplace apps, I'd recommend using our app, Deep Clone for Jira, which was built specifically to solve this exact…

What's going to happen with Compass Components in Jira Software? It was nice to have Components synced across spaces.

Hi @Justin Goodemoot If you want to avoid using the comment workaround or the potential flakiness of Jira Automations you can give our app Deep Clone for Jira a try. Deep Clone will keep the attachment visibility when cloning between Jira Service Management spaces. Additionally, you can use Deep Clone's Post Function Clone…

Hi @Stephen Anderson While you can achieve this with a Jira Automation, if this is a recurring process for sprint spillover or reusing similar requests, consider our app Deep Clone for Jira instead of maintaining a brittle automation rule. It is designed specifically for cloning work items, including more advanced…

Hi @Biancha If you are encountering Atlassian's Cloud-to-Cloud migration feature that previous answers by @Matthias Gaiser _K15t_ and @Arkadiusz Wroblewski have suggested or is not flexible enough for your purposes I want to suggest giving our app Deep Clone for Jira a try. Acquisitions and partial Cloud-To-Cloud…

Love our small local ACE events in Karlsruhe. Great to see local community members! :)

Hi @Asier Vadillo If this cloning flow is business-critical (or you’ll be maintaining it long-term), it’s often easier to move the cloning into an app like our Deep Clone for Jira. With Deep Clone you can also use the Field Editor feature to set values of fields that are only available in project/space B.

Hi @Marigona Alimi In Jira Automation, the built-in Clone work item action will clone the parent Task, but it won’t automatically bring along the Task’s Sub-tasks (so you end up with Tasks under your new Epic, but no Sub-tasks). That’s exactly what Bill pointed out in his answer. If you want the easiest and most reliable…

Hi @Alex Cook and welcome to the community! You can get pretty close with native Set to recur + Automation smart values (and the existing answer already points you in the right direction for summary and active sprint smart values). If you want this to be reliable and low-maintenance (especially once you move to a…

Hi @Kathleen Hamilton Bill’s accepted answer already nails the “native Automation for Jira” approach: create the parent in the Business project, store {{createdIssue.key}} in a variable, then Branch rule / related items → Sub-tasks and create each sub-task with Parent set to that variable. That’s the cleanest way if you…

Hi @jrmorrison One of the other answers already covers the built-in approaches (Automation, single issue Clone + Move, CSV import). If you want something that feels closer to “duplicate my template set” and stays repeatable at scale, this is exactly what our app Deep Clone for Jira is built for. Option A (most similar to…

Hi @Manor Shaked Schlossberg Both accepted answers already cover the “pure Jira” approaches (adding people as collaborators or using Automation to create/clone an issue in your Software project). 👍 If your goal is specifically “create a Bug for R&D with the right context, without turning the whole R&D team into JSM users”,…

Hi @Saif Wahab and welcome to the community That behavior is expected: Jira Automation rules run as the “Automation for Jira” actor, so if you don’t explicitly override it, the newly created issue ends up with that user as Reporter. If you want to avoid JSON and make this more robust at scale: Our Marketplace app Deep…

Hi @WarUniverse and welcome to the community! It looks like you are using our app Quick Filters for Jira Dashboards. If you are still encountering issues please contact our support.

Hi @Qusai Alattas and welcome to the community! Yes, it’s possible to migrate just a single Jira project with Atlassian’s Data transfer (a.k.a. “Copy product data”), as long as you’re an organization admin for both the source and the destination. Where this gets tricky in practice is usually one of these: * You’re not org…

Hi @shyam sunder rn If you need a reliable way to create many Stories with the correct parent-child issue link direction (without wrestling CSV link direction), one practical alternative is to switch from “import” to a template + clone approach. With our app Deep Clone for Jira, you can create one (or a small set of)…