{
	"id": "144590",
	"key": "TIMOB-18561",
	"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": "2015-02-12T21:13:48.000+0000",
		"priority": {
			"name": "None",
			"id": "6"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "pinnamuri",
			"key": "pinnamuri",
			"displayName": "Praveen Innamuri",
			"active": false,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2015-02-12T21:42:50.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": "It's challenging to manually update the current automation status for all of our repositories. I recommend we augment travis.appcelerator.org to highlight the following items. Suggestions on how to implement this are inlined:\r\n\r\n* Repo is a \"client\" project\r\n** use appc-client as keyword in package.json\r\n* Repo on CI build\r\n** Easy to check travis. How to check a repo is built with Jenkins?\r\n* CI build status\r\n** Easy for travis, how about Jenkins?\r\n* Container-based travis build\r\n** check for sudo: false in .travis.yml\r\n* Unit tests\r\n* Unit test run as part of CI\r\n** check for NPM test as part of .travis.yml\r\n* Performance tests\r\n* Performance tests run as part of CI\r\n* Code coverage\r\n* Code coverage run as part of CI\r\n* Code analysis\r\n* Code analysis run as part of CI\r\n* Automatic deployment of development builds\r\n** Could use travis for this where appropriate\r\n* Automatic deployment of pre-release builds (alpha, beta, etc)\r\n* Automatic deployment of release builds\r\n** Can check .travis.yml deploy section for providers",
		"attachment": [],
		"flagged": false,
		"summary": "Tooling: Create dashboard of current automation status",
		"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": [],
			"maxResults": 0,
			"total": 0,
			"startAt": 0
		}
	}
}