{
	"id": "144832",
	"key": "ALOY-1309",
	"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": "2015-02-17T11:34:23.000+0000",
		"priority": null,
		"labels": [
			"event",
			"underscore"
		],
		"versions": [],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-06T18:50:02.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": "I've written a suggestion about having the possibility to make an event debounced or onced directly in Alloy. There is nothing more than preventing repeating the same code always...\r\n\r\nhttps://developer.appcelerator.com/question/180774/idea-for-new-feature-in-alloy--once-and-debounce-events\r\n\r\nThank you for your consideration and answer",
		"attachment": [],
		"flagged": false,
		"summary": "Debounced and \"onced\" events",
		"creator": {
			"name": "gduthieuw",
			"key": "gduthieuw",
			"displayName": "Guile",
			"active": true,
			"timeZone": "Europe/Berlin"
		},
		"subtasks": [],
		"reporter": {
			"name": "gduthieuw",
			"key": "gduthieuw",
			"displayName": "Guile",
			"active": true,
			"timeZone": "Europe/Berlin"
		},
		"environment": null,
		"comment": {
			"comments": [],
			"maxResults": 1,
			"total": 1,
			"startAt": 0
		}
	}
}