{
	"id": "108671",
	"key": "ALOY-507",
	"fields": {
		"issuetype": {
			"id": "2",
			"description": "A new feature of the product, which has yet to be developed.",
			"name": "New Feature",
			"subtask": false
		},
		"project": {
			"id": "11113",
			"key": "ALOY",
			"name": "Alloy",
			"projectCategory": {
				"id": "10400",
				"description": "Tools for developing applications",
				"name": "Tooling"
			}
		},
		"fixVersions": [],
		"resolution": null,
		"resolutiondate": null,
		"created": "2013-01-28T22:20:05.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [
			"alloy"
		],
		"versions": [],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:26:00.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": "12333",
				"name": "Widgets"
			}
		],
		"description": "Currently widgets can only exist in the 'widgets' directory.  We are utilizing a package/dependency manager and it would be much easier for us if we could set the search path for alloy to find widgets.\r\n\r\nOne possible solution is to allow something like the following to be included in the config.json\r\n\r\n\"paths\":[\"my/path/to/widgets\", \"my/other/path/to/widgets\"]\r\n\r\n",
		"attachment": [],
		"flagged": false,
		"summary": "ability to configure search path for widgets",
		"creator": {
			"name": "btknorr",
			"key": "btknorr",
			"displayName": "Brian Knorr",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"subtasks": [],
		"reporter": {
			"name": "btknorr",
			"key": "btknorr",
			"displayName": "Brian Knorr",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"environment": "Alloy",
		"comment": {
			"comments": [],
			"maxResults": 0,
			"total": 0,
			"startAt": 0
		}
	}
}