Kanad Dagaonkar Atlassian Team

@Blum_ Volker _Extern_ : While we establish contact with right team at ScriptRunner, do you mind hopping on a quick call with us, so that we can debug this quickly? Link to my calendar: Meet with Kanad

Thanks, everyone — we're reading all of this. First, I appreciate the detail in these comments. This is exactly the kind of feedback that helps us, even when it's tough to hear. I want to acknowledge what we're consistently hearing from you so you know it's landing, not disappearing: * Fields are hard to tell apart :…

 @SA : We'd love to dig into this with you directly. Rather than going back and forth in the comments, would you be open to a quick 30-minute call? It'll let us see the issue in your environment firsthand, understand the steps that trigger it, and get it in front of the right people on our team to fix. You can grab a time…

@Ankit Thakur Good catch, Ankit — and you're right that Similar Work Items is a useful guard against duplicates. It is not surfaced in the compact view yet. We're reworking the detection logic to make the suggestions more accurate, and we'll bring them back into the new Create shortly. @Selena Vogel Thanks Selena, and…

Update: We're rolling "Summary" back Hi everyone — an update, and a genuine thank you. When we introduced the new create experience, we renamed the Summary field to Title — and this thread was one of the clearest signals that we hadn't got it right. You told us it broke muscle memory, clashed with your docs, training, and…

When you say that Custom Create Screens will expand the create modal, do you mean if the Create operation has a different Screen than Edit and View, or is it any Screen that we have created ourselves? Hi @Rune Rasmussen — good question, and there's one subtlety worth making explicit, because I think it's the bit you're…

Hi @Mark Baird Thank you for the detailed write-up, and genuinely sorry for the frustration. You're right, and it's a fair callout: the "Always open in this view" toggle wasn't persisting your preference, which is exactly the kind of thing that shouldn't slip through — especially when it means clicking through to your…

@Apryl Harris : This will be part of Bundled Release 

@Itamar Ben Sinai : Please find my comments - * We are pre-fetching the fields that are marked required from field validator in create workflow and showing them in Required field section upfront * There is a "Required" label and a vertical separator between Required and Optional fields in Quick Create. In Full form mode,…

@Cornelia Jeppsson : The Full Form load automatically if your work item has more than three required fields Thanks @Darryl Lee for covering up :)

@Ross Angelov and @Lorenzzi Bassoto : Forge/custom create extensions: Full Form opens by default when Forge UI modifications are present. Please let us know if you still run into problems and we would take care of it! 

Thanks @Julia Foden, this is helpful feedback. On Summary appearing as Title: this is a Create-screen label change only. JQL, APIs, dashboards, and integrations still use summary. In our end-user research, users found “Title” clearer at create time, so we made that tradeoff intentionally. A few of your other points are…

@Dave Mathijs : Thanks, for the interest shown! JSM/JPD are not part of this rollout; we’ll share updates separately as soon as timelines firm up.