Knowledge Base

 View Only

Adding a Field to an Existing Item

By Knowledge Base posted 01-07-2019 17:29

  

The results of adding a field to an Item Type will not cause any adverse effects to the existing items. It will, instead, add a blank field to the Item Type.

Creating the Field
To add a field to an Item Type you must be a Jama Admin. Select the Item Types menu, then decide which Item Type will get a new field. Select Config in the same row as the desired item.



A window will appear to the right showing all available fields in that Item Type as well as options for editing the list of fields in the upper right. The icons are (from left to right) edit, move up, move down, delete and add a field.




Add Field will open a dialog box where you can specify the details of the field.

 

First, decide if this will be a Predefined Field or a Custom Field. A Field Label is required, as this is the field name that users will see. A Unique Field Name will auto-populate in an editable field when a Field Label is chosen. Once the field has been created and saved, the Unique Field Name will no longer be editable in either the UI or with the API.

For additional information on adding fields, you can check out the Jama User Guide's entries on configuring an item type and modifying fields.


Adding New Fields to the Review Center
When you have finished creating the field, you must make sure it is viewable in the Review Center by going to Admin > Item Types, selecting Configure View on the item in question, and using the drop-down menu to select Review Center Single Item View and Review Center Reading View. The Review Center Reading View is the default view that displays multiple items per page, while the Review Center Single Item View displays just one item in detail.



When you move the new field to the Visible Columns you can go back to your review and see your newly-created fields.

The new field will appear in the Review Center without a new revision. When you fill the new fields in, you will have to publish a new revision in order to see the data. Publishing a new revision will let approvers and reviewers know that there is new information to review.
14 comments
125 views

Permalink

Comments

swoo Woo
09-21-2015 17:09

Hi Senthil, the required field will not be checked until you do a single item edit and save. Then mandatory fields will be required to have values before you can commit the changes to the database. In Excel RoundTrip  you also need to assign a default value for mandatory fields. Does this answer your question? swoo

Knowledge Base
09-21-2015 10:54

Hi Matt Thanks for this article.

Can you please let me know, what will be the impact on existing data, if we adding a new required columns to an existing item?


Thanks and Regards,

Senthil Gopi

Knowledge Base
06-18-2015 23:56

Hey, Bob. Thanks for the question. Creating and deleting a field won't have any impact of the functionality of the item itself but you will lose the data associated with that field.

Here is some good reading about keeping data regardless if you delete or modify a field.

Hopefully I answered your question. 

Bob Dilly
06-18-2015 15:14

I've never tried this, I've wondered how (well) Jama handles the removal of a field.  I considered trying out an idea for a field, but was a bit concerned about pulling it back out...   ;-)

(If you add a field to an item, it's global, right?  So you can't just try an idea out in a single project.)

Bob

Kristina King
06-18-2015 12:40

Thanks, Chris, for getting back to us. Archiving a test plan means any of those Test Runs in the plan stop affecting the Test Case Status. So that would make me think the same Test Case existed in an active Test Plan as "Not Scheduled", but due to how the status is calculated that didn't reflect until the Plan w/the case in an executed status was archived.

Chris Jenkins
06-18-2015 05:20

Hi All,

Thanks for the responses. On closer inspection, this issue was not system wide. Some test cases updated, whilst others did not.

Consequently i may have found the real reason for my issue. It actually has nothing to do with adding new fields to the test cases. At some stage the system tester at my company archived a suite of test cases. When this happens a message appears saying the system is refreshing test cycles. Therefore those test cases in those newly archived test plans. So my theory is that the archiving process updated those test cycles which may have changed the status. However, again I am seeing mixed results.

Either way, I believe the original issue is not an issue any longer and can be closed.

Kristina King
06-16-2015 15:21

@Chris, I think this is a good point to bring up. However, like @swoo my experience is not mirroring yours. Even if I add a new value to this field, the Test Case Status is remaining the same. The only way I can reset the status is by using the Make Test Runs Current option. Chris, if I'm missing a step I'd like to know so that we can pin this down and log something, if necessary. Accidentally changing all run statues to "Not Scheduled" is not a surprise anyone wants to run into!

swoo Woo
06-16-2015 13:16

Hi Chris,

Thanks for your note.

I was not able to reproduce the phenomenon that you observed. On the hosted version of 2015.1. Perhaps I did not replicated your steps correctly. This is what I did 

I added a new field "swoo test 1" to the test case.

I actually don't see any changes in the version history or item activity stream. I also see the test run status not being modified.

By going to the test run, when I open a test case, I see the test step status and test case status retained.

If you still observe your issue, perhaps Jama can help you more directly. Good luck.

swoo


Chris Jenkins
06-16-2015 04:18

Just a note on adding fields to test cases and an unexepcted side effect I encountrered:

I added a new field to the test case item type, the result being that all my test cases were "modfied" with this new field. The result however was that the test case status was also updated to "Not Scheduled" and subsequently when you do that, any coverage reports relying on the status field will no longer show the previous test run result (i.e., Pass, Fail, Blocked). Obviously since the test case is modified it will naturally not have been run, but since I was not modifying test steps I still wanted to rely on the test case status of my last test run. This isn't necessarily unusual behaviour for Jama but just a word of caution for those modifying their test cases.

swoo Woo
06-15-2015 20:29

Matt, I have confirmed the fix. Good job. We are all on the same team to make Jama more useful, usable, and desirable. Some of us get a paid check directly from Jama and some indirectly :-) Have a good evening. swoo

Knowledge Base
06-15-2015 20:19

Hi Swoo, The images should be fixed now. Thanks for bringing this to our attention! -Matt

swoo Woo
06-15-2015 02:42

Hi Matt, It's my pleasure. See the screenshot for why the images are not displaying. When I click on the blank, it's asking me to log into this Jama server: https://support.jamaland.com/login.req?failed=true Have a good evening. swoo

Knowledge Base
06-15-2015 02:39

Thanks, Swoo!

I'll check with our admin, make sure the images are posted correctly.

swoo Woo
06-15-2015 02:37

Hi Matt, thanks for this clear and concise instructions. You might consider explaining that a database rather than a project administrator can do this. You might have to check the permission of your images. I could not see them on my iPhone, iPad, nor my PC. Have a good day. Keep these tips coming. Keep up the good job. swoo