Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#3828 closed Enhancement (invalid)

[Feature Request] More advanced control over Transmission (see in details)

Reported by: mcgiwer Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.13+
Severity: Normal Keywords:
Cc: mdziczkowski@…

Description

My idea is to increase the configuration possibilities of Transmission and allow to:

  • cut-off slow hosts (mostly leechers)
  • kick and BAN hosts (security feature)
  • better manage the block list (security feature)
  • resize the columns in the informational tabs (peers and files)
  • do automatic updates of software and block list

Future ideas will come soon (hope so) :)

Change History (5)

comment:1 Changed 11 years ago by charles

  • Milestone changed from 2.20 to None Set
  • Resolution set to invalid
  • Severity changed from Major to Normal
  • Status changed from new to closed

One topic per ticket, please. Otherwise tickets are impossible to manage.

For example, different ideas may have different milestones, and different priorities. Piling them together in one ticket, and giving them all a "Major" severity, and giving them all a milestone for the next release... that's basically the equivalent of saying "drop everything and work on my list of changes! further ideas will come soon!"

So: leave the milestones to whoever's going to be doing the code, and don't make open-ended tickets. Thank you!

Last edited 11 years ago by charles (previous) (diff)

comment:2 follow-up: Changed 11 years ago by mcgiwer

  • Cc mdziczkowski@… added

In my modest opinion, your suggestion about making new ticket for every idea was unnessecary, because if I would do as you suggest then it would be harder to manage the ticket's then if it's put in one as I did.

Additionally, it wasn't a bug report, so there was no need to set it into "invalid". Please set it back to "new". Thanks.

Last edited 11 years ago by mcgiwer (previous) (diff)

comment:3 in reply to: ↑ 2 ; follow-up: Changed 11 years ago by charles

Replying to mcgiwer:

In my modest opinion, your suggestion about making new ticket for every idea was unnessecary, because if I would do as you suggest then it would be harder to manage the ticket's then if it's put in one as I did.

Thank you. Let's say hypothetically that the development team agrees to all six of the changes you suggested in this ticket (with future ideas to come soon), and that we decide to do half of them sooner than the others. What milestone should the ticket have? Let's say five of them is a "Major severity" as you suggested, but one doesn't. What severity should the ticket have? Let's say we implement half of the features and are ready for a release... but we can't close the ticket, because there are three other unrelated issues shoehorned into the ticket.

So, separate topics belong in separate tickets.

Additionally, it wasn't a bug report, so there was no need to set it into "invalid". Please set it back to "new". Thanks.

For the reasons listed above, I'm not going to do that. No insult is intended.

Last edited 11 years ago by charles (previous) (diff)

comment:4 in reply to: ↑ 3 Changed 11 years ago by mcgiwer

Replying to charles:

Thank you. Let's say hypothetically that the development team agrees to all six of the changes you suggested in this ticket (with future ideas to come soon), and that we decide to do half of them sooner than the others. What milestone should the ticket have? Let's say five of them is a "Major severity" as you suggested, but one doesn't. What severity should the ticket have? Let's say we implement half of the features and are ready for a release... but we can't close the ticket, because there are three other unrelated issues shoehorned into the ticket.

Thank You for the answer. I didn't told in any of my tickets that all of my ideas need to get implemented at once. Eveen if implemented in the order as the developer wish, it's easier if the ideas are in one ticket then multiple ones. Let's don't make the developers work more harder then it is by asking them to use many time to see the seperated tickets.

comment:5 Changed 11 years ago by charles

It is easier, not harder, for developers to use single-topic tickets.

Note: See TracTickets for help on using tickets.