Opened on 03/27/2014 at 10:42:28 AM

Closed on 04/03/2014 at 08:20:43 AM

#223 closed change (fixed)

[trac] Get rid of the in-progress flag

Reported by: fhd Assignee: philll
Priority: P3 Milestone:
Module: Infrastructure Keywords:
Cc: philll, trev Blocked By:
Blocking: Platform:
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):



We have an "In progress" checkbox now. I don't think a flag is the best way to communicate this: If something is "assigned" it means the assignee will see to it that it gets done. If anyone is wondering if the work already started or how far it is, they can ask the assignee. Plus, this is quite likely to get out of sync with reality, since it'd need to be changed frequently.

What to change

Remove the "In progress" flag.

Attachments (0)

Change History (8)

comment:1 Changed on 03/27/2014 at 10:43:12 AM by fhd

  • Cc philll added

@Philip: I deliberately didn't mark this as "ready", please do so if you consider the discussion on IRC concluded. If not, please voice concerns.

comment:2 Changed on 03/27/2014 at 10:43:35 AM by fhd

  • Component changed from Unknown to Infrastructure

comment:3 Changed on 03/27/2014 at 10:47:36 AM by philll

I think, it might be a valuable info for our community and especially for our staff, what we are working on right now. I regard this as a part of resource planning.

comment:4 Changed on 03/27/2014 at 11:02:07 AM by fhd

  • Cc trev added

Seems we need you here Wladimir, apparently this is still deadlocked.

My point above is pretty much that we have that info anyway, in a way that's not out of sync, if we actually ask. Which is how this is usually handled on public bug trackers from all I can tell.

comment:5 Changed on 03/27/2014 at 11:10:33 AM by trev

I agree with fhd, the added value of this flag is negligible. Yet it introduces significant overhead to the work flow as I noticed myself already. It is also something that I tend to forget, we'll have stale or missing flags rather frequently which will negate any potential advantages. To sum up: I don't consider this worth it. It's better to discourage bug hugging instead, issues should only be assigned if they are about to be addressed soon - otherwise they should be free for anybody to take.

comment:6 Changed on 03/27/2014 at 11:26:51 AM by philll

  • Owner set to philll
  • Ready set
  • Status changed from new to assigned

comment:7 Changed on 03/28/2014 at 02:45:15 PM by philll

  • Review URL(s) modified (diff)
  • Status changed from assigned to reviewing

comment:8 Changed on 04/03/2014 at 08:20:43 AM by philll

  • Resolution set to fixed
  • Status changed from reviewing to closed

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from philll.
Note: See TracTickets for help on using tickets.