I wonder if this is unintentional. I can't find anything that would limit the bundles (groups) to 25 items. However, the number of items shown in the dropdown is limited to 25 (which I found hardcoded in a few places), and perhaps this just interacts poorly with bundling.

Thanks for the quick response. I think you're right, I think it's a maximum of 25 for the whole dropdown tray. The below screenshot adds up to 25. I will update the ticket.

Relevant: T145250: Consider requesting more notifications if the popup only has bundles

Increasing the limit to something like 100 is probably easier than reworking to support "no limit" with a potentially very large number of items. Would that work for you?

I didn't find information about why the 25 limit was added, it looks like it was there from early on in rECHO9262614ded46: Initial version of Special:Notifications Javascript page and rECHOcf994794683a: Display a message if there are no notifications in Special:Notifications.

200 might be a better upper limit. But yes I'd be fine with any increase. Incremental improvement is good :)

In T317365#8232576, @Novem_Linguae wrote:

200 might be a better upper limit. But yes I'd be fine with any increase. Incremental improvement is good :)

+1; @kostajh is this something the Growth Team can take on fixing?

In T317365#8253643, @ppelberg wrote:

In T317365#8232576, @Novem_Linguae wrote:

200 might be a better upper limit. But yes I'd be fine with any increase. Incremental improvement is good :)

+1; @kostajh is this something the Growth Team can take on fixing?

@KStoller-WMF without having looked too closely, it seems like it would involve updating a number (25) used in a few places to a higher limit (200), plus QA time from @Etonkovidova. Should we try to fit this in sometime in the next weeks?

I'm in support of this change, but we already have way too much work pulled into our current sprint. So, in an attempt to help us focus and stick with how we attempt to prioritize passive maintenance work, I'm going to move to Triaged rather than Current Sprint.

On the API side, suggest updating includes/api/ApiEchoNotifications line 585 to

IntegerDef::PARAM_MAX => ApiBase::LIMIT_BIG1,
IntegerDef::PARAM_MAX2 => ApiBase::LIMIT_BIG2,

That should raise the notification API limit from 50/500 to 500/5000, allowing non-admins to fetch 200 notifications at a time.

Will try to finish the JavaScript side of this and write a patch, if I can get DiscussionTools working on my localhost wiki. Currently when I click subscribe nothing happens, so I must have broke something or missed a step when installing it. My goal is to get it installed so I can subscribe to a topic thread, add 26 responses, then the notification tray will group them into 25 notifications. Then I can test my JavaScript changes to make sure that it turns into a group of 26.

Also open to suggestions on other ways I can test this.