{
	"id": "87838",
	"key": "TIMOB-7976",
	"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": "2012-03-13T12:30:48.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [],
		"versions": [
			{
				"id": "12593",
				"name": "Release 2.0.0",
				"archived": false,
				"released": true,
				"releaseDate": "2012-03-30"
			}
		],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-06T18:57:56.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": "10206",
				"name": "iOS",
				"description": "iOS Platform"
			}
		],
		"description": "Developers would like more info about what JS is being evaluated when a crash happens posted to the crash log.  Any additional information that Titanium could output to a crash log would be appreciated.  Currently iOS crash logs sent in from users in the wild are very hard to correlate back to the application code. ",
		"attachment": [],
		"flagged": false,
		"summary": "iOS: Increase Crash Log output if possible",
		"creator": {
			"name": "aleard",
			"key": "aleard",
			"displayName": "Alan Leard",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "aleard",
			"key": "aleard",
			"displayName": "Alan Leard",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": "iOS Device",
		"comment": {
			"comments": [
				{
					"id": "186289",
					"author": {
						"name": "ngupta",
						"key": "ngupta",
						"displayName": "Neeraj Gupta",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "We should evaluate the same for Android platform as well.",
					"updateAuthor": {
						"name": "ngupta",
						"key": "ngupta",
						"displayName": "Neeraj Gupta",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2012-03-13T13:04:09.000+0000",
					"updated": "2012-03-13T13:04:09.000+0000"
				},
				{
					"id": "186374",
					"author": {
						"name": "ivan.skugor",
						"key": "ivan.skugor",
						"displayName": "Ivan Skugor",
						"active": true,
						"timeZone": "Europe/Amsterdam"
					},
					"body": "Hello.\r\n\r\n\r\nThis is, IMHO, extremely important topic. Currently on Android, when app crashes, Java exception is thrown (of course, when it is not related to JS directly) that can't be caught by try/catch in JS. Because of that, tracing the source of that exception and dumping execution stack is impossible (and that makes bug finding a hard task to do). Just by having the option to catch Java exception in JS we (developers) will have an option to build our own tools (by using JS) for debugging and tracing that would work on devices and not only on slow, buggy, slow and unreliable (did I say slow :) ) Android emulators.",
					"updateAuthor": {
						"name": "ivan.skugor",
						"key": "ivan.skugor",
						"displayName": "Ivan Skugor",
						"active": true,
						"timeZone": "Europe/Amsterdam"
					},
					"created": "2012-03-14T01:49:57.000+0000",
					"updated": "2012-03-14T01:49:57.000+0000"
				}
			],
			"maxResults": 2,
			"total": 2,
			"startAt": 0
		}
	}
}