{
	"id": "104376",
	"key": "ALOY-365",
	"fields": {
		"issuetype": {
			"id": "7",
			"description": "gh.issue.story.desc",
			"name": "Story",
			"subtask": false
		},
		"project": {
			"id": "11113",
			"key": "ALOY",
			"name": "Alloy",
			"projectCategory": {
				"id": "10400",
				"description": "Tools for developing applications",
				"name": "Tooling"
			}
		},
		"fixVersions": [
			{
				"id": "14632",
				"description": "Alloy 0.3.2",
				"name": "Alloy 0.3.2",
				"archived": false,
				"released": true,
				"releaseDate": "2012-11-16"
			},
			{
				"id": "14600",
				"description": "2012 Sprint 23",
				"name": "2012 Sprint 23",
				"archived": true,
				"released": true,
				"releaseDate": "2012-11-19"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2012-11-12T19:20:07.000+0000",
		"created": "2012-11-05T16:16:22.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [
			"notable"
		],
		"versions": [],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:25:51.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": "{{Alloy.CFG}} is a good, safe place to put globals in your Alloy applications so that you don't need to manage a commonjs module for globals yourself. It is also where your config.json configs get stored. It would likely be more intuitive for developers if they hada clear place to store globals. For this reason, I'd like to make the {{Alloy.globals}} namespace an empty object where developers can attach globals that they can then reference throughout the application. \r\n\r\nIt seems like a little bit of overlap with {{Alloy.CFG}}, but I think {{Alloy.globals}} is far more intuitive and and much more common use case.\r\n\r\nh4. alloy.js\r\n{code:javascript}\r\n// Alloy.globals by default equals {}\r\nAlloy.globals.someGlobalFunction = function(){}; \r\n{code}\r\n\r\n*Important*: {{Alloy.globals}} will erase the need for developers to roll their own globals libraries/namespaces.",
		"attachment": [],
		"flagged": false,
		"summary": "create Alloy.globals and reserve for developer use",
		"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": [
				{
					"id": "227034",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Completed and currently in \"binding\" branch of the github repo",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-11-12T19:20:07.000+0000",
					"updated": "2012-11-12T19:20:07.000+0000"
				},
				{
					"id": "227365",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "This is no in \"master\" and will be released with 0.3.2",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-11-14T19:42:20.000+0000",
					"updated": "2012-11-14T19:42:20.000+0000"
				}
			],
			"maxResults": 2,
			"total": 2,
			"startAt": 0
		}
	}
}