{
	"id": "101161",
	"key": "ALOY-269",
	"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": "14171",
				"description": "",
				"name": "2012 Sprint 19",
				"archived": true,
				"released": true,
				"releaseDate": "2012-09-24"
			},
			{
				"id": "14176",
				"description": "Release 3.0.0",
				"name": "Release 3.0.0",
				"archived": false,
				"released": true,
				"releaseDate": "2012-12-13"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2012-09-24T17:52:21.000+0000",
		"created": "2012-09-14T09:52:16.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [],
		"versions": [
			{
				"id": "14171",
				"description": "",
				"name": "2012 Sprint 19",
				"archived": true,
				"released": true,
				"releaseDate": "2012-09-24"
			}
		],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:26:02.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": "12332",
				"name": "Titanium SDK",
				"description": "Any integration or issues with the TiSDK"
			},
			{
				"id": "12331",
				"name": "Titanium Studio"
			}
		],
		"description": "Right now TiStudio is simply doing an \"npm install alloy\" to get alloy. This works for now, but eventually we are going to hit a point where non-backwards-compatible changes are made and developers should be able to manage which version of alloy they would like to install. We need to investigate from an npm perspective how different versions of Alloy can be installed, then we need to see how this can be managed inside TiStudio.",
		"attachment": [],
		"flagged": false,
		"summary": "Manage installed version of Alloy ",
		"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": "220394",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Any version of alloy can be installed globally like this:\n\n{code}\nsudo npm install -g alloy@0.2.34\n{code}\n\nand developers can also install locally and execute like this:\n\n{code}\nnode ./node_modules/alloy/Alloy/alloy.js ALLOY_PARAMS\n{code}",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-09-24T17:52:06.000+0000",
					"updated": "2012-09-24T17:52:06.000+0000"
				}
			],
			"maxResults": 1,
			"total": 1,
			"startAt": 0
		}
	}
}