Opened 9 years ago

Closed 9 years ago

#95 closed task (fixed)

identify bitesized bugs in redmine

Reported by: Will Kahn-Greene Owned by:
Priority: major Milestone: 0.2.1
Component: infrastructure Keywords: bitesized
Cc: Parent Tickets:


We need a way to identify bitesized bugs in redmine.

More specifically, we need to:

1. "tag" an issue in some way so that it's clear it's bitesized
2. trivially query the system for all bitesized bugs

This gets progressively more important as we continue to get new

I'm going to make this an Immediate priority for 0.0.3 to at least
look into more. If it's the case that we can't do this, then that's
a very compelling reason to switch to another bug tracking system.


Change History (9)

comment:1 Changed 9 years ago by Will Kahn-Greene

I spent 5 minutes looking into this. Seems like there's a tagging
plugin for redmine:

` <>`_

I didn't see other viable options, but didn't look very hard, yet,

comment:2 Changed 9 years ago by Elrond

Milestone: 0.0.3
I'd vote for abusing the Esitmated time field. Filtering and
sorting would be easy. The field isn't used anyway currently. So
just use some magic values for magic amounts of work.
Just my strange idea.

comment:3 Changed 9 years ago by Michel Albert

Elvenlord Elrond wrote:

    I'd vote for abusing the Esitmated time field. [snip]

You could even argue that this *is* the proper field to be used.
The one and only ;)

Think about it! What does "bytesized" mean? In my opinion it is an
issue that can be resolved in a **short amount of time** given you
have the required knowledge. Say... less than two hours? one hour?

comment:4 Changed 9 years ago by Michel Albert

on a sidenote: Sorry for posting in here without visiting IRC first
(as mentioned in the docs). But behind my corporate firewall, this
is all I can do.

comment:5 Changed 9 years ago by Christopher Allan Webber

Michel Albert: NP about posting here first. Welcome to the

Anyway re: time fields: That's a component of it. I think there's
one more component of it though, and that's that a **new**
contributor could pick it up without much difficulty. There are
some tasks that wouldn't take long for a user who has already
tackled a few tickets but which would be completely overwhelming
for a new contributor.

Arguably this is still closer to bitesized than anything else we
have, but I really would love to see tagging some day...

comment:6 Changed 9 years ago by Elrond

Priority: ImmediateHigh
I (and lately others) have started to tag issues by adding
estimated times of 1 or 2 hours. 1 hour is like "very simple,
anyone can handle that", 2 hours is like "With a little reading and
some help, anyone can also do that, it'll take a bit of time".

Also I created a "Simple Issues" search for the project to search
easily for these issues.

Lowering Priority, as we have a working solution (or workaround).
Let's see, how well it works out.

comment:7 Changed 9 years ago by Will Kahn-Greene

The original url for this bug was .

comment:8 Changed 9 years ago by Christopher Allan Webber

Keywords: bitesized added
Milestone: 0.2.1

comment:9 Changed 9 years ago by Christopher Allan Webber

Resolution: fixed
Status: acceptedclosed

Now that we're in Trac, this is technically resolved!!closed&keywords=~bitesized

Yay Will!

Note: See TracTickets for help on using tickets.