Text Item Type - New items don't reflect key change

Hello,
We currently use Jama 8.14.1. When we create a Set of Text items, the ID for that item type defaults to TXT-xxx (xxx= a numerical ID). We then right click on that Set of Text and choose Change Set Key, and rename it to something (example TXT_Test) we've found that after adding new texts to that set, the default ID stays TXT-xxx, and not TXT_Test. Alternatively we've also created a set of Text items, left the ID default, added a Text item to that set, and then changed the set key. The item that was already created changes to the new ID, but then the subsequent items that are created do not change.

I believe once we change that key, subsequent items that are created should inherit that custom key. Is there a setting that I should check under our Admin page to ensure that something is not checked or missing? Just as a sanity check, we did create a set of Requirements, changed the set key and the new items did inherit the new key, so it just seems to be a problem with our set of Texts. 

Steps to re-produce:
Create a Set of Texts
Right click set > choose Change Set Key
Rename to new Set Key
Add Text item type to your Set of Texts
ID will reflect system default instead of the custom Set Key

Comments

  • DMedhaug
    DMedhaug Jama Staff, Data Exchange, Automotive Solution, Medical Devices & Life Sciences Solution, Robotics Solution, Airborne Systems, Jama Connect Interchange™ (JCI), Jama Validation Kit (JVK) + Functional Safety Kit (FSK) Posts: 11
    edited October 2017
    Hello Josh,
    First of all, I want to apologize for the late response. Somehow this post slipped through the cracks. To answer your question this behavior has been present for a very long time, it can be reproduced as far back as 2015.1. There was a bug logged for this but it was dropped because it is working as designed. It is something that will be revisited when we look at categorization in the future.

    ------------------------------
    Dana Medhaug
    Technical Support Engineer
    Jama Software
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 09-28-2017 11:08
    From: Josh Romine
    Subject: Text Item Type - New items don't reflect key change

    Hello,
    We currently use Jama 8.14.1. When we create a Set of Text items, the ID for that item type defaults to TXT-xxx (xxx= a numerical ID). We then right click on that Set of Text and choose Change Set Key, and rename it to something (example TXT_Test) we've found that after adding new texts to that set, the default ID stays TXT-xxx, and not TXT_Test. Alternatively we've also created a set of Text items, left the ID default, added a Text item to that set, and then changed the set key. The item that was already created changes to the new ID, but then the subsequent items that are created do not change.

    I believe once we change that key, subsequent items that are created should inherit that custom key. Is there a setting that I should check under our Admin page to ensure that something is not checked or missing? Just as a sanity check, we did create a set of Requirements, changed the set key and the new items did inherit the new key, so it just seems to be a problem with our set of Texts.

    Steps to re-produce:
    Create a Set of Texts
    Right click set > choose Change Set Key
    Rename to new Set Key
    Add Text item type to your Set of Texts
    ID will reflect system default instead of the custom Set Key

    ------------------------------
    Josh Romine
    Plexus
    Neenah WI
    ------------------------------
    Dana Medhaug
    Technical Support Engineer
    Jama Software
    Portland Oregon
  • Lita Gribben
    Lita Gribben Member, Data Exchange, Jama Connect Interchange™ (JCI) Posts: 90
    edited October 2023

    Was this ever added back to the defect/bug list? The last response is from 2017, and I just ran into this scenario today. 

    We are self hosted on 8.79.1, and I had assumed that Text items always default to TXT as the set key and that it couldn't be changed. But come to find out that we can change it, but the change doesn't affect new items created in the set. Regenerating the IDs does force the IDs to change though, but as mentioned above, any items created after that process have the default TXT set key. 

    I am just going to tell our users we cannot customize that set key, but considering Project admins can change it and regenerate IDs, this is something that could cause issues later on.

    ------------------------------
    Lita Gribben
    Blue Origin
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 10-05-2017 09:57
    From: Dana Medhaug
    Subject: Text Item Type - New items don't reflect key change

    Josh,
    First of all, I want to apologize for the late response. Somehow this post slipped through the cracks. To answer your question this behavior has been present for a very long time, it can be reproduced as far back as 2015.1. There was a bug logged for this but it was dropped because it is working as designed. It is something that will be revisited when we look at categorization in the future.

    ------------------------------
    Dana Medhaug
    Technical Support Engineer
    Jama Software
    ------------------------------

    Original Message:
    Sent: 09-28-2017 11:08
    From: Josh Romine
    Subject: Text Item Type - New items don't reflect key change

    Hello,
    We currently use Jama 8.14.1. When we create a Set of Text items, the ID for that item type defaults to TXT-xxx (xxx= a numerical ID). We then right click on that Set of Text and choose Change Set Key, and rename it to something (example TXT_Test) we've found that after adding new texts to that set, the default ID stays and not TXT_Test. we've also created a set of Text items, left the ID default, added a Text item to that set, and then changed the set key. The item that was already created changes to the new ID, but then the subsequent items that are created do not change.

    I believe once we change that key, subsequent items that are created should inherit that custom key. Is there a setting that I should check under our Admin page to ensure that something is not checked or missing? Just as a sanity check, we did create a set of Requirements, changed the set key and the new items did inherit the new key, so it just seems to be a problem with our set of Texts.

    Steps to :
    Create a Set of Texts
    set > choose Change Set Key
    Rename to new Set Key
    Add Text item type to your Set of Texts
    will reflect system default instead of the custom Set Key

    ------------------------------
    Josh Romine
    Plexus
    Neenah WI
    ------------------------------