There should be a way to regenerate item IDs for a specific item type in a project starting from 1 and ensure that the IDs are created in the order that the item type is listed in the hierarchy. This should be something that only a project admin can do.
Where this comes from is a need to re-order and re-number after a review and approvals process where other users have significantly changed the order and hierarchy of items. This doesn't occur all of the time, but there have been a few instances where a review has resulted in a massive restructuring of items, yielding item IDs that are completely out of order.
For example, I might have three requirements that were entered as follows:Req-1Req-2Req-3
But I've reorganized them in the hierarchy (and subsequently, the report) to be in a different order, as well as added another requirement:Req-3Req-1Req-164Req-2
If I use "regenerate item ids", the item ids update to:Req-167Req-165Req-328Req-166
When what I really wanted was:Req-1Req-2Req-3Req-4
Since the items IDs are different from the API ID and the Global ID used for tracking, I would expect that this operation would be available already, but it's not.
Hi Kristina and Jeremy:
Sorry for the delayed response, I haven't had a chance to get back to you until today.
The team does not do reviews in Jama because the number of people who are potential reviewers across varying projects is around 50-75. (Note that these reviewers are split across about 7 projects and that not everyone reviews every document. For example, we might have 10 reviewers on a single PRD, but only 5 reviewers on a single FMECA.) Therefore, with the number of potential reviewers for any given document as high as it is, we've found it a lower barrier-to-entry from a company standpoint to do reviews in MS Word or Excel and have a more limited set of people interact with Contour.
As far as tags are concerned, yes, this would be a great mode of data visualization if everyone was always working in Contour. However, since that's not the case, the headings in the output documents (which are directly related to the hierarchical structure in Contour) are more useful. With that said, if it was as easy to export the data visualization using tags as it is to say, create an export of a coverage view, then yes, this would be an excellent feature.
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204