Skip to content

Conversation

@aaron-kruse
Copy link

Makes the torrent's "Created On" date/time available (but hidden by default) in the main transfer list for sorting and better visibility.

Unlike the "Added On" column (which shows when a torrent was added to the client's list), this shows the date the torrent file was originally created. This is something that can help prioritize which torrents to seed. I have a long list of torrents and looking at each one's properties for the "Created On" date isn't feasible. With the addition of this column, I can just sort by it and bring the oldest torrents to the top of the list. Similarly, I can sort by the number of seeders to find which torrents could use some help the most, then glance at the "Created On" column (ex. I'd rather seed torrents from 10+ years ago that are struggling due to age/availability vs. ones from a few weeks ago that have been replaced by newer/better options). This column could also help with cleaning up your list of torrents by making them easier to work with based on their actual age (and not date added/completed).

I should also maybe mention that this is my first submission here, so hopefully I've followed all the guidelines correctly. I added this column using other similar columns as an example and everything seems to be working fine, but if I missed anything less obvious, please let me know!

Screenshot for reference:
image

This column makes the torrent's "Created On" date/time available in the
main transfer list for sorting and better visibility.
@stalkerok
Copy link
Contributor

stalkerok commented Dec 27, 2025

@Chocobo1 Chocobo1 added the GUI GUI-related issues/changes label Dec 27, 2025
TR_POPULARITY,
TR_CATEGORY,
TR_TAGS,
TR_CREATE_DATE,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC you can only add new values to the end of the list, otherwise it affects existing user's setting. Something like user will see the visible columns are not the same columns as before.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had thought about that and wasn't sure if something like that might be an issue, but after looking at the ordering/grouping of the current values, it seemed like similar things were being grouped together and putting this in with the other date-based values would be the "right" answer. I also didn't have any issues in testing, although my testing wasn't very thorough and was using "out-of-the-box" setup.

I can move this if needed (it doesn't make me any difference) but it might be good to clarify if it's really necessary since that would go against how things are currently setup here (with all date-based values being grouped together).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

GUI GUI-related issues/changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants