Removing custom attribute impacts on unresolved work items
I just had a quick question to clarify something for me.
I know that custom attributes aren't ever really removed from the database based on these links:
https://jazz.net/forums/viewtopic.php?t=9626
https://www-304.ibm.com/support/docview.wss?uid=swg21453761
What I am wondering is there any impact to work items which aren't yet completed which were using that field? Do we have to wait until those are completed?
We have updated our editors to no longer include the custom attribute but I wasn't sure if I needed to wait to remove it from the work item type.
Thanks.
I know that custom attributes aren't ever really removed from the database based on these links:
https://jazz.net/forums/viewtopic.php?t=9626
https://www-304.ibm.com/support/docview.wss?uid=swg21453761
What I am wondering is there any impact to work items which aren't yet completed which were using that field? Do we have to wait until those are completed?
We have updated our editors to no longer include the custom attribute but I wasn't sure if I needed to wait to remove it from the work item type.
Thanks.
2 answers
I just had a quick question to clarify something for me.
I know that custom attributes aren't ever really removed from the database based on these links:
https://jazz.net/forums/viewtopic.php?t=9626
https://www-304.ibm.com/support/docview.wss?uid=swg21453761
What I am wondering is there any impact to work items which aren't yet completed which were using that field? Do we have to wait until those are completed?
We have updated our editors to no longer include the custom attribute but I wasn't sure if I needed to wait to remove it from the work item type.
Thanks.
Until you remove them from the Work Item Type, these attributes are still used and still created on all new work items where they apply. By taking them out of the Editor Presentation but leaving them on the Work Item Type, you've just made them uneditable (so they will get their default value, if any, and remain that way).
Removing them from the Work Item Type should not create any issues. If you have involved these attributes in any (pre)conditions or operational behaviors, you'll want to undo those (but even that shouldn't cause an issue as the code should be smart enough to not apply these when the involved attributes don't exist on the item). You might be able to create trouble here if the removed attribute was required or used in a custom script without care to its possible removal.
I did a quick test with a simple string attribute added then removed and I was able to process the various work items through their phases without issues.
Thanks Millard. I figured it should be fairly safe to do but this clears it up for me.
Until you remove them from the Work Item Type, these attributes are still used and still created on all new work items where they apply. By taking them out of the Editor Presentation but leaving them on the Work Item Type, you've just made them uneditable (so they will get their default value, if any, and remain that way).
Removing them from the Work Item Type should not create any issues. If you have involved these attributes in any (pre)conditions or operational behaviors, you'll want to undo those (but even that shouldn't cause an issue as the code should be smart enough to not apply these when the involved attributes don't exist on the item). You might be able to create trouble here if the removed attribute was required or used in a custom script without care to its possible removal.
I did a quick test with a simple string attribute added then removed and I was able to process the various work items through their phases without issues.
I just had a quick question to clarify something for me.
I know that custom attributes aren't ever really removed from the database based on these links:
https://jazz.net/forums/viewtopic.php?t=9626
https://www-304.ibm.com/support/docview.wss?uid=swg21453761
What I am wondering is there any impact to work items which aren't yet completed which were using that field? Do we have to wait until those are completed?
We have updated our editors to no longer include the custom attribute but I wasn't sure if I needed to wait to remove it from the work item type.
Thanks.
Until you remove them from the Work Item Type, these attributes are still used and still created on all new work items where they apply. By taking them out of the Editor Presentation but leaving them on the Work Item Type, you've just made them uneditable (so they will get their default value, if any, and remain that way).
Removing them from the Work Item Type should not create any issues. If you have involved these attributes in any (pre)conditions or operational behaviors, you'll want to undo those (but even that shouldn't cause an issue as the code should be smart enough to not apply these when the involved attributes don't exist on the item). You might be able to create trouble here if the removed attribute was required or used in a custom script without care to its possible removal.
I did a quick test with a simple string attribute added then removed and I was able to process the various work items through their phases without issues.