Help documentation

Card resources are located by issuing a GET request to the server with the card's number as a parameter.

Before you manipulate cards using the API, we recommend that you familiarize yourself with some key concepts related to cards like card types and card properties.

The following examples use curl. If you want to interact with the Mingle API using javascript, ThoughtWorks Studios maintains a sample app here.

The structure of a card will completely depend on your project and how you have configured your properties. That said, all cards in all projects in Mingle have a few default attributes. In addition to these you will have an attribute for each property definition that you define for your project.

The default attributes are described below, along with their data type. Also included with each attribute is whether you are allowed to update the value. System generated fields like id, number, created_on etc. are provided only as information about the card and cannot be updated through the API.

card resource xml - attributes

• name: String.
• description: String; the HTML that Mingle renders for the card description.
• card type: Resource; name of the card type for each card; string.
• id: Integer; read only, system assigned unique identifier for a card.
• number: Integer; read only, unique identifier of a card within a project - Use this for both GET and PUT.
• project: Resource; name and identifier of a project a card belongs to; both strings.
• version: Integer; read only, current card version. You can specify the version to get history version of the card.
• project_card_rank: Integer; read only, the rank of the card in a project.
• created_on: Datetime; read only, date and time of creating card.
• modified_on: Datetime; read only, date and time of last modification.
• modified_by: Resource; name and login id of user who is the last to modify the card; both String, read only.
• created_by: Resource; name and login id of user who created the card; both String, read only.
• properties: Array; property: Resource; name and a current value for each card property defined for current card's card type are listed; Data type will depend on the property while property name is always String. The property also includes attributes about the property type_description and whether or not it is hidden.
• tags: String; comma-delimited list of tags associated with the card.
• rendered_description: Resource; Link to rendered card description as HTML.

Reference

    Request Method: GET
    URL: /api/v2/projects/project_identifier/cards/card_number.xml
    Parameters: NA
      

Example

    GET

    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards/42.xml
      

Explanation

The above is an example of a GET request to a Mingle server running at your.mingle.server, port 8080. The request is made with the authorization credentials of yourname/password. The URL of api/v2/projects/test_project/cards/42.xml represents the card resource for the card numbered 42 in project with identifier test_project.

Result

<?xml version="1.0" encoding="UTF-8"?>
<card>
  <name>As an API user, I would like to lookup a card in Mingle, given that I know the card number.</name>
  <description>
  </description>
  <card_type>
    <name>Story</name>
  </card_type>
  <id type="integer">409</id>
  <number type="integer">42</number>
  <project url="http://localhost:8080/api/v2/projects/test_project.xml">
    <name>test project</name>
    <identifier>test_project</identifier>
  </project>
  <version type="integer">1</version>
  <project_card_rank type="integer">1</project_card_rank>
  <created_on type="datetime">2009-10-14T09:14:54Z</created_on>
  <modified_on type="datetime">2009-10-14T09:14:54Z</modified_on>
  <modified_by url="http://localhost:8080/api/v2/users/1.xml">
    <name>anne</name>
    <login>anne</login>
  </modified_by>
  <created_by url="http://localhost:8080/api/v2/users/2.xml">
    <name>jane</name>
    <login>jane</login>
  </created_by>
  <properties type="array">
    <property type_description="Managed text list" hidden="false">
      <name>Status</name>
      <value>Closed</value>
    </property>
    <property type_description="Managed number list" hidden="false">
      <name>Estimate</name>
      <value>4</value>
    </property>
    <property type_description="Managed text list" hidden="false">
      <name>Priority</name>
      <value nil="true"/>
    </property>
  </properties>
</card>
        

You can update different attributes on a card such as card name, card type or properties that are available on card via card resource API.

How to update different kinds of properties

• Managed/Unmanaged text: Use the text value of the value you would like to update the value to
• Managed/Unmanaged numbers: Use the numeric value you would like to set the property to
• Date: Use the date string in the project date format
• Team member: Use the id of the user you would like to update the value to. You can obtain the user id by looking up the user using the API.
• Card: Use the card number of the card you would like to update the value to.

Reference

    Request Method: PUT
    URL: /api/v2/projects/project_identifier/cards/card_number.xml
    Parameters: all card attributes that can be updated

    card[name] : The card name
    card[card_type_name] : The name of the card type
    card[properties][][name] : The name of a property you want to set
    card[properties][][value] : The value of the property named above
      

Example

    PUT
      
    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards/42.xml
      
    card[name]=new name
    card[card_type_name]=story
    card[properties][][name]=status
    card[properties][][value]=open
      

Explanation

The above is an example of a PUT request to a Mingle server running at your.mingle.server, port 8080. The request is made with the authorization credentials of yourname/password. The URL of api/v2/projects/test_project/cards/42.xml represents the card resource for the card with a card number of 42 in project with identifier test_project. Please note that this is not the card id. The value of the name and card_type_name attributes will get changed to the newly specified values of "new name" and "story" and the a card property called "status" will get a new value of "open".

Result

If you were authorized to perform the operation, and the operation succeeded, you will be returned a location attribute in the http header of the response, which is a URL to the updated resource.

Reference

    Request Method: POST
    URL: /api/v2/projects/project_identifier/cards.xml
    Parameters: all card attributes that can be updated
      

Example

    POST

    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards.xml

    card[name]=testing card creation
    card[card_type_name]=story
      

Explanation

The above is an example of a POST request to a Mingle server running at your.mingle.server, port 8080. The request is made with the authorization credentials of yourname/password. Upon execution of this request, the post parameters will be used to create a card on the project with identifier "test_project". The value of the name and card_type_name attributes will be set to the specified values of "testing card creation" and "story".

Result

If you were authorized to perform the operation, and the operation succeeded, you will be returned a location attribute in the http header of the response, which is a url from which you can get the card resource that was created.

Reference

    Request Method: GET
    URL: /api/v2/projects/project_identifier/cards.xml
    Parameters: 

    view : The name of a saved view, whose cards are to be returned back
    page : A specific set of 25 results, if the list contains more than 25 results. The first 25 results are page 1. The next 25 are page 2, and so on. Requesting the contents of a page of data that is past the last valid page, returns the data on the last valid page and not an empty array.
    filters[] : Each value for this parameter represents a filter applied to the list of cards. You can also use a standard filter or a MQL filter with this parameter.
    sort : The property whose value will be used to sort the cards returned
    order : ASC/DESC, whether the cards will be returned in Ascending or Descending order of the sort property 
    tagged_with : A comma separated list of tags that will be used to further filter the list of cards in addition to the filters
      

Example 1 - Using a standard filter

    GET

    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards.xml

    filters[]=[Type][is][story]
    filters[]=[Status][is not][accepted]
    sort=status
    order=ASC
      

Explanation

The above is an example of a GET request to retrieve a filtered set of cards from the project with identifier "test_project". The cards returned will all be of type "Story" and will have a status other than "accepted". They will be returned in the ascending order of their status values, as configured on the property management page in Mingle.

Result

If you were authorized to perform the operation, and the operation succeeded, you will be returned an array of card resources. The structure of each card resource is the same as would be obtained if you had issued a GET to obtain a single resource.

  <?xml version="1.0" encoding="UTF-8"?>
  <cards type="array">
    <card>
      <name>Automatically update event status when event date has passed</name>
      <description>
      </description>
      <card_type>
        <name>Story</name>
      </card_type>
      <id type="integer">419</id>
      <number type="integer">11</number>
    ...
      <properties type="array">
        <property type_description="Managed text list" hidden="false">
          <name>Status</name>
          <value>New</value>
        </property>
      ...
      </properties>
    </card>
    <card>
      <name>Add details to event</name>
      <description>
      </description>
      <card_type>
        <name>Story</name>
      </card_type>
      <id type="integer">424</id>
      <number type="integer">16</number>
    ...
      <properties type="array">
        <property type_description="Managed text list" hidden="false">
          <name>Status</name>
          <value>Open</value>
        </property>
      ...
      </properties>
    </card>
  </cards>
      

Example 2 - Using a MQL filter

    GET

    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards.xml

    filters[mql]=Type is story AND Status is not accepted
    sort=status
    order=ASC
      

Explanation

The above is an example of a GET request to retrieve a set of cards filtered using MQL from the project with identifier "test_project". The cards returned will all be of type "Story" and will have a status other than "accepted". They will be returned in the ascending order of their status values, as configured on the property management page in Mingle. This example is functionally equivalent to Example 1 above.

Result

If you were authorized to perform the operation, and the operation succeeded, you will be returned an array of card resources. The structure of each card resource is the same as would be obtained if you had issued a GET to obtain a single resource.

  <?xml version="1.0" encoding="UTF-8"?>
  <cards type="array">
    <card>
      <name>Automatically update event status when event date has passed</name>
      <description>
      </description>
      <card_type>
        <name>Story</name>
      </card_type>
      <id type="integer">419</id>
      <number type="integer">11</number>
    ...
      <properties type="array">
        <property type_description="Managed text list" hidden="false">
          <name>Status</name>
          <value>New</value>
        </property>
      ...
      </properties>
    </card>
    <card>
      <name>Add details to event</name>
      <description>
      </description>
      <card_type>
        <name>Story</name>
      </card_type>
      <id type="integer">424</id>
      <number type="integer">16</number>
    ...
      <properties type="array">
        <property type_description="Managed text list" hidden="false">
          <name>Status</name>
          <value>Open</value>
        </property>
      ...
      </properties>
    </card>
  </cards>
      

Example 3 - Using a saved view

    GET

    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards.xml

    view=Open Stories
      

Explanation

The above is an example of a GET request to retrieve all cards in the saved view called "Open Stories" in the project with identifier "test_project".

Result

If you were authorized to perform the operation, and the operation succeeded, you will be returned an array of card resources, in which each card resource would be a card in the "Open Stories" view. The structure of each card resource is the same as would be obtained if you had issued a GET to obtain a single resource.

  <?xml version="1.0" encoding="UTF-8"?>
  <cards type="array">
    <card>
      <name>Show event details in event list</name>
      <description>
      </description>
      <card_type>
        <name>Story</name>
      </card_type>
      <id type="integer">410</id>
      <number type="integer">2</number>
    ...
      <properties type="array">
        <property type_description="Managed text list" hidden="false">
          <name>Status</name>
          <value>Open</value>
        </property>
      ...
      </properties>
    </card>
    <card>
      <name>Create event and view event in an event list</name>
      <description>
      </description>
      <card_type>
        <name>Story</name>
      </card_type>
      <id type="integer">409</id>
      <number type="integer">1</number>
    ...
      <properties type="array">
        <property type_description="Managed text list" hidden="false">
          <name>Status</name>
          <value>Open</value>
        </property>
      ...
      </properties>
    </card>
  </cards>
      

Reference

    Request Method: GET
    URL: /api/v2/projects/project_identifier/cards.xml
    Parameters:

    tree_name: The name of a tree, whose cards are to be returned back
    

Example

    GET

    http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards.xml

    tree_name=Planning Tree
     

Explanation

The above is an example of a GET request to a Mingle server running at your.mingle.server, port 8080. This request will return all cards that belong to a 'Planning Tree'.

Result

If you have sufficient permissions to perform the action and the action was successful, you will be returned an array of card resources. The structure of each card resource is the same as would be obtained if you had issued a GET to obtain a single resource.

<?xml version="1.0" encoding="UTF-8"?>
<cards type="array">
  <card>
    <name>Story 1</name>
    <description nil="true"></description>
    <card_type>
      <name>Story</name>
    </card_type>
    <id type="integer">431</id>
    <number type="integer">4</number>
  ...
    <properties type="array">
      <property type_description="Any card used in tree" hidden="false">
        <name>Release</name>
        <value url="http://localhost:8080/api/v2/projects/test_project/cards/1.xml">
          <number type="integer">1</number>
        </value>
      </property>
      <property type_description="Any card used in tree" hidden="false">
        <name>Iteration</name>
        <value nil="true"></value>
      </property>
    </properties>
  </card>
  <card>
    <name>Iteration 1</name>
    <description nil="true"></description>
    <card_type>
      <name>Iteration</name>
    </card_type>
    <id type="integer">430</id>
    <number type="integer">3</number>
  ...
    <properties type="array">
      <property type_description="Any card used in tree" hidden="false">
        <name>Release</name>
        <value url="http://localhost:8080/api/v2/projects/test_project/cards/1.xml">
          <number type="integer">1</number>
        </value>
      </property>
    </properties>
  </card>
  <card>
    <name>Release 1</name>
    <description nil="true"></description>
    <card_type>
      <name>Release</name>
    </card_type>
    <id type="integer">428</id>
    <number type="integer">1</number>
  ...
    <properties type="array">
    </properties>
  </card>
</cards>
            

Reference

      Request Method: GET
      URL: /api/v2/projects/project_identifier/cards.xml
      Parameters:

      tree_name: The name of a tree, whose cards are to be returned back
      excluded[]: Any card type that is not wished to be returned back
      tf_card_type[] : A tree filter for the specified card type.
      tagged_with : A comma separated list of tags that will be used to further filter the list of cards in addition to the filters
      all tree properties               
      

Example

GET

http://yourname:password@your.mingle.server:8080/api/v2/projects/test_project/cards.xml

tree_name=Planning Tree
excluded[]=Defect
tf_release[]=[Release][is][1]
      

Explanation

The above is an example of a GET request to a Mingle server running at your.mingle.server, port 8080. This request will return all cards that belong to the Release card numbered 1 in the 'Planning Tree', while excluding the Defect card types. For example, let's say you have two Defects and one Story that belong to Release card numbered 1. This request will only return one story card since the Defect card type is excluded.

Result

If you have sufficient permissions to perform the action and the action was successful, you will be returned an array of card resources. The structure of each card resource is the same as would be obtained if you had issued a GET to obtain a single resource.

<?xml version="1.0" encoding="UTF-8"?>
<cards type="array">
  <card>
    <name>Story 1</name>
    <description nil="true"></description>
    <card_type>
      <name>Story</name>
    </card_type>
    <id type="integer">431</id>
    <number type="integer">4</number>
  ...
    <properties type="array">
      <property type_description="Any card used in tree" hidden="false">
        <name>Release</name>
        <value url="http://localhost:8080/api/v2/projects/test_project/cards/1.xml">
          <number type="integer">2</number>
        </value>
      </property>
      <property type_description="Any card used in tree" hidden="false">
        <name>Iteration</name>
        <value nil="true"></value>
      </property>
    </properties>
  </card>
  <card>
    <name>Iteration 1</name>
    <description nil="true"></description>
    <card_type>
      <name>Iteration</name>
    </card_type>
    <id type="integer">430</id>
    <number type="integer">3</number>
  ...
    <properties type="array">
      <property type_description="Any card used in tree" hidden="false">
        <name>Release</name>
        <value url="http://localhost:8080/api/v2/projects/test_project/cards/1.xml">
          <number type="integer">2</number>
        </value>
      </property>
    </properties>
  </card>
  <card>
    <name>Release 1</name>
    <description nil="true"></description>
    <card_type>
      <name>Release</name>
    </card_type>
    <id type="integer">428</id>
    <number type="integer">1</number>
  ...
    <properties type="array">
    </properties>
  </card>
</cards>
                  

From a card resource, follow the rendered_description resource to retrieve the rendered description for a card as HTML.

For example: suppose you have a card with the following description:

The card resource and rendered description will show the following:

<h3>Steps to reproduce</h3>

<ol>
  <li>Navigate to login page</li>
  <li>Enter incorrect name and password</li>
</ol>

<h3>Behavior</h3>

<p>Login fails, but there is no error message.</p>

<h3>Expected behavior</h3>

<p>Provide an error message the login failed.</p>
            

Notice that rendered_description does not contain any styling information. If you view the card description in Mingle, the description will be styled according to Mingle's style:

In comparison, viewing rendered_description in a browser will not style the description:

You may reference the Mingle stylesheet, found on every Mingle page, when displaying rendered_description if you would like it to be styled as is in Mingle. If you would like it styled a different way, you can do that as well.

Macros in rendered_description

In the previous section, the card description didn't contain any macros. If there are macros in the description, the macros will be rendered as part of the rendered_description. In the following example, the card contains two macros, table and pie-chart:

When you get the card resource, the description and rendered_description are provided as follows:

<card>
  <name>Release 1</name>
  <description>

{{
  table 
    view: "story backlog"
}}


{{
  pie-chart
    data: SELECT status, count(*) WHERE type = story and priority = must
}}</description>
  ...
  <rendered_description url="http://localhost:8080/api/v2/projects/test_project/render?content_provider%5Bid%5D=990&amp;content_provider%5Btype%5D=card">
  </rendered_description>
</card>
          

If you access the rendered_description it will render these macros:

<table>
  <tr>
    <th>Number</th>
    <th>Name</th>
    <th>Status</th>
    <th>Priority</th>
    <th>Estimate</th>
  </tr>
  <tr>
    <td>
      <a href="http://localhost:8080/projects/test_project/cards/17">17</a>
    </td>
    <td>
      <a href="http://localhost:8080/projects/test_project/cards/17">Sort event list</a>
    </td>
    <td>New</td>
    <td>Could</td>
    <td>&nbsp;</td>
  </tr>
  <tr>
    <td>
      <a href="http://localhost:8080/mingle/projects/test_project/cards/11">11</a>
    </td>
    <td><a href="http://localhost:8080/mingle/projects/test_project/cards/11">Automatically update event status when event date has passed</a></td>
    <td>New</td>
    <td>Could</td>
    <td>&nbsp;</td>
  </tr>
</table>


<img alt="pie-chart" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAbgAAAEsCAMAAACG41bUAAACTFBMVEX////6
+v/r6//i4v/Pz//Fxf+ysv+oqP+Vlf+Li/+Cgv94eP9vb/9mZv//Pz//S0v/
WFj/ZWX/cnL/cXH/i4v/mJj/srL/v7//2Nj/5eX/+Pitrf+Jif9xcf9sbP9r
a/9oaP//MzP/Njb/Ojr/PDz/QkL/YmL/kpL/2dn/WVnv7/+kpP//hob/6ur/
5ub/TEz19f95ef9paf9ubv//Pj7/ODj/8fH/jIwAAADq6v+7u///paX/5ORt
bf+MjP//Zmbm5v9qav//OTn/3t7m5ubT0///xMQ/Pz+Pj4+PY2PmLi7mRETE
xP//sbGUlP//cHDOzv//vr6goP//gIC/v///qqqBgf/Y2P//y8vJyf//t7f/
pKSjo//TdUl1vTQ69zSG4mnyPzNmzjU+9jUz/zM+/z6x/7HLZjNC8DPY/9iy
fzNM/0yGrTQ+9DQ8/zyG/4a+/75C/0Lx//GXl/83/zd0/3SY/5iljDPe/96T
k/9v/2/lTDNY2zU8+DXL/8tY/1g4+TM//z9m/2Y4/zjk/+R1vjU5/zm/czM5
+DO3/7c/9DWk/6TYWTNM5jSYmTM89jM4+zU841dUoLJka/g29T9mbfhMsplJ
u4xicfBmbvZGxX9geebs7P9lb/Spqf9Dz3NegttkbvQ/2GbZ/9lZ/1lbjM7m
/+ZkbPaM/4xiYvc84lkx9zH39/efn58yMk9Yl74pTylPT0+AgJ9qavdkafk8
9zx2n3Y560xSpK1mafuSkv+q/6qA/4Bw/3DE/8RkbfVN2HOy/7K73tzw8P+R
qgeVAAANTElEQVR4nO2diX9cVRXH084kTSd5IS5QNEnTZ1OWppJkmspNsCEV
Cy4VI2JjNe6JS6OjsVUQlRILruCGKChUEQTUoqK44L78Y868fZKZN/e+d8+5
b3J/38+nM0MyTN6738+55y7nvenpAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANLBrd6nc27env39vZWBg
0Bm64orhl738Fa+88qp9V7/q1aYPDrSkVB4ZHXP2jx9wYtyI1xyccA9dc+2+
q40c23XXuxq4/jojB0/I4fJkxRkfd7ax7dwPHnSHj+x7LfPx3TClw5vrTt3A
fOCUTJcnZ6pHtztrLc5j9tjUkX2vYzzGG13R+Lui9eGI+FfhkxCJx8RbbmQ8
aFLm5kedwTbS2otrMORec9PruQ5zKm7+Nt5EICxhMnoUbvTjKa4jJuXwfKV6
PMVaqrg6E8eGb+LpNCMDfhQlYyhhKTIUv24S13hiOVxaygudrHUS57m7eR/D
sTYZiF8m+s+24hpRKKKfdb24xZETaT2ktLg6Q2+49pbGR75R0OGGrqL/EskO
MA7ASFyQ48JfitCx6YbPx8mFalVGm5Q41z127OZbe3puexPdAcfi4nBqIS4y
lYyxRHR2ubjeSrsxZEZxdWaH33wb4SFPhSOQZHZrcrRlVOkm35MQ18WDk94B
qT5SUZz7FvHWq+gOOp4OCNEspYW4uENNvDd41bXTgVNK2hTE1RmaehvVYadO
wNvM7lq9sVsn4CcVOkl1cXV1w7cSHXnqkpekOdGtS16Lt+9X1KYqrj49ePst
pk9zx9GnbC2DuDpXmj7RncXSQOfZth5xE1PvMH2yO4fpO9R7yazi6ureybkA
vZNZGpOcb+sR5x47hKDTwWTGcMssrh50R0yfdPdTypbd8omrZzozW+U7hzuz
W8sjrs67TJ96VzOpOuXWJ24W3WVm5k7n6CbzinMnhtm2yHcYy2P5tOUU57qH
3m26CbqSM3m15Rbnuu8x3QhdyHz2WYA+cRPvNd0MXUdfvmGJJnHuLNYu1VjR
4U2DOHcIg0sVTmnxpkOcO0S2v7oD0eRNizh3FuZk0dNP6hKHqbgs2rxpEoc8
J4eW8aRWce4QxpadmdfnTZs4dxbzuU6c0TDv1i/OncAaSjrLGrXpFOe6WLdM
Yy73ujKZuEPYK0jhtFZvWsW57zPdOAVmRWeC0yzu/R/4oOnmKSy6FkwIxH3o
wx9ZXfuo6QYqKCXN2jSK+9jHVxt8wnQTFZOBwoo7u+qzbrqJConuBKdP3Cc/
FYirfdp0IxWQJf3e9IhrpLeQ2mdMN1PhmNY7g9MnLkhvARufNd1QReNc1usD
iMWdXW3i/OdMN1TBoOgodYiL0hs6y9boH1HqEJdMbyEYWSbpIwm4vOKa01sY
cp833VgFYpFEW15xd7XQ1uBu081VHL5QRHHb0lvIPaabqzAs03SUucR98Utf
buNttXav6QYrCpo3c3SIa5neQi6YbrCCoH1TIL+4u+5L8ba6iW0CD5qpQB5x
bdNbAKYEDegCLqO4lPSGkEtAF3DZxKWmN4RcBGHAZRKXnt4QchFkQ8ps4jql
twAMLJcJA05dXOf0FrBm/VxugdCbsjiZ9BbwFdMNZ5g5im24rOKk0lvAxftN
N51ZVgok7gG59OZz3vLykxOU3pTESae3gK+abjqjnKEcmiiJ+9rXlbTVZwTf
MN14JiEdmqiIU0lvATYPT2iHJgriHvimsjerhyc67h6kQZxqevOpfct085mD
ctVEXpxyeguwd/WEuqeUE5chvfnY21dS95RS4rKkNx97+0riMaWMuGzpLcDW
ceU0tbfO4rKmtwBLLyRYop19S4jLnN58Ni0tR1+h9tZJXPb0FmDpeiVhzYKM
uAcfypHefOysYCCfDKSLy5nePOycENCnuDRx3/5Ofm+ra1YmOfoUlyIud3rz
sTLJUa93pYh78KHvavFm56oXvbd24nSktwDTjWiAEn2KayNOS3rzWbPwljWn
qBcq24nTlN48ahYWxjKMTVqJ05befCwcnZCvMLcUpzG9eVi4zkxxQ5qO4jSm
N58N083ID4O3beJ0prcA083ITolhbLJFnOb05lGzbljJsOC1RdzZzhrUsW9n
h2M20CROe3rzsG8+0MfgLSGu1c2dtGDdfYbOsYqjSG8+1t1Nj2Ma55CmNx/r
JnIMewOROJr05mPd/gB93UIojiy9eVhXvcCxcOLQpjcP65ZOaK9ojMURpjcP
665vZBJHmd7sFMfhzaFNbz6mG5IbFnG06Q3iyPgevTeIo+D7EKcdFnEP/wDi
dMMyqnzkh+TerBtVsohjCDnrxLGsnDiP/IhanHUrJyxrlY7zKLU469YqWXYH
HOcx6pCzbneAZT/OoQ856/bjWHbA6zz2Y1pxxd4BL1XkW6pSkvpIlpqTBj+h
FVfompPHZ1RaauZxmc9kqfJq8ARpyBW7yuvSlrYQQtQf2jSUcC7JfCZLXaUH
acgVu65yS8AJ7197cTMyn8lSyezxxE8JxRW7knmrmfDJi7wtj42fZ/hQSn5G
KK7YS5VtxIlWj0JWHM/SSYMnCUOu2AsnqeKcMOBE9BOpD+WayDmkIVfsaVy6
ON9e9CtZcRxXpAY8+XMycXJXpD71tKY/9/RTOcRF3WK+rpJtPlDnF5rabRty
s4Fn1rX9wfVncoiLpgO5Biccd10IeZYq5OTuuvBc/Z319mn/MSL8ffSuRubx
Hrxf+W/x/j2XR1wnaD41D2QhJ3Wm63G7t/XmPcXvEk2/EvFPlXYjVJtJ7lNP
/5JCUWue/RWJtl/L7Q3ENsRqHFjB66SkSFzkuFlc48m0uMvP/6bdFJ6C35KI
E797/rKaOBH7EWKLpajDDHrKyKJIvoVSnJDhhd//gcJQG14kCbk//ukFmVNN
RpyvTIjt4RV1mLGkZDCGb6UUJ/OZlznuV5mAJOQu3t+jGHGrcb+3RVxyBJIU
Gf2PohjietiqF3xe/DOBOMmRQjw4aeoqm8RFD8kXLcQpD0780b8Ilkic4Efh
kwgn40JBHOMUvM5fCMRJ3hAqng40D06SlsKRf2Q4EX3+G/xXqtOBSEpCmIie
RLxdIOTF8e3seOgPOdk9nXgC3npGkDLD2/pG1Ql40ltkSERPCXHSE3CO7x1I
8hJByMl+70C05NVGkaQ5ob7kFa4jx97CF8KJV0wUxXGuMzfQXhxb7BXmnlBc
6KpJXLwVLpzIq+znkn+3ThPa69GL/906TeLiaXO8nePEXaaKON4JgfZ69OLf
vH4mirRt4qKnhDip0gUPpqrYAN0hV/xa2EtBOhNxT5noM6PEF4aeVLGQB29f
qbk4tvg9ZaM8T3pdUUiW53kw95V669GL31N6BbGS5oRsQawP87hSa8gVfkxJ
CfH3gG9FZz263d8DznR9Y4TG4ljrrmhsZoU3y+mrRz9v4Y3rkzAPT/SFXDcM
TUhhHp5oq0e3emjSYJl3eKKrOHbtXtMNZxze1RNd9ejFXzUh51Q3htxmoS+L
Y4K1gkFTPbp191poBXfIaSiORcB5MIechnp0BJxH14UcAi6AeWCZux4dQ8qA
Zd5tubzFsTXM4UL+yisuZz36Paabqzgs8orLGXJ3m26uAtHH21nmqUevFfpe
QuwwTwlyFMdiKtDEEvP4JHPI1Qp9KyEDnGPdmMtcj36+2HfLM8A03w1rPDIW
x27IXi5gD7ydZcbiWHSULVhhNZepHr1meaFJG1hHlplCDiPKlpQ4xWUqji30
PQ4NwrpNoF6PvoZNgXawpjnVkEOCS4Fzg0e1Hh2bOSnMcc7m1IpjN2yvgE1n
mVGcWj06NuHSOcOY5hRCrmb3tTkyzPMNLeXr0deKf/Wpefr4zMkWx25iD06G
FTZzkvXom5gIyMFnTirk1uBNFrYlFJl6dCyYKMBmrnNxLKpfleDqLTvWoyO/
KcI1tuwQcmsYT6rCdNeh9Hr0Lrh7UPE4wyIuvTgW6yVZWGZZcU6pR9/A+mQ2
5k4fZzDXLuRqF7AfkJlJhiFKm3p0TLtzcSe9uDb16H8zfepdTmmAvrvcHnK1
ddQF5WaSel6wvR4d5SVaWBqjvq6guTj24gbqlfUwfQdt0L3UVBxb+zuuD9DG
Em2mS9Sj19YRblrpoxSXqEfH2qRuFm8n7C8fDsLtH7i+m4CTFbLpuFePvnnh
n6ZPcadyamCQyNyjq5vr2DElpJdI3b/+/R/Tp7bT6SXoMI9W/mv6tGzg5EJV
54y8Wl04afqUbGFx5ISuHnPwxMii6dOxivJCNf+c/Hh1oWz6ROzjf/OVXO6O
Vyvzh02fhKXMzY862frMQWd0fs704VvNdHlypqo2zjxanZksT5s+cFDvNMuT
FWd8XMJZ/U2VyTI6yCJRKo+Mjjn7xw+0NHZgfL8zNjpSVvlyO8DHrt2lcm/f
nv7+vZWBgUFncGCgsre/f09fb7m0e5fpgwMAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAZv4Pehjjppw2F8cA
AAAASUVORK5CYII=
" />
            

In this example, the table macro is rendered as HTML, so it is simple to include the markup for the rendered table. The pie chart is an image, so the image is also included in the rendered_description. Here is the rendered_description as seen in a browser:

Any JavaScript in the rendered description will be removed from rendered_description. For example, the following Mingle macros use JavaScript:

• Daily history chart
• Generic gadget
• Go pipeline gadget