Opened 8 years ago

Closed 8 years ago

Last modified 5 years ago

#5030 closed enhancement (wontfix)

Stop auto-assigning Trac tickets based on the component

Reported by: karsten Owned by: erinn
Priority: Medium Milestone:
Component: Internal Services/Service - trac Version:
Severity: Keywords:
Cc: mikeperry, phobos, pde, aaronsw, erinn, asn, n8fr8, atagar, nickm, runa, kaner, ioerror, chiiph Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Trac assigns new tickets to the component owner if no ticket owner is specified. But in my understanding the ticket owner is the person who's supposed to work on a ticket. This requires a commitment from the person. Auto-assigning a ticket is the wrong concept here.

Should we remove component owners to stop auto-assigning tickets based on the component?

The question is: how we can ensure that the right persons learn about new tickets. Can we assume that current "component owners" know how to filter their tor-bugs email?

(Cc'ing all component owners.)

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by Sebastian

I think auto-assigning is fine. By default if something shows up in "your" component, you should deal with it, even if that means changing the ticket state to indicate that you're not gonna deal with it further.

comment:2 Changed 8 years ago by phobos

The history is that we started auto-assigning way back in flyspray. It turns out that no one looks through a queue of unassigned, new tickets.

comment:3 Changed 8 years ago by arma

My workflow would be fine if autoassigning stopped, because I get all the trac mails anyway. But I think I'm not the owner of many (any?) components.

Notice that we can change on a per-component basis whether there's an owner that gets autoassigned. So perhaps Karsten can identify some specific people (e.g. himself) who want to try the other approach for their components?

I think if Karsten wants to declare a new project-wide policy that tickets only have owners when a specific person has explicitly signed up for the ticket, which means it's easy to know from the ticket whether the component owner knows about it... I'd be willing to go along with it if other people want it, but I bet it'll be messier than it sounds.

comment:4 Changed 8 years ago by karsten

Sebastian and arma are not the owner of any component. phobos is the owner of Company and Website. nickm is not the owner of the components that I think he cares about (Tor Bridge, Tor Client, etc.), but he's the owner of Tor Check which he doesn't care about, AFAIK.

I removed myself as the owner of some metrics components. My workflow is based on tor-bugs email filtering, not only on the concept of ticket ownership. I notice new Metrics tickets without being the component owner.

If others want me to remove their role as component owners, please let me know.

I realize the discussion of project-wide policies should happen in another place than here. I'll bring it up at the dev meeting.

comment:5 Changed 8 years ago by atagar

My preference is to be auto-assigned for my components (arm and stem). I don't use the field so it doesn't matter much, but I'm the first to work on those tickets so it's a more accurate initial state for them.

comment:6 Changed 8 years ago by karsten

Resolution: wontfix
Status: newclosed

Giving up on suggesting to make it a project-wide policy that owning a ticket means being responsible for it. I'll use that semantic for project tickets and for my own tickets. I also removed myself from being the component owner of anything. Other component or ticket owners can do whatever they prefer. Closing.

comment:7 Changed 5 years ago by qbi

Component: TracService - trac

Move all tickets from trac to "Service - trac" component.

Note: See TracTickets for help on using tickets.