{
	"id": "113744",
	"key": "ALOY-655",
	"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": null,
		"resolutiondate": null,
		"created": "2013-05-02T22:21:14.000+0000",
		"priority": {
			"name": "Low",
			"id": "4"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:26:09.000+0000",
		"status": {
			"description": "The issue is open and ready for the assignee to start work on it.",
			"name": "Open",
			"id": "1",
			"statusCategory": {
				"id": 2,
				"key": "new",
				"colorName": "blue-gray",
				"name": "To Do"
			}
		},
		"components": [],
		"description": "For Studio integrations, we need to be able to store meta-data about the Alloy components, ie\r\n{code}\r\n<Alloy>\r\n\t<Window class=\"container\">\r\n\t\t<Label id=\"label\" onClick=\"doClick\" data-studio-id=\"323112\">Hello, World</Label>\r\n\t</Window>\r\n</Alloy>\r\n{code}\r\n\r\nThis is similar to what HTML5 provides, so there appears to be other use cases for it",
		"attachment": [],
		"flagged": false,
		"summary": "Provide a data- attribute support for Alloy xml",
		"creator": {
			"name": "nle",
			"key": "nle",
			"displayName": "Nam Le",
			"active": false,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "nle",
			"key": "nle",
			"displayName": "Nam Le",
			"active": false,
			"timeZone": "America/Los_Angeles"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "296779",
					"author": {
						"name": "skypanther",
						"key": "skypanther",
						"displayName": "Tim Poulsen",
						"active": true,
						"timeZone": "America/New_York"
					},
					"body": "Can you provide more details on this? Is the request still valid? What is the use-case? Does the ID need to be unique per app, per build, per developer, globally? Does the ID need to be numeric, sequential, a GUID/hex string?",
					"updateAuthor": {
						"name": "skypanther",
						"key": "skypanther",
						"displayName": "Tim Poulsen",
						"active": true,
						"timeZone": "America/New_York"
					},
					"created": "2014-03-12T14:49:01.000+0000",
					"updated": "2014-03-12T14:49:01.000+0000"
				},
				{
					"id": "304649",
					"author": {
						"name": "skypanther",
						"key": "skypanther",
						"displayName": "Tim Poulsen",
						"active": true,
						"timeZone": "America/New_York"
					},
					"body": "[~pinnamuri] Is this still something Studio needs? If so, can you answer the questions above?",
					"updateAuthor": {
						"name": "skypanther",
						"key": "skypanther",
						"displayName": "Tim Poulsen",
						"active": true,
						"timeZone": "America/New_York"
					},
					"created": "2014-05-13T19:39:25.000+0000",
					"updated": "2014-05-13T19:39:25.000+0000"
				},
				{
					"id": "304651",
					"author": {
						"name": "pinnamuri",
						"key": "pinnamuri",
						"displayName": "Praveen Innamuri",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"body": "I don't know where did this request originated from. However, I don't think we would require this additional property specific to Studio at this moment, and  that doesn't sounds right to me (unless I get to know the original use case).\r\n\r\nI would shelve this to backlog and we can prioritize it as we discover the real need for this :-)",
					"updateAuthor": {
						"name": "pinnamuri",
						"key": "pinnamuri",
						"displayName": "Praveen Innamuri",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-05-13T19:42:58.000+0000",
					"updated": "2014-05-13T19:42:58.000+0000"
				}
			],
			"maxResults": 3,
			"total": 3,
			"startAt": 0
		}
	}
}