{
	"id": "104948",
	"key": "ALOY-386",
	"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-14T14:35:05.000+0000",
		"created": "2012-11-14T14:21:07.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:26:09.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": "12327",
				"name": "Documentation"
			},
			{
				"id": "12332",
				"name": "Titanium SDK",
				"description": "Any integration or issues with the TiSDK"
			}
		],
		"description": "In alloy's early state, it's a good idea to keep the \"master\" branch as the current path of development for the next release. If a new feature is not going to be ready within the space of a single release, it should be developed in a new \"alpha\" branch. In the \"alpha\" branch new development can be a little more relaxed in terms of testing. Also, the development can take place over a longer period of time without impacting the \"master\". This will be useful for new features that will have a large impact on alloy like model-view binding and dynamic styling. The extra time this code remains in the \"alpha\" branch can be used to solicit feedback and help mold the beta or final state of the feature.",
		"attachment": [],
		"flagged": false,
		"summary": "create an \"alpha\" branch in the alloy github repo",
		"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": "227301",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Created an \"alpha\" branch in the github repo. This branch will contain the latest experimental features of alloy while they are still in development.",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-11-14T14:35:05.000+0000",
					"updated": "2012-11-14T14:35:05.000+0000"
				}
			],
			"maxResults": 1,
			"total": 1,
			"startAt": 0
		}
	}
}