Can you clarify how tagging works in modules?
When I create a tag for an artifact within a module, I cannot see if it I open the base artifact outside of the module. Is there a way to copy these tags? Or, can you help me with a work-around for this scenario:
I have a document with several individual requirements. I'm importing this document into a module and using text delimiters to create individual artifacts for all of the specific requirements. My team then needs to review the module (or all the requirements) to tag the ones that need to be tested.I want to create a collection (or a module) of all the requirements that need testing so I can link it to a development plan and test plan to generate stories and test cases. I know that I can just import the requirements and tag at that level, but I'm using the module because it's much easier for the team to complete their reviews.
Several of the artifacts are tagged for testing. However, I cannot filter by that tag to find them to add them to the collection. I've tried copying artifacts and copying the entire module, but neither copy retains the tags. I've even gone to the base artifacts to see if the tags are there, but they are not even though the base artifacts that are created in a separate folder have the same IDs as the artifacts within the module. As a last resort, I opened the module, opened an artifact tagged for the test collection, and wanted to either use the option at the top to add it to a collection or move it to another folder so I could sort that way. Unfortunately, those two options are not available when you open the artifact from within the module. I can copy the artifact and store the copy in the folder, but then I have three versions of the same artifact - the base, the one in the module, and the copy - and that doesn't seem like a good solution.
So, short of making my team go through the artifacts one by one to tag them, is there an easy way to accomplish the review and the creating of my test collection?
My solution right now is to record the IDs of the artifacts tagged for testing and use that to find the artifacts and add them to the test collection, but will be very tedious.
I'm open to any suggestions. Thanks!
|
Accepted answer
2 other answers
As you have already found out, the module artifact and the base artifact has their own tags, and you cannot put a module artifact into a collection. So you should stick to the base artifacts whenever possible. For this purpose, you should be aware of the situations where you have access to a base artifact. I would suggest you always use "search by id" to access to the base artifact and add tags to it.
Depending on how you work on the module artifacts, here is what you can do. 1. Suppose you work in a module view and identify an artifact that needs tagging. Hover over the artifact Id to check the details of the artifact - existing tags (of the base artifact) should appear under the "Location" section. If no tags are defined yet, put the artifact Id in the top right search box and open the artifact in the search result in a new browser window and add tags there. Note: do not add the "tags" column in the module view as it shows the tags of the module artifacts and will make you confused. 2. If you always open the module artifact itself, click on the second icon in the top right icon list, which reads "include links, tags and comments from the base artifacts" and check whether the base artifact has any desired tags. If not, follow the same process of searching by Id and adding tags. Once you add tags to the base artifacts, you can filter by tags when adding artifacts to a collection. |
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.