0

Both theses work items seem (at least to me) to be interchangable, with the possible exception that work items may be usable for non-defect changes (such as new functionality).

Is that all there is to it, or is there some more fundamental difference between the two?

skaffman
  • 398,947
  • 96
  • 818
  • 769
paxdiablo
  • 854,327
  • 234
  • 1,573
  • 1,953
  • 5
    I'm voting to close this question as off-topic because it is not about programming. – Vadim Kotov Oct 25 '17 at 08:57
  • @VadimKotov, not that I care any more (since I've moved well beyond RTC) but wouldn't this be covered by the "software tools commonly used by programmers" clause in the help center? – paxdiablo Oct 26 '17 at 01:07
  • Please take a look at this [answer](https://meta.stackoverflow.com/questions/343829/is-stack-overflow-an-appropriate-website-to-ask-about-project-management-issues/343841#343841). This question is not unique to software development and this tool can be used not only by programmers - Rational Team Concert can be used by Project managers, testers, etc. For example, JIRA-related questions are off-topic here too, but questions about using JIRA API are not. – Vadim Kotov Oct 26 '17 at 09:40

1 Answers1

3

A Task is an an over-arching work item type meant to encapsulate a piece of work that does not fall under the umbrellas of the other work items (Defect, Story, Bug Report, and Feature Request, by default). Typically, new functionality would fall under the Feature Request umbrella.

Work items that might be good candidates for Tasks might include:

  • researching the capabilities of a library you are considering adopting,
  • building a new test client, or
  • filling up the soda machine.
cheeken
  • 33,663
  • 4
  • 35
  • 42
  • 1
    This is all true, but it's worth noting that the significance is WHAT YOU PLACE ON IT. With RTC you can massage your process definition in any way you see fit, meaning that you can remove or add work item types as appropriate to your project. – Erigami Aug 03 '11 at 14:24