{
"id": "97949",
"key": "ALOY-125",
"fields": {
"issuetype": {
"id": "2",
"description": "A new feature of the product, which has yet to be developed.",
"name": "New Feature",
"subtask": false
},
"project": {
"id": "11113",
"key": "ALOY",
"name": "Alloy",
"projectCategory": {
"id": "10400",
"description": "Tools for developing applications",
"name": "Tooling"
}
},
"fixVersions": [],
"resolution": {
"id": "1",
"description": "A fix for this issue is checked into the tree and tested.",
"name": "Fixed"
},
"resolutiondate": "2012-07-27T12:59:40.000+0000",
"created": "2012-07-25T00:33:20.000+0000",
"priority": {
"name": "Medium",
"id": "3"
},
"labels": [],
"versions": [],
"issuelinks": [],
"assignee": null,
"updated": "2018-03-07T22:25:55.000+0000",
"status": {
"description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.",
"name": "Resolved",
"id": "5",
"statusCategory": {
"id": 3,
"key": "done",
"colorName": "green",
"name": "Done"
}
},
"components": [],
"description": "Styles are done in tss files and typically tied to markup elements using class or id. Having support as a style attribute on the element would be. It should act as CSS style attribute when calculating style values. ",
"attachment": [],
"flagged": false,
"summary": "Add style attributes to markup ",
"creator": {
"name": "rmcmahon",
"key": "rmcmahon",
"displayName": "Russell McMahon",
"active": true,
"timeZone": "America/Los_Angeles"
},
"subtasks": [],
"reporter": {
"name": "rmcmahon",
"key": "rmcmahon",
"displayName": "Russell McMahon",
"active": true,
"timeZone": "America/Los_Angeles"
},
"environment": null,
"comment": {
"comments": [
{
"id": "209305",
"author": {
"name": "tlukasavage",
"key": "tlukasavage",
"displayName": "Tony Lukasavage",
"active": true,
"timeZone": "America/Los_Angeles"
},
"body": "I think what is meant to happen, as per the conversations had on the google group is not something like this:\r\n\r\n{code:xml}\r\n\r\n{code}\r\n\r\nbut instead like this:\r\n\r\n{code:xml}\r\n\r\n{code}\r\n\r\nI think the JSON will become extremely messing in a {{style}} attribute. Also, individual attributes is how this behavior is already handled for widgets and required views.",
"updateAuthor": {
"name": "tlukasavage",
"key": "tlukasavage",
"displayName": "Tony Lukasavage",
"active": true,
"timeZone": "America/Los_Angeles"
},
"created": "2012-07-25T08:31:13.000+0000",
"updated": "2012-07-25T08:31:13.000+0000"
},
{
"id": "209373",
"author": {
"name": "rmcmahon",
"key": "rmcmahon",
"displayName": "Russell McMahon",
"active": true,
"timeZone": "America/Los_Angeles"
},
"body": "Your right Tony. I did not mean use style=\"{..}\" in xml markup. I was thinking each style would be it's own attribute. I brought CSS for how to apply specificity.",
"updateAuthor": {
"name": "rmcmahon",
"key": "rmcmahon",
"displayName": "Russell McMahon",
"active": true,
"timeZone": "America/Los_Angeles"
},
"created": "2012-07-25T12:50:30.000+0000",
"updated": "2012-07-25T12:50:30.000+0000"
}
],
"maxResults": 2,
"total": 2,
"startAt": 0
}
}
}