From that perspective, the underlying problem is that JIRA puts every
"release" on the "roadmap" whether we want it to or not. It's not that we are using JIRA wrongly, only that JIRA, like any off-the-shelf product, is imperfect.
We are mapping what we want to do to the JIRA system, the best way we know how. Leaving issues at unknown is not workable, since as Craig and Martin pointed out, we want a "job jar" of issues that have been reviewed and found joyful, but have not been assigned to a specific milestone or release series. On 2/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
The purpose of the Road Map is to assign issues to a release. Since "Future" is not a version or a release -- but just a grouping of issues for the "future" -- it has little use, and the way we use it tells me we're using the Road Map wrongly. Now, I believe that's the case, but I am not going to fight this issue too strongly because it is not critical to anything. I'll go back and look at the archives, but there's nothing wrong with re-examining past decisions. I haven't seen other JIRA projects slating things into a "Future" version -- and probably because it's not a version. Paul
-- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
