BugNET

Open source issue tracking & project management

Forums

HomeHomeSupportSupportGeneral SupportGeneral SupportWhatWhat's the best use of the "Milestone" field when logging issues?
Previous
 
Next
New Post
11/10/2009 1:56 AM
 

Hi,

I'm a new user of BugNet and wanted to get some help with the use/reason for the Milestone field when logging an issue.

The documentation says "When creating an issue, you assign the issue a version or milestone such as First, Second, or Third." but there is already a field for Version. I'd like to know how others use the Milestone field or do people ignore it?

Thanks,
Tony

 
New Post
11/10/2009 8:24 AM
 

I've found the answer to my own question. The Milestone is the expected version number of when the issue will be released.

Seems a bit strange to me it can be set by the person logging the issue, rather than after an investigation in to the amount of work has been performed, but I guess it can always be changed.

 
New Post
11/22/2009 1:38 AM
 

Hi

I leave the milestone for the triage team - or the project manager/lead, etc to complete after the bug has been analysed not by the person reporting the bug. I let my developers cherry-pick bugs with < 1/2 days estimated time in conjunction with any bugs/features they have as planned work. The milestone then becomes the version implemented in as well as the version targeted.

 
Previous
 
Next
HomeHomeSupportSupportGeneral SupportGeneral SupportWhatWhat's the best use of the "Milestone" field when logging issues?


Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.