Individual Artifacts not Automatically Generated in Base Artifacts folder?
Good day,
I know when I create a Module that all of the individual artifacts are placed in the Base Artifacts folder or a subfolder of Base Artifacts.
However, when I create or import a requirement that is just part of the folder, it does not get a "copy" in the Base Artifacts folder nor a subfolder of Base Artifacts.
Why is this? It could be related to this article: https://jazz.net/forum/questions/264460/question-about-purpose-of-base-artifacts: https://jazz.net/forum/questions/264460/question-about-purpose-of-base-artifacts
Sincerely,
Mary
|
Accepted answer
Hi Mary,
Only artifacts that are added to the Module will be added to the 'base artifacts' folder for that Module. If you add non-module artifacts to the same folder in which the Module resides (which is what I think you're saying), they won't also be reflected in base artifacts unless you use "insert existing artifact" and add them to the Module.
And you're correct, base artifacts only come into play with modules. If you use non-module artifacts too, those are handled differently. For example, if you delete a non-module artifact, it's permanently deleted. If you "remove" an artifact from a Module, and do not also check the box to permanently delete it, then the base artifact will still be in the base artifacts folder.
I recently had a situation where someone inadvertently deleted a base artifacts folder. While it didn't impact the associated module, since the artifacts were still in the database, there wasn't an easy way to "recreate" the base artifacts folder. I did find there's a utility you can use with the support team, but in my instance the module was tiny so it wasn't worth the effort. I cycled through and removed the Delete Folder permission for all Roles in all projects afterwards, to ensure that didn't happen again.
Hope this helps,
Carol
Mary Miller selected this answer as the correct answer
|
3 other answers
I find people get really wrapped around the axle over the whole 'base' artefact thing, especially if they have come from a DOORS Classic background.
The simple fact is that the artefacts you see in the folders are the actual requirements - they are not copies of the things you see in Modules, they ARE the things in the Modules. This is completely different to DOORS Classic where the requirements objects are created and live inside one and only one Module.
In DOORS Next Gen, a Module is is really just a 'Collection with a Context' - it's a holder for the requirements artefacts that you see in the folders, and it remembers the order and hierarchy in which you put them. You can even add the same requirement artefact multiple times into the same Module and it'll remember you put it in there each time.
The Base artefact folder concept was added to DOORS Next for those people who came from DOORS Classic and didn't get how Modules have changed and, IMHO, it's made it more difficult for people to understand. Basically when you add a requirement to a Module in DOORS Next, what is actually happening is:
- the requirement artefact is created in the repository and is put into a folder
- the artefact is then inserted into the Module in the place where you indicated
If you get your team to alter their mindset to think of the requirements artefacts being stand alone objects that live in the repository as a whole, organised by folders, and that they may also be inserted into and arranged in one or more Modules, then the whole idea of Modules gets simpler.
Modules then become the way you organise your requirements if you want something that looks like a document. If you only need a list or spreadsheet view of them, you can just use the folder hierarchy, or a normal Collection - Modules are overkill and actually harder to use if you just need a list you can query and sort.
|
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.