Do we think we need to limit the popups Jira shows these days?

[Bhupinder G]

When we create a new work item; Jira shows a popup "You created a work items..." and if you are creating multiple work items the popups keep on showing one after the another. Sometimes they need to be closed one by one. Atlassian should get stats on how many users actually need the popup and use the link that comes with it. Sometime yes; if one has to bookmark but a work item created afresh might not have enough information. Work item is anyways created and there is no option in the popup to delete it so I think there is very limited use of the same and more of a distraction.

[Tomislav Tobijas]

Yeah... this can be improved for sure @Bhupinder G 
I'm not a fan of that button "View work item" (when I create a single one) which then redirects me to JQL search with just that one item.. Then I need to click on the item key/link actually to open it 🫠

While I can see some benefits, it's usually unnecessary. Generally speaking, it would be great if this could be configured either on the admin side or on a per-user basis.

Anyway, there are a couple of feature requests, and one of the bigger ones is this: CLOUD-11698: Disable all in app pop-ups (also check linked suggestions) 👈

I actually tend to create items more and more through Rovo and MCP so that actually isn't that big of a deal that it used to be. 

But to get back on topic, I hope this will be improved at some point.

Cheers,
Tobi

[Jovânio Junior]

Hi Bhupinder, welcome to the Atlassian Community!

I agree this can get distracting, especially when creating several work items in a row.

The confirmation popup is useful occasionally because it gives quick access to the item just created, but when multiple items are created back-to-back it can become more noise than help.

I’d like to see either:

an option to disable these confirmations;
automatic grouping when several work items are created;
or a shorter timeout so they disappear faster.

For users doing bulk/manual creation, the current behavior can definitely interrupt the flow more than it helps.

I think this would be a good candidate for an Atlassian product suggestion.