Olivier_OSTConsulting Atlassian Partner

Hi @Olivia Carter For service operations the structure usually comes down to how different the workflows and SLAs really are. If field scheduling, maintenance, and customer follow-ups each need their own statuses, request types, or permissions, separate projects keep them clean and let you report per team. If they mostly…

Hi @Negar Jalalian, "No actions performed" in the audit log almost always means the JQL branch matched zero work items, not that the clone step failed. Two things to check first: * Rule scope. If your rule is single-project and the label = template items live in a different project, the branch silently finds nothing. Open…

Hi Sandeep, Just to add a heads-up on some limitations, even once the parent linking is sorted. Jira's Clone work item action only copies a subset of the source by design. Things that don't carry over, no matter how well the rule is configured:* Hierarchy with attachments * Comments (internal and external) * Outbound issue…

Great overview, Olga, particularly the honest call-out that native + Automation for Jira can't fully replicate an epic's deeper hierarchy or handle bulk cloning cleanly. A few additions readers landing here in 2026 might find useful: * Comments on clones (to Trevor's point above): native cloning still doesn't carry…

Hi Murat, May I ask you to confirm if you are referring to our app Easy Clone? If yes, please open a ticket on our helpdesk and include the following details: * Your Jira instance URL ("https://<instance>.atlassian.net") * The project (space) and work items ID involved in the cloning process. We’ll be happy to troubleshoot…

Hi @Vikrant Yadav When cloning issues via Jira Automation, Jira requires values for all mandatory fields defined on the Create Screen of the target project. If any required field is left empty, the automation will fail because Jira blocks the creation until mandatory fields are filled. With native Jira features, there…

Hi @AS, You can achieve this with a Jira Automation Rule. Here’s one way: Go to Project Settings → Automation and create a new rule. Add a Trigger: Issue Created. Add a Condition: check if the Summary contains "(clone)". Add an Action → Edit issue: in the Summary field, use the smart value function to remove the unwanted…

Hi Natalia, As far as I know, there isn't a native way to pre-populate the Create Screen with a default description value. However, this is a very common use case some apps on the Marketplace are addressing in a way or another. I would suggest you to have a look there, as some apps are adding the template capabilities…

Hi @Digvijay Singh Gehlot If you're open to using Atlassian Marketplace apps, I’d recommend checking out our app Easy Clone for Jira Cloud. It's specifically designed to help with cloning issue hierarchies like the one you described (Portfolio Epic > Feature > Task > Subtask) and can save time by replicating entire…

Hi Ian, You can use Automation to apply changes to your work items on-the-fly on events such as Work Item Creation: Alternatively, you can use 3rd-party apps from Atlassian Marketplace that are providing templating capabilities to Jira. We are the ones behind Issue Templates for Jira Cloud. Hope that helps! Olivier

Hi @Qasim Qureshi As @Walter Buggenhout mentioned earlier, there are apps specifically designed to meet your needs. I'm sure you'll find one that matches exactly what you're looking for. I’d suggest taking a look at ours: Issue Templates for Jira Cloud.

Hi @Prolaborate, Yes it does apply to your app. The quota is calculated from various metrics, including global API usage (cross tenants) and per-tenant basis. There are new HTTP headers implemented in the API responses that will tell you where you are in your current usage. Hope this helps, Olivier