Events API
Introduction
The event API was introduced in Mingle 3.3 and provides programmatic access to Mingle historical data. This API is readonly.
It has always been possible to subscribe to history in Mingle. However, those subscriptions are oriented toward human readability - generally in a feed reader. In comparison, the event API is oriented toward programmatic access. This programmatic orientation provides many benefits and possibilities for clients to integrate with and consume Mingle data. Potential usages of this API include:
- Aggregated feeds between Mingle projects or even other products
- Custom filtered Mingle feeds
- Activity monitoring
- Integrating Mingle with other products
- Custom metrics analysis, such as cycle-time analysis and scope change analysis
Structure of the event API
The event API is an atom feed. As an atom feed, the event API is comprised of a feed root element with the feed attributes described below.
Feed
feed resource xml - attributes
- title: String; The title of this feed.
- id: String; The URL for this feed.
- link: XML Element; There are several links associated with the feed. These provide information about the feed, in particular it provides information which allows you to navigate through the feed.
- updated: Datetime; The time that the last entry on this feed occurred.
- entry: Resource; The feed will contain one or more entry elements which describe the Mingle events in the feed. Details can be found in the Entries section on this page.
The URLs that are contained within the events feed are based on the site URL that was entered during installation. If the URLs are incorrect, see advanced mingle configuration to learn how to change the site URL.
Entries
Entries are the core of the the API. Each entry represents one or more Mingle events. Entries are broadly one of the following: card, page, revision, or feed corrections . Although each type of event differ, all events have some common elements.
entry resource xml - attributes
- id: String; Identifier of this entry.
- title: String; Friendly title for entry.
- updated: Datetime; The time that the last entry on this feed occurred.
- author: Resource; The user who caused this event. Revision events may only contain a name element, if the person who checked in is not associated with a Mingle user. If a Mingle user is known, the following elements may be present: name, email, uri, and mingle:icon.
- link: XML Element; Links associated with the entry. The link contains several attributes about the resource: href (link to resource), rel (definition of the resource), type (type of the resource, e.g., "text/html"), and title.
- category: XML Element; Categories associated with the entry. The category contains term and scheme attributes. Term identifies the types of changes that occurred in this entry, e.g., "property-change". There will be one category for each entry with a term of card, page, revision, or feed-correction. This defines the source of the entry.
- content: XML Element; Details about the changes that occurred in this entry. E.g., what property changed along with the old and new values. Content will contain a changes XML element which contains individual change elements.
Card events
Card events are entries which have a category with a term value of "card"; other categories may also be present. Card events can have the following types of changes.
Mingle 13.1 introduced two new card event types: "copied to" and "copied from". For these events, you will see the URL of the card that was copied in the source project as well as the URL of the new card in the destination project, which was copied from the source project. Read more about copying a card.
| Event | Category | Example |
|---|---|---|
| Create card | card-creation |
<change type="card-creation" > </change> |
| Copy card | card-copied-to |
<change type="card-copied-to" > <source url="http://your.mingle.server:8080/api/v2/projects/one/cards/2.xml"> <destination url="http://your.mingle.server:8080/api/v2/projects/two/cards/3.xml"></destination> </change> |
| Copied card | card-copied-from |
<change type="card-copied-from" > <source url="http://your.mingle.server:8080/api/v2/projects/one/cards/2.xml"> <destination url="http://your.mingle.server:8080/api/v2/projects/two/cards/3.xml"></destination> </change> |
| Delete card | card-deletion |
<change type="card-deletion"> </change> |
| Change name | name-change |
<change type="name-change"> <old_value>Old name</old_value> <new_value>New name</new_value> </change> |
| Change description | description-change |
<change type="description-change"> </change> |
| Change property | property-change |
<change type="property-change">
<property_definition
url="http://your_mingle_server.com/api/v2/projects/your_project/property_definitions/10418.xml">
<name>Priority</name>
<position nil="true"></position>
<data_type>string</data_type>
<is_numeric type="boolean">false</is_numeric>
</property_definition>
<old_value nil="true"></old_value>
<new_value>must</new_value>
</change>
|
| Change card type | card-type-change |
<change type="card-type-change">
<old_value>
<card_type url="http://your_mingle_server.com/api/v2/projects/your_project/card_types/123.xml">
<name>Story</name>
</card_type>
</old_value>
<new_value>
<card_type url="http://your_mingle_server.com/api/v2/projects/your_project/card_types/432.xml">
<name>Iteration</name>
</card_type>
</new_value>
</change>
|
| Add tag to card | tag-addition |
<change type="tag-addition"> <tag>Client X</tag> </change> |
| Remove tag from card | tag-removal |
<change type="tag-removal"> <tag>Needs review</tag> </change> |
| Add attachment to card | attachment-addition |
<change type="attachment-addition">
<attachment>
<url>/attachments/b4a16f3dcbebe1cc631f8c5a08f78394/811/notes.txt</url>
<file_name>notes.txt</file_name>
</attachment>
</change>
|
| Remove attachment from card | attachment-removal |
<change type="attachment-removal">
<attachment>
<url>/attachments/b4a16f3dcbebe1cc631f8c5a08f78394/811/notes.txt</url>
<file_name>notes.txt</file_name>
</attachment>
</change>
|
| Replace attachment on card | attachment-replacement |
<change type="attachment-replacement">
<attachment>
<url>/attachments/b4a16f3dcbebe1cc631f8c5a08f78394/811/notes.txt</url>
<file_name>notes.txt</file_name>
</attachment>
</change>
|
| Comment on a card | comment-addition |
<change type="comment-addition"> <comment>Attached discussion from sales engineers.</comment> </change> |
| System-generated comment added to card. | system-comment-addition |
<change type="system-comment-addition"> <comment> next release changed from release + 1 to release + 8 </comment> </change> |
When a card is deleted, an entry is created for the event. All of the events for the card should remain.
What is a system-generated comment? Occasionally, Mingle will add comments to a card based on system changes. For example, if the formula of a formula property has changed, Mingle will comment on all cards with that property about why the property value has changed.
Page events
Page events are entries which have a category with a term value of "page"; other categories may also be present. Page events can have the following types of changes.
| Event | Category | Example |
|---|---|---|
| Create page | page-creation |
<change type="page-creation" /> |
| Change name | name-change |
<change type="name-change"> <old_value nil="true"></old_value> <new_value>New name</new_value> </change> |
| Wiki content changed | description-change |
<change type="description-change"> </change> |
| Add tag to page | tag-addition |
<change type="tag-addition"> <tag>Client X</tag> </change> |
| Remove tag from page | tag-removal |
<change type="tag-removal"> <tag>Needs review</tag> </change> |
| Add attachment to page | attachment-addition |
<change type="attachment-addition">
<attachment>
<url>/attachments/b4a16f3dcbebe1cc631f8c5a08f78394/811/notes.txt</url>
<file_name>notes.txt</file_name>
</attachment>
</change>
|
| Remove attachment from page | attachment-removal |
<change type="attachment-removal">
<attachment>
<url>/attachments/b4a16f3dcbebe1cc631f8c5a08f78394/811/notes.txt</url>
<file_name>notes.txt</file_name>
</attachment>
</change>
|
| Replace attachment on page | attachment-replacement |
<change type="attachment-replacement">
<attachment>
<url>/attachments/b4a16f3dcbebe1cc631f8c5a08f78394/811/notes.txt</url>
<file_name>notes.txt</file_name>
</attachment>
</change>
|
When a page is deleted, all of the entries for that page are removed.
Plan objective events
Plan objective events are entries that have a category with a term value of “objective”; other categories may also be present. Objective events can have the change types below. See related documentation on our objective API and how to get a list of objective-related events from your plan.
Please note that:
- The plan objective events feed pertains to Mingle Plus users only.
- Plan objective events relate to planned objectives only, that is objectives on your plan timeline. They do not include events related to unplanned objectives, that is objectives in your program backlog.
- Currently, this plan objectives event API does not track:
- Objective status or alerts
- Work-related events (e.g. when work is added or removed from an objective or when a work item’s status has changed)
| Event | Category | Example |
|---|---|---|
| Create objective on plan timeline | objective-planned |
<change type="objective-planned"> </change> |
| Plan objective from backlog onto plan timeline | objective-planned |
<change type="objective-planned"> </change> |
| Change objective name | objective-updated |
<change type="objective-updated">
<old_value>old name</old_value>
<new_value>new name</new_value>
</change>
|
| Change objective start date | objective-updated |
<change type="objective-updated">
<old_value>old start date</old_value>
<new_value>new start date</new_value>
</change>
|
| Change objective end date | objective-updated |
<change type="objective-updated">
<old_value>old end date</old_value>
<new_value>new end date</new_value>
</change>
|
| Delete objective from plan timeline | objective-removed |
<change type="objective-removed"> </change> |
| Remove objective from plan timeline to backlog | objective-removed |
<change type="objective-removed"> </change> |
Revision events
Revision events are entries which have a category with a term value of "revision"; other categories may also be present. Revision events have the following type of change.
| Event | Category | Example |
|---|---|---|
| Revision committed | revision-commit |
<change type="revision-commit">
<changeset>
<user>timmy</user>
<check_in_time type="datetime">2011-01-20T01:17:16Z</check_in_time>
<revision>176254d9317ded4d6a5f5089db1132246f41b9e2</revision>
<message>#119 (Contact API): done.</message>
</changeset>
</change>
|
Feed correction events
Feed correction events are entries which have a category with a term value of "feed-correction"; other categories may also be present. Feed correction events generally represent changes to the structure of your project which affect previous feed entries. For example, previous entries could have shown that cards were tagged with "developer review". If the "developer review" tag is renamed to "need developer help" then the previous entries will change to show that those cards are tagged with "need developer help." Depending on how you are using this API, you may or may not be interested in feed corrections. Feed correction events can have the following types of changes.
| Event | Category | Example |
|---|---|---|
| Rename managed property value | property-change |
<change type="managed-property-value-change"> <property_definition url="http://your_mingle_server.com/api/v2/projects/your_mingle_project/property_definitions/140.xml"/> <old_value>Low</old_value> <new_value>Lowest</new_value> </change> |
| Rename property | property-change |
<change type="property-rename"> <property_definition url="http://your_mingle_project.com/api/v2/projects/your_mingle_project/property_definitions/140.xml"/> <old_value>Status</old_value> <new_value>Story Status</new_value> </change> |
| Delete property | property-deletion |
<change type="property-deletion"> <property_definition url="http://your_mingle_server.com/api/v2/projects/your_mingle_project/property_definitions/169.xml"/> </change> |
| Card type and property disassociated | card-type-change and property-change |
<change type="card-type-and-property-disassociation"> <card_type url="http://your_mingle_server.com/api/v2/projects/your_mingle_project/card_types/25.xml"/> <property_definition url="http://your_mingle_server.com/api/v2/projects/your_mingle_project/property_definitions/133.xml"/> </change> |
| Rename card type | card-type-change |
<change type="card-type-rename"> <card_type url="http://your_mingle_server.com/api/v2/projects/your_mingle_project/card_types/27.xml"/> <old_value>Card</old_value> <new_value>Story</new_value> </change> |
| Delete card type | card-type-deletion |
<change type="card-type-deletion"> <card_type url="http://your_mingle_server.com/api/v2/projects/your_mingle_project/card_types/31.xml"/> </change> |
| Rename tag | tag-change |
<change type="tag-rename"> <old_value>dev</old_value> <new_value>developer</new_value> </change> |
| Change repository configuration | repository-settings-change |
<change type="repository-settings-change"> </change> |
| Delete repository configuration | repository-settings-change |
<change type="repository-settings-change"> </change> |
| Clear revision cache | repository-settings-change |
<change type="repository-settings-change"> </change> |
| Change project numeric precision | project-change |
<change type="numeric-precision-change"> <project url="http://your_mingle_server.com/api/v2/projects/your_mingle_project.xml"/> <old_value>2</old_value> <new_value>1</new_value> </change> |
| Modify project card keywords | project-change |
<change type="card-keywords-change"> <project url="http://your_mingle_server.com/api/v2/projects/your_mingle_project.xml"/> <old_value>card, #</old_value> <new_value>card, #, story, bug</new_value> </change> |
Feed navigation
There are four potential links on an event feed: current, self, next, and previous. The type of link is identified by its "rel" attribute.
- current represents the URL of the most recent events in this feed. The current link is always available and the link URL will not change.
- self represents the URL of the page for the has been requested. The self link is always available.
- next is a link to the next older set of events. The next link is available unless the current set of events are the oldest events in the project.
- previous is a link to the next newer set of events. The previous link is available unless the current set of events are the newest events in the project.
Suppose your project has three pages of events.
The page numbers are not guaranteed to be in any particular order. In this example, page 1 contains the oldest events. However, page 1 is not guaranteed to contain the oldest events. Please do not assume that feed pages follow any particular order. Instead you should rely on the feed links to navigate the feed.
If you do not specify any particular page, you will get the most recent events in the project - represented here by page 3. On page 3, you will have the following links:
<link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml" rel="current"/> <link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml" rel="self"/> <link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml?page=2" rel="next"/>
On page 2, you will have the following links:
<link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml" rel="current"/> <link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml?page=2" rel="self"/> <link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml?page=1" rel="next"/> <link href="http://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml?page=3" rel="previous"/>
Lastly, on page 1, you will have the following links:
<link href="https://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml" rel="current"/> <link href="https://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml?page=1" rel="self"/> <link href="https://your_mingle_server.com/api/v2/projects/your_project/feeds/events.xml?page=2" rel="previous"/>
Using next to go to older history and previous to go to newer history can be confusing at first. Shouldn't next be used to go to newer events (the next things that happened) and previous to go to older events (the previous things that happened)? Keep in mind, that these links are based on the atom standard which was created largely with blog entries in mind. Think of next/previous in terms of navigating the feed, not in terms of the next/previous things that have happened.
You always start at the most recent set of events.
Then you follow the next link to see the next oldest set of events.
If you decide you need to go back to more recent events, you use the previous link to look at newer events. These are "previous", because you have seen these pages previously when you navigated the feed with the next link.
Get a list of events from your project
You can list the events that happened in your project.
Reference
Request Method: GET
URL: /api/v2/projects/project_identifier/feeds/events.xml
Parameters: NA
Example
GET
http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/feeds/events.xml
Explanation
The above is an example of a GET to retrieve the most recent events in a project with identifier "test_project". The request is made with the authorization credentials of yourname/password.
Result
If you were authorized to perform the operation, and the resource was available, you should get an xml document that looks something like the following.
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:mingle="http://www.thoughtworks-studios.com/ns/mingle">
<title>Mingle Events: agile</title>
<id>http://your.mingle.server:8080/api/v2/projects/test_project/feeds/events.xml</id>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/feeds/events.xml" rel="current"/>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/feeds/events.xml?page=5" rel="self"/>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/feeds/events.xml?page=4" rel="next"/>
<updated>2011-01-20T01:23:05Z</updated>
<entry>
<id>http://your.mingle.server:8080/projects/test_project/events/index/443</id>
<title>Story #120 Delete email created</title>
<updated>2011-01-20T01:23:05Z</updated>
<author>
<name>bob</name>
<email>bob@your_mingle_server.com</email>
<uri>http://your.mingle.server:8080/api/v2/users/1.xml</uri>
</author>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/cards/120.xml"
rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="application/vnd.mingle+xml" title="Story #120"/>
<link href="http://your.mingle.server:8080/projects/test_project/cards/120"
rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="text/html" title="Story #120"/>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/cards/120.xml?version=1"
rel="http://www.thoughtworks-studios.com/ns/mingle#version" type="application/vnd.mingle+xml" title="Story #120 (v1)"/>
<link href="http://your.mingle.server:8080/projects/test_project/cards/120?version=1"
rel="http://www.thoughtworks-studios.com/ns/mingle#version" type="text/html" title="Story #120 (v1)"/>
<category term="card" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="card-creation" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="card-type-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="description-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="name-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="property-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<content type="application/vnd.mingle+xml">
<changes xmlns="http://www.thoughtworks-studios.com/ns/mingle">
<change type="card-creation"/>
<change type="card-type-change">
<old_value nil="true"></old_value>
<new_value>
<card_type url="http://your.mingle.server:8080/api/v2/projects/test_project/card_types/24.xml">
<name>Story</name>
</card_type>
</new_value>
</change>
<change type="description-change">
</change>
<change type="name-change">
<old_value nil="true"></old_value>
<new_value>Delete email</new_value>
</change>
<change type="property-change">
<property_definition url="http://your.mingle.server:8080/api/v2/projects/test_project/property_definitions/154.xml">
<name>Added to Scope in Iteration</name>
<position nil="true"></position>
<data_type>card</data_type>
<is_numeric type="boolean">false</is_numeric>
</property_definition>
<old_value nil="true"></old_value>
<new_value>
<card url="http://your.mingle.server:8080/api/v2/projects/test_project/cards/37.xml">
<number type="integer">37</number>
</card>
</new_value>
</change>
<change type="property-change">
<property_definition url="http://your.mingle.server:8080/api/v2/projects/test_project/property_definitions/114.xml">
<name>Story Status</name>
<position nil="true"></position>
<data_type>string</data_type>
<is_numeric type="boolean">false</is_numeric>
</property_definition>
<old_value nil="true"></old_value>
<new_value>New</new_value>
</change>
</changes>
</content>
</entry>
...
<entry>
<id>http://your.mingle.server:8080/projects/test_project/events/index/432</id>
<title>Story #113 Add calendar event via email deleted</title>
<updated>2011-01-20T12:32:49Z</updated>
<author>
<name>sally</name>
<email>sally@your_mingle_server.com</email>
<uri>http://your.mingle.server:8080/api/v2/users/2.xml</uri>
</author>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/cards/113.xml"
rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="application/vnd.mingle+xml" title="Defect #113"/>
<link href="http://your.mingle.server:8080/projects/test_project/cards/113"
rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="text/html" title="Defect #113"/>
<link href="http://your.mingle.server:8080/api/v2/projects/test_project/cards/113.xml?version=4"
rel="http://www.thoughtworks-studios.com/ns/mingle#version" type="application/vnd.mingle+xml" title="Defect #113 (v4)"/>
<link href="http://your.mingle.server:8080/projects/test_project/cards/113?version=4"
rel="http://www.thoughtworks-studios.com/ns/mingle#version" type="text/html" title="Defect #113 (v4)"/>
<category term="card" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="card-deletion" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<content type="application/vnd.mingle+xml">
<changes xmlns="http://www.thoughtworks-studios.com/ns/mingle">
<change type="card-deletion">
</change>
</changes>
</content>
</entry>
</feed>
Get a list of objective-related events from your plan
You can get list of objective-related events that happened in your plan.
Reference
Request Method: GET URL: /api/v2/programs/program_identifier/plan/feeds/events.xml Parameters: NA
Example
GET
http://yourname:password@your.mingle.server:8080/api/v2/programs/program_identifier/plan/feeds/events.xml
Explanation
The above is an example of a GET to retrieve the most recent events in a plan from the program with identifier "test_program". The request is made with the authorization credentials of yourname/password.
Result
If you were authorized to perform the operation, and the resource was available, you should get an xml document that looks something like the following. The URL of the objective to which the event occurred is also provided.
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:mingle="http://www.thoughtworks-studios.com/ns/mingle">
<title>Mingle Plan Events for Program: Events Api</title>
<id>http://your.mingle.server:8080/api/v2/program/events_api/plan/feeds/events.xml</id>
<link href="http://your.mingle.server:8080/api/v2/program/events_api/plan/feeds/events.xml" rel="current"/>
<link href="http://your.mingle.server:8080/api/v2/program/events_api/plan/feeds/events.xml" rel="self"/>
<updated>2013-02-12T01:30:32Z</updated>
<entry>
<id>http://your.mingle.server:8080/events/index/2500143</id>
<title>Objective removed</title>
<updated>2013-02-12T01:30:32Z</updated>
<author>
<name>user</name>
<email>user@thoughtworks.com</email>
<url>http://your.mingle.server:8080/api/v2/users/14281.xml</url>
</author>
<link href="http://your.mingle.server:8080/api/v2/programs/events_api/plan/objectives/first.xml" rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="application/vnd.mingle+xml" title="Objective: first"/>
<category term="objective" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="objective-removed" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<content type="application/vnd.mingle+xml">
<changes xmlns="http://www.thoughtworks-studios.com/ns/mingle">
<change type="objective-removed">
</change>
</changes>
</content>
</entry>
<entry>
<id>http://your.mingle.server:8080/events/index/2500142</id>
<title>Objective updated</title>
<updated>2013-02-12T01:30:26Z</updated>
<author>
<name>user</name>
<email>user@thoughtworks.com</email>
<url>http://your.mingle.server:8080/api/v2/users/14281.xml</url>
</author>
<link href="http://your.mingle.server:8080/api/v2/programs/events_api/plan/objectives/second.xml" rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="application/vnd.mingle+xml" title="Objective: second"/>
<category term="objective" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="end_at-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<content type="application/vnd.mingle+xml">
<changes xmlns="http://www.thoughtworks-studios.com/ns/mingle">
<change type="end_at-change">
<old_value>2013-05-22</old_value>
<new_value>2013-06-12</new_value>
</change>
</changes>
</content>
</entry>
<entry>
<id>http://your.mingle.server:8080/events/index/2500141</id>
<title>Objective planned</title>
<updated>2013-02-12T01:30:24Z</updated>
<author>
<name>user</name>
<email>user@thoughtworks.com</email>
<url>http://your.mingle.server:8080/api/v2/users/14281.xml</url>
</author>
<link href="http://your.mingle.server:8080/api/v2/programs/events_api/plan/objectives/third.xml" rel="http://www.thoughtworks-studios.com/ns/mingle#event-source" type="application/vnd.mingle+xml" title="Objective: third"/>
<category term="objective" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="objective-planned" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="end_at-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="name-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<category term="start_at-change" scheme="http://www.thoughtworks-studios.com/ns/mingle#categories"/>
<content type="application/vnd.mingle+xml">
<changes xmlns="http://www.thoughtworks-studios.com/ns/mingle">
<change type="objective-planned"/>
<change type="end_at-change">
<old_value nil="true"></old_value>
<new_value>2013-07-31</new_value>
</change>
<change type="name-change">
<old_value nil="true"></old_value>
<new_value>third</new_value>
</change>
<change type="start_at-change">
<old_value nil="true"></old_value>
<new_value>2013-07-01</new_value>
</change>
</changes>
</content>
</entry>
</feed>