Why the requirements cannot be seen in the folder even though they were imported in a module?
![]() The requirements were imported in a module (e.g. module name - XYZ). Hence these requirements should show up in the module as well as in its respective folder (e.g. folder name - XYZ artifacts). However, these requirements are only being shown in the module and not in the respective folder. Since I am creating links, tags and views for the base artifacts, I would like to see these requirements in the folder. Is there a way to get these requirements to show up in the folder? |
2 answers
![]()
We had this happen to us, too. We are not sure how, but we had a module with 693 artifacts and when you hovered on each artifact, no folder was shown, but it did show "Use in Module <Module Name>". If you opened the artifact, it only showed the module it was used in, and not the folder it was contained in. We could not find the artifact by id in the quick view search.
It is possible the containing folder tree was deleted, or something else we don't know... either way, we were able to fix it by going into Browse Artifacts, clearing all filters, and then adding a "Used in Module <Module name>" filter. Then we moved the artifacts into the desired folder... Before we did this, we could not even find the affected artifacts by id in quick search. We discovered the issue of the artifacts not being on folders when we noticed team members we expected to be able to edit them could not. The cause was that the team ownership for the affected artifacts was incorrect. Since we wanted to edit the team ownership in bulk by the containing folder, we kind of needed them in a folder. So the solution was found by creating a view in browse artifacts to show all artifacts used in the affected module, hooray! As an additional note... we were baffled that the module showed "690 artifacts" but the folder only contained "670 artifacts". The reason for this was because one artifact was reused 20 times in the module... so the module counted it for each reuse, but the folder only counted the artifact once. |
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.