Changes between Version 2 and Version 3 of Ticket #7767


Ignore:
Timestamp:
Jan 20, 2011, 11:38:28 PM (13 years ago)
Author:
Ryan J Ollos
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #7767 – Description

    v2 v3  
    1 Currently it seems TracTicketChainedFields only supports one field at the top of the chain. It would be nice if we could have multiple independent chains. Perhaps there is a way to hack it, but the following doesn't work today even though it's valid json. Only the second set of chained fields is considered
     1Currently it seems !TracTicketChainedFields only supports one field at the top of the chain. It would be nice if we could have multiple independent chains. Perhaps there is a way to hack it, but the following doesn't work today even though it's valid json. Only the second set of chained fields is considered
    22
    33{{{