{
	"id": "160944",
	"key": "AC-3807",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "12217",
			"key": "AC",
			"name": "Appcelerator - INBOX",
			"projectCategory": {
				"id": "10000",
				"description": "",
				"name": "Customer Service"
			}
		},
		"resolution": {
			"id": "8",
			"description": "",
			"name": "Needs more info"
		},
		"resolutiondate": "2016-06-21T18:26:12.000+0000",
		"created": "2016-06-09T15:50:02.000+0000",
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "shossain",
			"key": "shossain",
			"displayName": "Shak Hossain",
			"active": false,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2016-06-21T18:26:12.000+0000",
		"status": {
			"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
			"name": "Closed",
			"id": "6",
			"statusCategory": {
				"id": 3,
				"key": "done",
				"colorName": "green",
				"name": "Done"
			}
		},
		"components": [
			{
				"id": "14548",
				"name": "Titanium SDK & CLI",
				"description": "Please enter tickets related to the MobileSDK here."
			}
		],
		"description": "I tend to build custom tags, using the module=\"ui\" attribute to point the create function toward a commonJS lib that handles the createThis, and createThat etc.\r\n\r\nTypically that means if I'm building a control, I would use classic Ti in the commonJS file and the return a view, button etc.\r\n\r\nIn this example, I was trying to use an alternative where I could create a controller, view, style file in a subfolder e.g. ui/slider and then invoke that from a custom tag so:\r\n{code:xml}\r\n<Slider module=\"ui\"/>\r\n{code}\r\n\r\nin the ui.js lib would be something like :\r\n\r\n{code:java}\r\nexports.createSlider = function(){\r\n   return Alloy.createController(\"ui/slider\").getView();\r\n}\r\n{code}\r\n\r\nThe idea being I'd have a simple XML markup that would still say the name of the object (rather than using require) but have the benefit of using TSS, XML etc to create the element.\r\n\r\n(basically didn't want to use Require)\r\n\r\nIt works as in it renders the view fine -- the issue is that any exceptions don't appear in the console and neither do any events work in the control -- so if I add ANY event listener in the control it never works.\r\n\r\nIf I change the XML entry to:\r\n\r\n{code:xml}\r\n<Require src=\"ui/slider\"/>\r\n{code}\r\n\r\nand bypass the CommonJS lib, it works fine.",
		"attachment": [],
		"flagged": false,
		"summary": "Exceptions and events don't fire for Alloy views created via Tags and a CommonJS lib",
		"creator": {
			"name": "jasonkneen",
			"key": "jasonkneen",
			"displayName": "Jason Kneen",
			"active": true,
			"timeZone": "Europe/London"
		},
		"subtasks": [],
		"reporter": {
			"name": "jasonkneen",
			"key": "jasonkneen",
			"displayName": "Jason Kneen",
			"active": true,
			"timeZone": "Europe/London"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "388335",
					"author": {
						"name": "sdarda",
						"key": "sdarda",
						"displayName": "Sharif AbuDarda",
						"active": false,
						"timeZone": "Asia/Dhaka"
					},
					"body": "Hello, This is how the Alloy XML markup works. It's started from Alloy 1.2.0. You have to use the require. This is not a bug. For reference please follow the link http://docs.appcelerator.com/platform/latest/#!/guide/Alloy_XML_Markup-section-46248608_AlloyXMLMarkup-RequireElement",
					"updateAuthor": {
						"name": "sdarda",
						"key": "sdarda",
						"displayName": "Sharif AbuDarda",
						"active": false,
						"timeZone": "Asia/Dhaka"
					},
					"created": "2016-06-14T20:46:41.000+0000",
					"updated": "2016-06-14T20:46:41.000+0000"
				}
			],
			"maxResults": 1,
			"total": 1,
			"startAt": 0
		}
	}
}