#618: Parent/child updates for QCT <select /> --------------------------+------------------------------- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: Component: ui design | Version: 0.6.0 Resolution: | Keywords: qct ticket fields --------------------------+------------------------------- Changes (by olemis):
* keywords: => qct ticket fields * owner: => nobody * component: => ui design Old description: > There's something wrong with quick ticket user experience once multi- > product support is installed in place . > > The fact is that QCT will display field values for the current > (product/global) context . If a ticket is created for a different product > the set of components / versions / milestones / ... will not be the same > . This might lead to one of (at least) three cases . > > 1. missing value UI due to resource name mismatch > 2. wrong/invalid field value reflected in UI , in cases where field > value is > shown anyway even on mismatch > 3. Trac errors e.g. resource not found New description: There's something wrong with quick ticket user experience once multi- product support is installed in place . The fact is that QCT will display field values for the current (product/global) context . If a ticket is created for a different product the set of components / versions / milestones / ... will not be the same . This might lead to one of (at least) three cases . 1. missing value UI due to resource name mismatch 2. wrong/invalid field value reflected in UI , in cases where field value is shown anyway even on mismatch 3. Trac errors e.g. resource not found -- -- Ticket URL: <https://issues.apache.org/bloodhound/ticket/618#comment:1> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound issue tracker