{
	"id": "140061",
	"key": "TIMOB-18059",
	"fields": {
		"issuetype": {
			"id": "2",
			"description": "A new feature of the product, which has yet to be developed.",
			"name": "New Feature",
			"subtask": false
		},
		"project": {
			"id": "10153",
			"key": "TIMOB",
			"name": "Titanium SDK/CLI",
			"projectCategory": {
				"id": "10100",
				"description": "Titanium and related SDKs used in application development",
				"name": "Client"
			}
		},
		"fixVersions": [],
		"resolution": null,
		"resolutiondate": null,
		"created": "2014-11-19T22:35:13.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "cbarber",
			"key": "cbarber",
			"displayName": "Chris Barber",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"updated": "2014-11-20T14:32:15.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": [
			{
				"id": "10207",
				"name": "Tooling"
			}
		],
		"description": "Between Google and Apple alone, there have been 30+ releases this year of various pieces of our software stack.\r\n\r\nWhile we blog when something is truly broken (i.e. http://www.appcelerator.com/blog/2014/10/updating-to-android-platform-tools-version-21/), and we link people to tickets to track status, it's not feasible to let everyone know in this way if Android SDK 23.0.2 is safe to use (though we may have tested it internally to confirm)\r\n\r\nA easy proposal would be to create a status page, similar to http://status.appcelerator.com. I have investigated reusing an existing status page sites, but they are not quite right for the purpose, so I believe we may need to create our own.\r\n\r\nRequirements:\r\n* Groups for each of the main families (Apple, Google, BlackBerry, Microsoft, etc)\r\n* Sub-sections for each of the individual areas (iOS, OS X). Debatable if we should instead just have them in a date-ordered cross-product list.\r\n* Columns for name, version, test environment, related JIRA tickets\r\n** green = tested\r\n** yellow = test in progress\r\n** red = test failed\r\n** grey = untested\r\n\r\nMy expectation this would be a Node.ACS application with some way of adding items to the matrix, and another item for updating status. Perhaps we can query status based on JIRA tickets...even if QE has an internal ticket to verify it working, the status page changes color based on that.\r\n\r\nSee attached page for a sample (though could be made prettier)",
		"attachment": [
			{
				"id": "52718",
				"filename": "Prototype Status Page.htm",
				"author": {
					"name": "ingo",
					"key": "ingo",
					"displayName": "Ingo Muschenetz",
					"active": true,
					"timeZone": "America/Los_Angeles"
				},
				"created": "2014-11-19T23:04:54.000+0000",
				"size": 77263,
				"mimeType": "text/html"
			}
		],
		"flagged": false,
		"summary": "Tooling: Create \"Tested\" status page for SDK dependencies",
		"creator": {
			"name": "ingo",
			"key": "ingo",
			"displayName": "Ingo Muschenetz",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "ingo",
			"key": "ingo",
			"displayName": "Ingo Muschenetz",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "332982",
					"author": {
						"name": "aleard",
						"key": "aleard",
						"displayName": "Alan Leard",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "I like this a lot and would love to have this as a reference with customers.  Would this be automated on CI builds?  Would we have a separate page for GA builds?  The prototype seems to have Studio and SDK separate, but what about CLI or Alloy (others?).",
					"updateAuthor": {
						"name": "aleard",
						"key": "aleard",
						"displayName": "Alan Leard",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-11-19T23:23:45.000+0000",
					"updated": "2014-11-19T23:23:45.000+0000"
				},
				{
					"id": "332983",
					"author": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Please note that this is not related to SDK builds. This is only for the releases of our dependencies that we want to let people know have been confirmed as working. see may have a separate page for SDK. It really should say \"Google\" vs. \"Android\"",
					"updateAuthor": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-11-19T23:36:59.000+0000",
					"updated": "2014-11-19T23:36:59.000+0000"
				},
				{
					"id": "332984",
					"author": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "If we wanted, we could have column(s) for various SDK/Studio versions so it was more matrix-like, but that could be confusing.",
					"updateAuthor": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-11-19T23:39:21.000+0000",
					"updated": "2014-11-19T23:39:21.000+0000"
				},
				{
					"id": "333041",
					"author": {
						"name": "rblalock",
						"key": "rblalock",
						"displayName": "Rick Blalock",
						"active": false,
						"timeZone": "America/Havana"
					},
					"body": "I love this idea.  \r\n\r\nColumns doesn't seem that confusing to me.  Example:  http://status.twilio.com\r\n\r\nOr maybe something like this:  https://status.basecamp.com\r\n\r\nWhere a column could represent a platform and the items under it would represent the different version #'s, etc.",
					"updateAuthor": {
						"name": "rblalock",
						"key": "rblalock",
						"displayName": "Rick Blalock",
						"active": false,
						"timeZone": "America/Havana"
					},
					"created": "2014-11-20T14:08:34.000+0000",
					"updated": "2014-11-20T14:08:34.000+0000"
				},
				{
					"id": "333045",
					"author": {
						"name": "bgrantges@appcelerator.com",
						"key": "bgrantges",
						"displayName": "Bert Grantges",
						"active": false,
						"timeZone": "America/Chicago"
					},
					"body": "Yep - i'm on board, i'd like to see also see us add tested Ti SDKs to this as well",
					"updateAuthor": {
						"name": "bgrantges@appcelerator.com",
						"key": "bgrantges",
						"displayName": "Bert Grantges",
						"active": false,
						"timeZone": "America/Chicago"
					},
					"created": "2014-11-20T14:22:27.000+0000",
					"updated": "2014-11-20T14:22:27.000+0000"
				},
				{
					"id": "333047",
					"author": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "[~rblalock] [~bgrantges] Would one of you like to mock up what/how you see that information being presented?",
					"updateAuthor": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-11-20T14:31:39.000+0000",
					"updated": "2014-11-20T14:31:39.000+0000"
				}
			],
			"maxResults": 6,
			"total": 6,
			"startAt": 0
		}
	}
}