Additional UX Regression: Child issue creation focus mismatch in Epic view after recent update

Question

Following the recent Jira update, there is a UX mismatch when creating child issues within an Epic view. Previously, the input field and the newly created issue were aligned at the bottom of the list.

Now, the inline input field appears at the top of the child issues list, but once created, the new issue is appended to the very bottom. On Epics with many child issues, the newly created task is immediately pushed out of the visible screen area, giving the impression that it failed to create.

Josh · Answer

Hi, that behaviour is a real UX regression, not something you misconfigured. If the inline create field sits at the top of the child list but new children are appended at the bottom, long epics will always scroll the new item out of view and look like a failed create.

Until Atlassian puts the input back next to where the item lands (or scrolls to it), the least-painful workarounds I've seen:

* After create, sort or filter the child list by Created so the new item is easy to find, if your view allows it.
* Create the child from the space List or board with the epic set as parent, instead of from the epic's child panel, when you're adding many items.
* For a single add, note the key in the success toast (if shown) and open it from there.

Worth a support ticket on a paid plan, or in-product feedback, with your steps and that the create field and the new item are at opposite ends of the list. Ask them to file a public JAC bug so others can watch it — I didn't find an existing public ticket that matches this exact "input at top / item at bottom" mismatch.

Tomislav Tobijas · Answer

Wait @usamah fefg - are we talking about new Jira work item view? If so, I'd definitelly recommend leaving a comment/feedback on that post for PM team to see and check it out 👀

Cheers,

Tobi

Arkadiusz Wroblewski · Answer

Hello @usamah fefg

I encourage you to open a support ticket if you see a regression.

Best,

Arek🤠