Opened 7 years ago

Last modified 7 years ago

#5528 new Bug

magnet link with auto-assigned group loses group

Reported by: MB Owned by: livings124
Priority: Normal Milestone: None Set
Component: Mac Client Version: 2.82
Severity: Normal Keywords: group, magnet link
Cc:

Description

When a magnet link successfully gains a group setting based on the "Assign group... based on criteria" settings it will lose this group when the torrent info has been downloaded.

I know related issues with group assignment to magnet link torrents have been up before, but I haven't seen this prior to 2.82, so this seems like a significantly separate issue and not a duplicate.

I have only tested with the mac client.

Change History (4)

comment:1 Changed 7 years ago by jordan

  • Component changed from Transmission to Mac Client
  • Owner set to livings124

comment:2 Changed 7 years ago by MB

I have now tested some more and unfortunately found this issue is intermittent. I'm trying to find exactly what triggers it. Is perhaps the tagging made twice and some data may be different in the magnet stage compared to the torrent stage? I don's see how this can be, but maybe there's misread data in the process.

I'm using data from the name for the tagging, which I assumed is known already at the magnet stage.

comment:3 Changed 7 years ago by MB

So I've found that when the magnet link contains the string that matches with the criteria set for group assignment and the name of the torrent do not, this is what causes this behaviour.

"No group" must be considered undesirable if you have set up rules for automatic group assignment.

I see two simple resolutions. Perhaps the simplest one is to distinguish between the magnet link name and the name of the torrent. The user can then set the criteria based on the either one of these. If the latter does not contain the same string the group assignment already set is respected.

Another possible resolution that embraces the current feature that magnet link names are initially treated as torrent names would be to assume that when a group assignment have been set based on one piece of criteria (the magnet name) then the group should not be removed again if the actual name of the torrent does not contain the same string. This is natural user expectation.

So if that the criteria string is "theCriteria" set to name and has been set to be assigned the group "Green" in Groups preferences this should give this behaviour: -> Given that the magnet link DOES contain the string "theCriteria" and the group is set to "Green". -> When the torrent name can be read after download it DOES NOT contain the string the string "theCriteria" -->Then the group assignment stays.

and if -> The magnet link DOES NOT contain the string "theCriteria", the group is not set -> When the torrent name can be read after download it DOES contain the string "theCriteria" and the group is set to "Green" -->Then the group assignment of course stays.

It's of course acceptable that if there are conflicting group assignment rules that are triggered both by the magnet link name and the name of the torrent, that the latter decides the group. Again, It's just that "No group" must be considered undesirable if you have set up rules for automatic group assignment. Automatic group removal is not a useful behaviour, though a change to another group may be.

comment:4 Changed 7 years ago by MB

As I've now given more info I'm sure you agree it's unlikely that this bug is limited to the Mac Client. Unless of course handling magnet link names and torrent names are specific to platform. I find that unlikely though.

Note: See TracTickets for help on using tickets.