From the peanut gallery...
How we do this stuff at my day job is that we create versions in Jira
for each of the milestones (which I think is what you guys are talking
about) which lets us use the roadmap feature, etc..
We also create an artificial milestone called "Future" that we assign
things that are of the wish-list variety. We always schedule it after
all of the other versions so that it doesn't bog down the roadmap displays.
-Paul
Don Brown wrote:
Personally, I agree, although I know there are those that see them still
as a valuable source of ideas. By emphasizing Milestones, though, they
will fade into the background.
I'd be in favor of a "Probably Never" resolution though :)
Don
Niall Pemberton wrote:
On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote:
JIRA is already on Apache servers.
But back to the topic, what do folks think of the proposal to target
tickets to
milestones and use them for release planning? I think we should start
immediately by creating upcoming milestones, and going through all
our old
tickets and assigning them to the new milestones. This would go a
long way to
folks wondering what exactly was in 1.3.0.
+1, but what we could probably do with is closing down tickets that
have been open too long and are never going to be realistically done -
can we have a "Probably Never" target?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
