Manuel Vacelet (vaceletm)2018-07-17 11:14Status changed from Ready (stalled) to CanceledCategory set to
Manuel Vacelet (vaceletm)2015-02-09 16:33 I start to understand but I don't think it could be automated (ie. as soon as there is a shared field between a parent and a child then values should be inherited). So a couple of questions: - Should this be mandatory (ie. If Epic is assigned to Team A, then all user stories of this Epic MUST be assigned to Team A) or could this be more relax ? - How would you make the configuration (and in which tracker) Actually this looks very close to "fields dependencies" features, could this be the same requirement but cross-tracker ?
Patricia Carrasco (pcar)2015-02-09 16:24 As a Tuleap User I have created a field called "Assigned Team" in my Epic tracker. In my User Story tracker I create a shared field based on the "Assigned Team" from the Epic tracker. If a user story artifact is created and the parent epic has a value for "Assigned Team", then the user story artifact shall inherit the value from its parent.
Manuel Vacelet (vaceletm)2015-02-09 10:24 Hi Patricia, I've read this artifact a couple of time but I don't get it, I think I'm lacking of context/examples of what you want to do. Could you please to rewrite it more like a story with examples of what the users would like to setup / get done ?