Tracing requirements to projects
I'm curious how other groups are tracing requirements to projects (tracking what requirements are added for a particular story or work item). We are on DNG 5.0.2 but are getting ready to upgrade to 6.0.4. We trace all of our requirements to a project identifier (we use Jira). We do this by creating a project identifier attribute and putting the project id (JIRA number) in. If there is more than 1 JIRA for an artifact, we use a comma to separate.
There is a defect ( work item112913) that the attribute field can only contain upwards of 1024 characters but if that number is exceeded, the method to add artifacts to a collection by selecting an attribute using the "Contains" method fails. We haven't reached this limit yet, but I'm worried when we do.
Would love to hear how other groups are handling this. Thank you in advance!
|
One answer
Rachel,
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.