| | 1 | == Milestone Summary: ClientsPlugin Event Summary == |
| | 2 | |
| | 3 | === Description === |
| | 4 | |
| | 5 | The Milestone Summary will summarise the tickets assigned to future milestones (those with a date set in the future). It will extract "client" blocks from ticket descriptions and will take the estimated hours from the TimingAndEstimationPlugin and combine it into an XML object. |
| | 6 | |
| | 7 | Most actions will require manipulation to turn this XML into something useful. This will typically take the form of an XSLT transform. |
| | 8 | |
| | 9 | |
| | 10 | === Example XML === |
| | 11 | |
| | 12 | {{{ |
| | 13 | #!xml |
| | 14 | <clientsplugin> |
| | 15 | <client> |
| | 16 | <name>Big Corp. Ltd</name> |
| | 17 | <lastupdate>13 Oct 2008</lastupdate> |
| | 18 | </client> |
| | 19 | <milestones> |
| | 20 | <milestone> |
| | 21 | <name>milestone1</name> |
| | 22 | <duetimestamp>1204761600</duetimestamp> |
| | 23 | <due> 6 Mar 2008</due> |
| | 24 | <description><p> |
| | 25 | Something |
| | 26 | </p> |
| | 27 | </description> |
| | 28 | <estimatedhours>No estimate available</estimatedhours> |
| | 29 | </milestone> |
| | 30 | </milestones> |
| | 31 | <summary> |
| | 32 | <ticket> |
| | 33 | <id>1</id> |
| | 34 | <summary>Testing 123</summary> |
| | 35 | <description><p> |
| | 36 | This ticket is a tricky one and as such may be subject to a a few delays. |
| | 37 | </p> |
| | 38 | <p> |
| | 39 | I hope you appreciate the nature of this. |
| | 40 | </p> |
| | 41 | </description> |
| | 42 | <status>accepted</status> |
| | 43 | <milestone>milestone1</milestone> |
| | 44 | <due> 6 Mar 2008</due> |
| | 45 | </ticket> |
| | 46 | </summary> |
| | 47 | </clientsplugin> |
| | 48 | }}} |
