Kodi Jellycon : Bumping Recently Added Shows

[NepuddiN]

I am hoping there were a way or option for the user to change Jellycon behavior for older existing shows so it would be bumped to the top, when a new file or episodes are added to the library.
For example, suppose I have a Series spanning from 2010 which contained 3 Season, but for some reason I only downloaded the first season some years ago. Then I decided to continue watching and added new episodes around this week.
I have set my Kodi Jellycon to sort the shows by Date Added - Descending. For some reason, Jellycon doesn't bump the show in question to the top, and it retained the original Date Added order.

I can view the individual episodes are registered correctly from the Jellycon -Recently Added option, but I would like to view my libary as shows, instead of episodes.

Is there any way to configure the behaviour so new episodes, regardless of the original date added, would bump the shows to the top when sorted by Date Added?
Would using Jellyfin for Kodi instead of Jellycon the only option?

My considerations for using Jellycon instead of JF for Kodi is because I thought a low powered device like Firestick 4K would struggle with syncing and storing metadata.
Maybe I would install it one of these days... Does anyone here have some experience with my intended use case? FTV 4K with JF with Kodi and tell me how would it fare.

[NepuddiN]

Sadly, my suspicion is true in that using JF for Kodi directly in Firestick made it so unstable. It made FTV 4K keep restarting upon installation. I have to nuke the Kodi installation sadly. Dunno if it might due to Jellycon conflict. I disabled Jellycon prior to testing this though,,,

Edit : I'm not sure actually, seems like there were otherworldly forces at play because the restart was happening even after Kodi Refresh and restarting client, until I unplug the NIC and replug it. So weird...

In any case, hopefully there would be a way to bump recently added "Shows", not just episodes.

[mcarlton00]

Jellycon's behavior should match the web client's. I'm pretty sure they're using the same endpoints to retrieve the data being displayed.