Rolf Eriksen -Eriksen Labs- Atlassian Partner

Thanks Mertcan, good addition. I've added it to option 5 and credited you. It's the best fit when every work item of a type needs the same sub-tasks, and as you say, there's no template epic to go stale. Two things to watch with it: the rule runs on every work item of that type, so one that doesn't need the sub-tasks still…

Hi Charli, one correction to the Create-link idea that may get you all the way: on Cloud the old link takes more than the space and work type. I tried it today on a Cloud site (replace "YOURSITE" with your site)…

Hi Stefán, a native path that is not in this thread yet, for you or the next reader: Jira Cloud's own Clone can take the children along now. Keep one "template" epic with its tasks and sub-tasks, open it, choose ••• > Clone, and tick Child work items under Include (the option is there on a Cloud epic as of this week; I…

Hi Eric, Trudy's two-rule split is the reliable way to do this. In detail: Rule 1: trigger Field value changed (Project Type). Conditions: work type = Feature and Project Type = PDCA. Add Lookup work items with JQL parent = {{issue.key}}, then the condition {{lookupIssues.size}} equals 0. Then add four Create work item…

Hi Malee, two things tend to keep an onboarding setup manageable as it grows. Let one form branch instead of getting longer. JSM forms can show a section only when an earlier answer matches. The trigger must be a radio, checkbox or dropdown field, not a multi-select. The requester then sees only the questions for the role,…

Hi Andreas, to your follow-up: the native "templating" depends on the space type. Team-managed: each work type can have default Description text, which shows in the Create dialog (Space settings > Work types). Company-managed: the system Description has no default. Atlassian's workaround is a paragraph custom field with a…

Hi Kathryn, one native detail for the weekly and monthly report stories that hasn't come up yet is Set to recur. Open the current weekly-report story, select Automation (lightning icon) or the Due date field, choose Set to recur and set the schedule. Atlassian's documentation says the next copy keeps most fields and…

Hi Ggy, here is a native setup for recurring statutory work that needs no extra apps: One business space for compliance, with a work type per obligation (for example Annual return or Tax filing) and a due date on each. For each client and obligation, one epic holding the steps as child work items: gather documents,…

Hi Catarina, a native option that avoids the variable juggling altogether is Jira's own Set to recur. On the template task, select Automation (the lightning icon) or the Due date field, choose Set to recur and set the schedule. Atlassian's documentation says the recurring copy carries over child work items, so the…

Hi Jaspreet, one addition for the "standard format" side of your question. If you want every new story to start with the same outline (the story statement, acceptance criteria and definition of done), Jira can do it natively. How depends on your space type: Team-managed space: set default text for the Description field on…

One I’d really like to see addressed is the reliability of Confluence PDF export when Marketplace/Forge macros are involved. I’ve been digging pretty far into this recently while working on a Forge app, and managed to reproduce a case where PDF export consistently times out after roughly 4 minutes depending on how the…

Hi Keith, I’ve been working quite a bit with Jira’s new Create experience lately from the Forge side, and the bit that stands out to me here is that creating the subtask normally from the parent still works. That makes me think this is more likely something in the newer inline Create flow rather than your issue…

Thank you, Dani!