Project

General

Profile

"Category" vs. "Target version" fields in issues

Added by Joseph Mornin almost 14 years ago

Hi,

I'm confused about the difference between the "category" and "target version" attributes on an issue. Is there an example somewhere showing how to properly define these fields? I've read the "issues" section in the guide, but it leaves the "target version" field blank, with no other commentary.

We're using Redmine as a project management tool for a research project--especially for writing a white paper and keeping track of use cases--rather than for a software development project. If we were writing code, I assume the "target version" field would be used to determine which release version should include the issue at hand. Can anybody explain how to use these fields in our context?

Thanks very much!


Replies (2)

RE: "Category" vs. "Target version" fields in issues - Added by Robert Smith almost 14 years ago

I would say that Categories should be:
  • key areas of interest in your domain, the research project
  • well-defined and non-overlapping
  • not more than a dozen unless there's a clear need
  • not transient
For the case you cite these might be:
  • Background Research
  • Use Cases (one main area of the new research)
  • (other main areas of the new research)
  • Research Paper
Then the Target Versions would be major milestones. Cast as a PhD project these might be called:
  • Stop Reading (this is tied to all the background research issues, or when the supervisor asks when you'll be starting to do some real work)
  • Final Draft (tied to all new research issues and some of the research paper issues)
  • Submit (tied to remaining research paper issues, e.g. reviewer feedback, check references, format compliance)

Just some thoughts, I hope they help.

RE: "Category" vs. "Target version" fields in issues - Added by Joseph Mornin almost 14 years ago

Thanks--this is very helpful!

When I get a chance, I'll edit the Redmine guide wiki to be more clear on this.

    (1-2/2)