harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Simons <m...@leosimons.com>
Subject Re: New JIRA 'component'?
Date Wed, 18 Jan 2006 17:11:51 GMT
On Wed, Jan 18, 2006 at 04:48:29PM +0000, Tim Ellison wrote:
> (Geez, that component word is overloaded...)

No kidding!

> What do you think about having a new JIRA component called "Classlib -
> Newcomer" where we can put bugs that are good candidates for people to
> start with?

Suboptimal. Jira can do so much more!

> I experimented with modifying the issue summary to have a structured
> keyword ( #easy# or something ), but it's a bit of a hack, and I don't
> see any way to produce a URL for a filter that will find them easily.
> This is part of the wider goal to make it easy for people to contribute
> to Harmony.  Other suggestions welcome of course.

Another option is to have a custom field. Eg we could have something like

"Estimated Complexity"

field, and then make the select list of values something such as

 Needs James Gosling

with "Uknown" as the default value. Having a plain text field is
also possible, as well as several others (multiple selection list,
textarea, checkboxes). Hmm. Checkbox might be what you described
above, eg you have a checkbox like

 [ ] Easy to fix

when you create or edit an issue.

Yet another option is to (ab)use one of the other fields, such as
"priority", "status" or "resolution". I've also seen the "version"
dimension abused for this (eg create an "easy" version). Me being the
semantic web enthusiast I am, I like having a specific field. (Really
what we want here is not clear to me yet. I also just don't know what
we should call this thing. Its possible to create a "summary view"
that includes this stuff and define searches/filters for them.

I can set that up (as can about a 100 other people with jira admin
privileges, probably at least Geir too, I suspect Dims too), just
need to know what we want.


View raw message