{ "id": "104932", "key": "ALOY-383", "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": [ { "id": "14770", "description": "Alloy 0.3.4", "name": "Alloy 0.3.4", "archived": false, "released": true, "releaseDate": "2012-12-14" }, { "id": "14773", "description": "2012 Sprint 24", "name": "2012 Sprint 25", "archived": true, "released": true, "releaseDate": "2012-12-17" } ], "resolution": { "id": "2", "description": "The problem described is an issue which will never be fixed.", "name": "Won't Fix" }, "resolutiondate": "2012-12-07T14:52:01.000+0000", "created": "2012-11-14T02:46:41.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [ { "id": "14631", "description": "Alloy 0.3.1", "name": "Alloy 0.3.1", "archived": false, "released": true, "releaseDate": "2012-11-02" } ], "issuelinks": [ { "id": "22777", "type": { "id": "10020", "name": "Depends", "inward": "is dependent of", "outward": "depends on" }, "inwardIssue": { "id": "104931", "key": "ALOY-382", "fields": { "summary": "rightNavButton markup (and other similar properties)", "status": { "description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.", "name": "Resolved", "id": "5", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "4", "description": "An improvement or enhancement to an existing feature or task.", "name": "Improvement", "subtask": false } } } }, { "id": "22778", "type": { "id": "10002", "name": "Duplicate", "inward": "is duplicated by", "outward": "duplicates" }, "inwardIssue": { "id": "99676", "key": "ALOY-202", "fields": { "summary": "Implement a \"nolayout\" attribute (or something similar) in tags", "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" } }, "priority": { "name": "Medium", "id": "3" }, "issuetype": { "id": "4", "description": "An improvement or enhancement to an existing feature or task.", "name": "Improvement", "subtask": false } } } } ], "assignee": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2014-01-28T23:18:07.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": "12326", "name": "XML", "description": "View XML and parsing" } ], "description": "We should add an *inViewHierarchy* attribute to the XML markup, that when set to false, would indicate that the view is not to be added to the view hierarchy by Alloy. This would be useful in the case of markup for dialogs, or in the case of special properties that rely on references to titanium proxies. Properties like rightNavButton, leftNavButton, searchbar, etc... More details on these properties can be found in ALOY-382. ", "attachment": [], "flagged": false, "summary": "inViewHierarchy markup attribute", "creator": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "230371", "author": { "name": "fokkezb", "key": "fokke", "displayName": "Fokke Zandbergen", "active": true, "timeZone": "Europe/Amsterdam" }, "updateAuthor": { "name": "fokkezb", "key": "fokke", "displayName": "Fokke Zandbergen", "active": true, "timeZone": "Europe/Amsterdam" }, "created": "2012-12-07T07:28:25.000+0000", "updated": "2012-12-07T07:31:34.000+0000" }, { "id": "230381", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "@Fokke, you make a good point that by simply adding the views under that they are automatically not in the view hierarchy. I wanted to have the {{inViewHierarchy}} attribute to allow structuring as in ALOY-382, but perhaps abiding by the XML view hierarchy convention would be a bit \"purer\".", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-12-07T14:06:51.000+0000", "updated": "2012-12-07T14:06:51.000+0000" }, { "id": "230383", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Let's continue without it, using the modified structure in ALOY-382. This can be revisited if there ever is an additional need that can not be handled by simply making the UI components a child of ", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-12-07T14:52:01.000+0000", "updated": "2012-12-07T14:52:01.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }