{
	"id": "109979",
	"key": "ALOY-530",
	"fields": {
		"issuetype": {
			"id": "4",
			"description": "An improvement or enhancement to an existing feature or task.",
			"name": "Improvement",
			"subtask": false
		},
		"project": {
			"id": "11113",
			"key": "ALOY",
			"name": "Alloy",
			"projectCategory": {
				"id": "10400",
				"description": "Tools for developing applications",
				"name": "Tooling"
			}
		},
		"fixVersions": [
			{
				"id": "15271",
				"description": "Alloy 1.1.0, concurrent with SDK 3.1.0",
				"name": "Alloy 1.1.0",
				"archived": false,
				"released": true,
				"releaseDate": "2013-04-16"
			},
			{
				"id": "14873",
				"description": "2013 Sprint 04",
				"name": "2013 Sprint 04",
				"archived": true,
				"released": true,
				"releaseDate": "2013-02-25"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2013-02-23T03:32:20.000+0000",
		"created": "2013-02-21T16:30:23.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [
			"notable"
		],
		"versions": [
			{
				"id": "14634",
				"description": "Alloy 1.0.0",
				"name": "Alloy 1.0.0",
				"archived": false,
				"released": true,
				"releaseDate": "2013-02-19"
			}
		],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:25:45.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": [
			{
				"id": "12329",
				"name": "Runtime",
				"description": "Generic bucket for uncategorized runtime issues"
			}
		],
		"description": "h2. update (2/22/2013)\r\n\r\nWidgets will have an object available in controllers that will allow them to execute these functions and get other information about the current widget. Only widget controllers will have this available, non-widget controllers will not have access to this object. The relevant widgetId will be embedded in these calls, so they will have the same signature as the Alloy namespace counterparts. \r\n\r\n* Widget.createController(name, args)\r\n* Widget.createWidget(id, name, args)\r\n* Widget.createModel(name, args)\r\n* Widget.createCollection(name, args)\r\n* Widget.widgetId\r\n\r\nh2. original\r\n\r\nThe following functions always reference locations relative to the \"app\" directory:\r\n\r\n* Alloy.createController()\r\n* Alloy.createWidget()\r\n* Alloy.createModel()\r\n* Alloy.createCollection()\r\n\r\nThese functions are often executed within controllers in widgets. It would be beneficial for developers if these functions references the paths relative to the given widget, rather than those in the app itself which don't really apply to the widget. I'd like to do it transparently without having the developers needs to pass additional information into those functions, but I'll need to investigate further to see if that is possible.",
		"attachment": [],
		"flagged": false,
		"summary": "Creation functions for widgets",
		"creator": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": null,
		"comment": {
			"comments": [],
			"maxResults": 0,
			"total": 0,
			"startAt": 0
		}
	}
}