Hi Terry,
Yes, this is live for all of our subscriptions and should be working as you
described. If your template does not contain "DisplayColor", it should use
the DisplayColor of the parent. (For any other readers, do be aware that
DisplayColor is automatically added to your template and must be manually
removed.)
Can you share how you are creating stories that are not inheriting the
parent color? (In a Feature editor? Create or Create with Details)
-Nate
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
Original Message:
Sent: 7/8/2025 10:08:00 AM
From: Terry Ginzburg
Subject: RE: Creating Children Inherits Parent Color
Hi Nate,
Is this released yet? I have a template that only applies to the Description field on new User Stories, it does not affect the DisplayColor attribute, but the User Story is not inheriting the Parent Feature's DisplayColor. I would expect it to respect a template that provides a specific DisplayColor, but not be affected by templates that only apply to other fields. Is that not how this is working?
------------------------------
Terry Ginzburg
------------------------------
Original Message:
Sent: Jul 03, 2025 01:48 PM
From: Nate Bever
Subject: Creating Children Inherits Parent Color
Hello everyone,
A small but useful "quality of life" feature will be released Monday, July 7th, where child items will inherit their parent's DIsplayColor upon creation. Many of you (like us) use DisplayColor to make it simple to see which work items are associated with which Feature or Portfolio Item hierarchy. In the past, that meant manually changing the color of these items right after their creation and periodically checking that no new items were created with different colors.
Now the default color for a child item will be the same as its parent, except where templates are involved. Template settings will always overrule this default behavior.
Thank you,
-Rally Product Management