Opened 12 years ago

Closed 10 years ago

#3841 closed Bug (wontfix)

Inconsistency in tracker/tier numbering

Reported by: papibe Owned by:
Priority: Normal Milestone: None Set
Component: Web Client Version: 2.13
Severity: Normal Keywords: daemon transmission-remote


The web interface starts numbering from 1. But transmission-remote (option -it) starts from 0. Examples:

From Web:

  Tier 1

  Tier 2

From cli:

$ transmission-remote -n transmission:transmission -t 1 -it

 Tracker 0:
 Tracker 1:

This create confusion to me. If I want to remove a tracker using its id, which id number should I use? After trial an error I learned that transmission-remote's, but not without removing several trackers by mistake.


Change History (6)

comment:1 Changed 11 years ago by jordan

  • Component changed from Daemon to Web Client
  • Milestone changed from None Set to 2.50
  • Resolution set to fixed
  • Status changed from new to closed

The web client now uses the same numbering scheme as everyone else.

comment:2 Changed 11 years ago by livings124

  • Resolution fixed deleted
  • Status changed from closed to reopened

The Mac client starts at Tier 1. This should be the correct way as far as users are concerned. The value actually being 0 is an implementation detail users shouldn't need to know.

comment:3 Changed 11 years ago by jordan

I agree with the point about the different audiences intended for the GUI clients and low-level tools like transmission-remote.

Another point is that numbering tiers at all in the GUI is a little misleading, since it refers back to when they were used in order. However we now announce to all tiers in parallel.

Maybe the GUI shouldn't number them at all.

comment:4 Changed 11 years ago by livings124

Numbers aren't that helpful or meaningful, but I feel like numbers do help differentiate. The audience for the web client, at least, should have it start at 1. I don't see a reason for all clients to start at 1.

comment:5 Changed 11 years ago by livings124

  • Milestone changed from 2.50 to None Set

comment:6 Changed 10 years ago by livings124

  • Resolution set to wontfix
  • Status changed from reopened to closed

#5118 does the opposite of this.

Note: See TracTickets for help on using tickets.