Project area not capable of creating Requirement
When I attempt to create a Requirement in a project area that I created with the Eclipse Way process, I get the following error:
No project area capable of creating requirement type Requirement could be found.
However, I can successfully create a Requirement in the Cloudburst sample project, built from the Sample process. Is there something special about the Sample process that allows this? Is there some bit I need to flip to get the Requirement piece working?
FWIW, I can successfully create a Story, just not a Requirement or Nonfunctional Requirement, or Use Case, or a bunch of other Requirement-type thing. If I right-click on Requirements in Team Artifacts, I have these choices:
* Story
* Glossary Term
* Classification
* Document
* Query ...
In the Sample project I have many more choices. Thanks in advance ...
shawn.
No project area capable of creating requirement type Requirement could be found.
However, I can successfully create a Requirement in the Cloudburst sample project, built from the Sample process. Is there something special about the Sample process that allows this? Is there some bit I need to flip to get the Requirement piece working?
FWIW, I can successfully create a Story, just not a Requirement or Nonfunctional Requirement, or Use Case, or a bunch of other Requirement-type thing. If I right-click on Requirements in Team Artifacts, I have these choices:
* Story
* Glossary Term
* Classification
* Document
* Query ...
In the Sample project I have many more choices. Thanks in advance ...
shawn.
2 answers
Pls file a work item against the requirements component.
Kai
"shawnlauzon" <lauzon@us.ibm-dot-com.no-spam.invalid> wrote in message
news:fakd55$109$1@localhost.localdomain...
Kai
"shawnlauzon" <lauzon@us.ibm-dot-com.no-spam.invalid> wrote in message
news:fakd55$109$1@localhost.localdomain...
When I attempt to create a Requirement in a project area that I
created with the Eclipse Way process, I get the following error:
No project area capable of creating requirement type Requirement could
be found.
However, I can successfully create a Requirement in the Cloudburst
sample project, built from the Sample process. Is there something
special about the Sample process that allows this? Is there some bit
I need to flip to get the Requirement piece working?
FWIW, I can successfully create a Story, just not a Requirement or
Nonfunctional Requirement, or Use Case, or a bunch of other
Requirement-type thing. If I right-click on Requirements in Team
Artifacts, I have these choices:
* Story
* Glossary Term
* Classification
* Document
* Query ...
In the Sample project I have many more choices. Thanks in advance ...
shawn.