Michał Krysiuk - Terano Apps Atlassian Partner

Hi @BGajula, Trudy and Matthew covered the permissions: Administer Jira, and the button reads Create flow. Sami laid out the native Space created rule well. One detail before you build it: {{createdIssue}} moves with every create, so after the first Story it points at that Story, not the Epic. Save the Epic's key with…

Hi @Xenia Chilkowich, One correction to the replies above, as of late October 2026: team-managed spaces do have Σ Original Estimate, and not only in list views. We tested a team-managed space last week with a Story estimated at 2h and subtasks at 3h and 5h, and Σ showed 10h ("1 day, 2 hours" with an 8-hour day). Where your…

Hi @Shivoy Malhotra, Your 3W-instead-of-4W example matches what we saw when we built the same tree on a Jira Cloud site last week: an Epic at 1h, Stories at 2h and 4h, and four subtasks with 24h between them. Σ Original Estimate on the Epic showed 7h, while the whole tree adds up to 31h. A few things from that test on the…

Hi @Charli Parker, Tomislav and Bartosz covered the native options: a manual Automation rule with Clone work item, or a Create link with the space and work type preset. One catch with the link: on Cloud it opens the older full-page Create issue screen with an empty description, so the DOR checklist still has to come from…

Hi @Anna Laptyuhova, One correction to the answers above, as of October 2026: team-managed spaces do show the subtask total, just not in the Original estimate field. I tested a team-managed space this week with a Story estimated at 2h and two subtasks at 3h and 5h: List view: add Σ Original Estimate from the column picker.…

Hi @Gor Greyan, The replies above have the native side right: Σ Time Spent and Include subtasks stop one level down, and JRACLOUD-93508 and JRACLOUD-70150 are the tickets to watch. Since you're going the Automation route, two things from testing the same tree this week (Epic → 2 Stories → 2 subtasks each) on a Jira Cloud…

Hi @Shin jeong hun, Ollie is right that Jira has no per-space view of storage: the Storage page in Atlassian Administration shows one figure for all of Jira. His ticket, JRACLOUD-75922, is now marked In Progress, but nothing has shipped yet. If you want to script it, Gabriela's correction is the route that works today:…

Hi @Benjamin Zhou, Adding to the accepted answer: as @Gabriela - LeanZero explained, the native Attachment field in JSM is not a regular field on the work item view, so no setting makes it show when it is empty, on old requests or new ones (JSDCLOUD-8576). If you need a file field that is always there, a custom field for…

Hi @Stephanie Blair, As Gabriela said, the built-in Field Required validator runs on every pass of the transition and has no setting that skips it when SDLC Exempt is checked. The Jira expression validators suggested above are the server-side way to make it conditional. A rule per field instead of an expression. I'm with…

Hi @Florian Ehlig, Gabriela's summary of the native side holds. Jira has no allow list of file types for attachments (the suggestion JRACLOUD-61024 was closed as Won't Fix), and the only size limit is the global Attachment Size under Settings > System > Advanced > Attachments. In the form builder, the Attachment field…

Hi @Karmandroid Singularity, Why the action fails: smart values have no {{#elseif}} or {{#else}} blocks, so Jira can't evaluate Rovo's expression and the action errors out. Arek's nested if() works. I tested it in the Original estimate field of the Create work item action for Badge Animation (Sub-task, parent Trigger work…

Hi @Eric Roetenberg, The two-rule split above works, but one rule is enough. Atlassian documents the pattern in Create new stories/tasks and respective subtasks when the automation rule is triggered, and I wrote it up step by step, with screenshots, in How to create a Jira Epic with all its Stories and subtasks in one…

Hi @Sav Cent , Glad you got it working. If you ever rebuild it, two answers in this thread fit together well. What native Jira allows: as Trudy said, a Task can't be a child of a Story, because both sit on the same level under the Epic. The Story–Task relation has to be an issue link, such as relates to or a custom link…

Thanks @Julia Foden, both are good additions. Rovo: since the edit API stopped checking screens, Rovo can change a field that’s off the Edit screen in the same way the REST API can, because it works with the user’s own permissions. Vanessa’s point is the important one: it no longer takes API skills. So Rovo belongs on the…

Hi @Khrystyna Tymofiychuk , A deleted Jira attachment doesn't go to a trash, so there is nothing left to empty for those files. What you describe matches a known Atlassian bug, CONFCLOUD-85021: after a large number of attachments is deleted, the storage calculation doesn't finish and the report keeps the old total. It's…

Hi @Chris Zander_xdpzy3, The "Read only" checkbox Rovo described doesn't exist. Field configurations, and the field schemes replacing them, can hide a field or make it required, but have no read-only setting. The convenience problem may be smaller than it looks, though. In the current work item view, people don't switch…

Hi @Mamidipaka Pavan Kumar, Besides John's self-looping transition, you can get close natively without changing the workflow: Lock it after creation: keep the field on the Create and View screens and leave it off the Edit screen. After that, nobody can change it in the work item view or the List view. Give admins a way…

Hi @Ricardo Figueiredo, It works in team-managed spaces now. I tested it on a Jira Cloud site in October 2026: jira.issue.editable = false on Done locked the work item in the interface and in the REST API, and the work item stayed visible. JRACLOUD-87543 was closed in 2024. Where to set it: Space settings → Work types,…

Hi @gollapudi sidhvi, Ciro's version of the transition pattern is the closest native fit. On the bulk edit question he raised: I tested it on a Jira Cloud site in October 2026, and taking a field off the Edit screen locks it only in the work item view and the List view. Bulk edit still offers a field that isn't on the Edit…

Hi @nboreddy , Keep Sami's validator either way. It sits on the workflow's Create transition, so it stops new Features wherever they're created, including quick create on the board and backlog. Its one gap is the first item on your list: Feature stays in the Work type dropdown, and people only find out after filling in the…

Hi @Manjunath Shivanna, Your concern is valid, and splitting QE work out doesn’t fix it on its own. The sprint report and the velocity chart count estimates on parent work items only (a QE sub-task’s estimate is left out), and neither breaks the total down by person or role. In a company-managed space, the closest native…

Hi @Pedro Wagner, On the error: /rest/api/3/attachment/content/{{id}} is an API endpoint, so a click in the browser doesn't always get through. A browser-friendly form is https://YOURSITE.atlassian.net/secure/attachment/{{id}}/{{name.urlEncode}}, worth trying in the child's Description. The file still lives on the parent,…

Hi @klevenick2, Sami's rule is the native way to get there, and it works: the form's field keys tell the rule which file is the SOW, and the rule writes names and download URLs into two text fields your export can read. Two things to know before you build on it: The columns are a snapshot. The rule runs only on Form…

Hi @Wei Sheng Foo, While JRACLOUD-92229 and JRACLOUD-94138 stay open, two native settings already cover part of what your CreateIssueDetails links did, each with a catch: Preset values per space: a custom field can have several contexts, each limited to chosen spaces and work types, with its own default value. The standard…

Hi @Amitava Chattopadhyay , The estimate half is settled above, so here is a note on the second half: developers logging their time every day. Why the Automation rules alone won't show who missed a day The rules suggested above are worth setting up, but they look at work items, not people: timeSpent IS EMPTY only catches…

Hi @Thorsten Schöning On the timeframe: nobody outside Atlassian can give you one. AUTO-2273 is still in Gathering Interest, with no comment from Atlassian. The closest precedent is from 2025, when Automation got a rich text editor, but only in the Confluence actions. Atlassian said they hope to bring it to every component…

Hi @Benjamin Zhou, Since adding a transition is off the table, the answer depends on one thing: do you need to lock only those two fields, or is it acceptable to lock the whole work item once it's Closed? The whole work item is fine: the status property Gabriela and Staffan described does exactly that without adding a…

Hi Catarina, I think the important part here is where you capture the cloned parent. Once the rule enters the Sub-tasks branch, the issue context changes to each original sub-task. So I would save the newly cloned parent's key before entering that branch. Something like: * Clone the template parent * Create variable:…

Hi @Helmut Priyanka, Short version: Jira Cloud has no duration custom field type you can create — nothing in the field-type list stores a length of time somebody types in. So it's a choice between compromises, and each one fails differently for what you described (four planned phase durations, typed by hand, used in…

Note: I'm aware this thread is more than six months old (per the Community Guidelines on necroposting) — I'm deliberately replying anyway, because the technical situation has changed since the last answers were written: Forge Object Storage is now generally available in production, which finally makes real attachment…