Similar to Ignasi, I use the fix version when creating issues to indicate the target release an issue *should* or *will* be fixed in. That value typically does not have to change once the issue has been marked resolved.
I plan to start using the "Start/Stop Progress² more effectively and that will help track overall progress. There are only 6 issues "In Progress² at the moment, and I know the community is a lot more busy that that! ;) /jd On 9/3/14, 8:17 AM, "Ignasi Barrera" <n...@apache.org> wrote: >I've often set the Fix Version before the issue was assigned or fixed, >because that's the way you can take a look at the road map in JIRA. > >People using JIRA to track the "state" of the next version to have an >idea of the progress (how many planned issues remain unresolved, etc), >would use the roadmap view, which uses the Fix Versions. > > > >On 3 September 2014 17:12, Andrew Gaul <g...@apache.org> wrote: >> On Wed, Sep 03, 2014 at 01:55:20PM +0000, Everett Toews wrote: >>> On Sep 2, 2014, at 5:50 PM, Andrew Gaul <g...@apache.org> wrote: >>> >>> > I would like to move all tasks to a >>> > indefinite version and only move a task to a definite version when we >>> > have an owner and a corresponding JIRA issue. Thoughts? >>> >>> +1 >>> >>> I¹ve never understood why we set the Fix Version when an issue (a) >>>hasn¹t been fixed and (b) hasn¹t even been assigned to someone. >> >> I removed the fix version for 20 orphan issues previously listed at: >> >> >>https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND% >>20resolution%20%3D%20Unresolved%20AND%20fixVersion%20!%3D%20null%20AND%20 >>assignee%20%3D%20null >> >> Most of these had no activity for months. >> >> -- >> Andrew Gaul >> http://gaul.org/
