udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Problem:    When working in an Alloy project, it is very common for me to work on a <file>.xml, <file>.tss, <file>.js simultaneously. If the project is large and has many files it is very difficult to find the same file_name in all the relevant folders and requires a lot of scrolling.  To simplify navigation and discovery of the files, maybe we can have a right-click menu that allows the developer from the <file>.xml to launch the relevant JS and TSS files?"
Answer: 339702.0

User story: "Before starting to work on debugging local Node.ACS projects (TISTUD-2814), we would like to first investigate if we could get debugging a regular node.js app to work using the steps described in https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger. Once we determine it is a feasible approach, we could then break down the tickets for implementing the feature.  "
Answer: 17474.0

User story: Add formatting support to TSS files after parser is created. We could copy from JSON formatter and extend.    Here is an example of formatted TSS file:    {code}  "Window": {   backgroundColor: "#fff"  },  "Label": {   width: Ti.UI.SIZE,   height: Ti.UI.SIZE,   color: "#000",   font: {    fontSize: 20,    fontFamily: 'Helvetica Neue'   },   textAlign: 'center'  }   {code}  
Answer: 20490.0

User story: "The action will invoke a wizard that contains the same fields the packaging launch configuration tab has (TISTUD-3262) except for the project field.  "
Answer: 47675.0

User story: "The action will create launch shortcut based on the launch configuration defined in TISTUD-3258 and install the Tizen app on device. The menu should only appear when the Tizen platform is enabled in project's tiapp.xml.    "
Answer: 44823.0

User story: "The action will create the launch shortcut for the corresponding launch config from TISTUD-3257 and directly install the app on Tizen emulator without an additional wizard. The menu should only appear when the Tizen platform is enabled in project's tiapp.xml.  "
Answer: 46953.0

User story: "The launch configuration tab for now could contain just a project field and the distribution location. We will add more if more fields are required. See the screenshot for an example of our Android packaging's main tab.  "
Answer: 53385.0

User story: "Add support for the packaging command via the CLI extension.    {code}  titanium build --package --platform=[platform] [project.dir]  {code}    See https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on downloading and running Tizen-enabled CLI.  "
Answer: 44796.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We should try call "build" again when we've cleaned all our projects and build automatically is checked.  The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed.    {code}  titanium build [--platform=[tizen]] [--package] [--device] [--emulator] [--production] [--development] [--verbose [0-5]] [project-dir]  {code}    See https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on installing a version of CLI that supports Tizen.
Answer: 215880.0

User story: "{code:title=V2|borderStyle=solid}  titanium build --platform=[platform] --emulator=[emulator.name] [project-dir]  titanium run --platform=[platform] --emulator=[emulator.name] [project-dir]  {code}    See https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on downloading and running Tizen-enabled CLI."
Answer: 37447.0

User story: "The launch configuration tab will just have a project field unless additional options are needed. See the screenshot for an example of the corresponding launch configuration tab for Android."
Answer: 44804.0

User story: "Initially, the launch configuration tab could just contain a project field and an option to re-build project on launch. See the screenshot for an example of the Android emulator launch configuration tab."
Answer: 37462.0

User story: "The preference page node will be under Titanium, and the content will contain a field for the Tizen SDK location and a browse button. It should validate the path and generate TizenSDKLocator from it.    The Tizen SDK could be downloaded at https://developer.tizen.org/downloads/sdk.  "
Answer: 34786.0

User story: "The checkbox should only be enabled when user specified the Tizen SDK location in the preferences page and the selected Titanium SDK has Tizen platform support.  "
Answer: 42914.0

User story: "We should show Tizen as a checkbox in the deployment targets section of Titanium project creation wizard. The checkbox should only be enabled if user specified the Tizen SDK location in the preferences page and the selected Titanium SDK version has Tizen support.    Please see https://wiki.appcelerator.org/display/tools/Tizen+Integration for the doc on the Tizen-enabled CLI."
Answer: 42919.0

User story: "The action will create launch shortcut based on the launch configuration defined in TISTUD-3118 and install the app on IVI device. The menu should only appear when the IVI platform is enabled in project's tiapp.xml.  "
Answer: 218077.0

User story: "The action will create the launch shortcut for the corresponding launch config from TISTUD-3117 and directly install the app on IVI emulator without an additional wizard. The menu should only appear when the IVI platform is enabled in project's tiapp.xml.  "
Answer: 218160.0

User story: "The action will invoke a wizard that contains the same fields the packaging launch configuration tab has (TISTUD-3119) except for the project field.  "
Answer: 218171.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "{code:title=V2|borderStyle=solid}  titanium build --platform=[platform] --emulator=[emulator.name] [project-dir]  titanium run --platform=[platform] --emulator=[emulator.name] [project-dir]  {code}  "
Answer: 100932.0

User story: "Add support for the packaging command via the CLI extension.    {code}  titanium build --package --platform=[platform] [project.dir]  {code}  "
Answer: 218199.0

User story: We should try call "build" again when we've cleaned all our projects and build automatically is checked.  The platform does not support incremental builds, so that call should probably only happen when a 'clean-build' is performed.    {code}  titanium build [--platform=[ivi]] [--package] [--device] [--emulator] [--production] [--development] [--verbose [0-5]] [project-dir]  {code}
Answer: 100941.0

User story: "SDK Installation: improve Node.js detection and node module detection.    There are many ways to have invalid or unusual node.js environments, and we need to improve our detection and correction.    See related issues."
Answer: 120276.0

User story: "Steps:  1. Use Import->Git Repo as projects  2. Enter the github credentials and click validate    Expected result:  The login is successful and the UI is displayed as expected    Actual results:  A login success dialog appears. The user closes the dialog and the UI is displayed as logged in    The login message is unnecessary since the UI reflects that the login was successful. If there was an error with the login, it should be displayed as an dialog error"
Answer: 100363.0

User story: "Node.js: update to v0.8.17.    Current hosted version is v0.8.14.    Minimum supported is: v0.8.13    See story for more information: TISTUD-3171"
Answer: 5653.0

User story: "Node.js: update to latest version.    Node.js Install: http://nodejs.org/  Titanium Docs: https://wiki.appcelerator.org/display/guides2/Titanium+Compatibility+Matrix#TitaniumCompatibilityMatrix-Node.js    We need a mechanism to test new Node.js versions:    1. Manual testing.  2. Staging environment.  3. Update studio validation for minimum Node.js version."
Answer: 6938.0

User story: "h3. Issue    Cannot select or add provisioning profiles in Studio    This issue is related to https://jira.appcelerator.org/browse/TISTUD-3064    The customer has the latest stable version but is still having the same issue.    We have already tried the following:    1. Revert studio to old version and then upgraded. Also tried the nightly build.  2. Reinstall Studio  3. Downloaded new profile  4. Also, checked for openssl modules as per this blog http://developer.appcelerator.com/blog/2012/12/titanium-studio-3-0-1.html     Will attach the log file soon."
Answer: 35147.0

User story: "After project templates for Denso are defined and created, we will need to include them in the Denso version of Titanium Studio.  "
Answer: 495653.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In alloy 0.3.4, the following format will generate the model appropriately for all supported adapters types: (sql, properties, and localStorage):    {code}  alloy generate model NAME ADAPTER_TYPE col1:type1 col2:type2 ...  {code}    so for example, a sql model would be generated like this:    {code}  alloy generate model myModel sql name:string value:integer  {code}    However, we currently call "alloy generate model myModel col1:type1 ..." Need to add "sql" after the model name. For the other adapter types, we are inserting the type correctly, so just need to fix for sql.    
Answer: 1438.0

User story: "The current instructions state to use the Help->Install New Software option for installing into an existing Studio. This has problems because they are most likely trying to update the RCP version, which is confusing to update. We need to update the instructions to be:    1. Add the update site to Preferences->Install/Update  2. Use Help->Check for updates"
Answer: 17673.0

User story: "The epic for adding code processor to Studio as a validator and showing annotations based on its output is captured in TISTUD-3112. We will need to create individual tickets for the workflow."
Answer: 233780.0

User story: "As a mobile developer I want to be able to quickly take the design that the UI designer or business analyst made and turn into code.    Currently I have to code it by hand and that is time consuming, plus I may miss some details.    Taking the image and auto converting it to alloy code will reduce the development time and ensure that the design is exactly what was requested.    (This can be done through photoshop, visa, or other mockuping tools.)    Choose 1 to start with but keep in mind that we will want to expand it later.    -Lower priority would be to be able to upload the image again and just create the changes between the 2 images.  But not for version 1.    For more detail please see https://wiki.appcelerator.org/display/tools/Design2Code+Use+Cases  "
Answer: 537935.0

User story: "The launch configuration tab for now could contain just a project field and the distribution location. We will add more if more fields are required. See the screenshot for an example of our Android packaging's main tab.  "
Answer: 239546.0

User story: "The launch configuration tab will just have a project field unless additional options are needed. See the screenshot for an example of the corresponding launch configuration tab for Android."
Answer: 239548.0

User story: "Initially, the launch configuration tab could just contain a project field and an option to re-build project on launch. See the screenshot for an example of the Android emulator launch configuration tab."
Answer: 239550.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In the Denso version of Titanium Studio, add a checkbox "Automatically enabled automotive extension for this project" to the project creation wizard. It should be enabled and auto-selected when IVI platform is selected. When selected, Studio will automatically include the automotive module in project's tiapp.xml.    
Answer: 18639.0

User story: "Host Staging dashboard on a url in addition to staging dns.    This will allow the user to test the master/staging dashboard without connecting to the staging server.    This would be on par with the other dashboards, which have unique urls.    This will aid testing and validation.    Proposed Usage:    1. Edit TitaniumStudio.ini file to include staging/master dashboard.  2. Open Titanium Studio in a live production network environment.  3. Open Dashboard.    Result:    Staging/master dashboard loads without the need to connect to the staging dns."
Answer: 122825.0

User story: "Allow user to query dashboard version using Studio UI.    This will aid testing and validation.    Proposed Usage:    1. Open Titanium Studio.  2. Open Dashboard.  3. <Perform some action to display the dashboard version/url.>    Result:    User can validate dashboard specified in TitaniumStudio.ini file."
Answer: 122842.0

User story: "Build path entries are returned as a Set from the BuildPathManager, so order is not guaranteed. However, order is important because it determines the order we query the indices for entries. This order should be retained when we persist the entries, load them, iterate through them.    This would also involve updating the build path entry UI to use an ordered list, allowing users to move entries up and down in the list."
Answer: 32702.0

User story: I was running my dev environment and noticed that while indexing modules (see screenshot), my log was filled with calls to:    !ENTRY com.aptana.core 1 0 2012-12-21 09:14:41.326  !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process:  Process: "/usr/local/bin/npm" "config" "get" "prefix"  Working directory: null  Environment: {APTANA_VERSION=3.1.0.qualifier, Apple_PubSub_Socket_Render=/tmp/launch-lARzbP/Render, Apple_Ubiquity_Message=/tmp/launch-YOCWjK/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/<USER> LANG=en_US.UTF-8, LOGNAME=<USER> PATH=/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin, PWD=/Applications/eclipse_42/Eclipse.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-puYPOq/Listeners, TMPDIR=/var/folders/zw/n1jmn7z52yb6x0rfd2cn5bgr0000gq/T/, USER=<USER> __CF_USER_TEXT_ENCODING=0x1F7:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI.java}    This seems like something we can cache before the indexing job happens and re-use it. Making this call every ~300ms seems overkill
Answer: 25377.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The Alloy templates should be displayed as follows (no beta description):    Alloy    The tag/category and the template title/description should also no longer include the word "beta"
Answer: 1622.0

User story: "The BlackBerry packaging is done via a launch-configuration. However, since it's missing a tab-group implementation, it's not being displayed in the Run configurations, so a user has to go through the packaging wizard every time."
Answer: 22496.0

User story: Currently there is a single IP address box that is used for both device install and running in simulator. It is a pain to switch the address between simulator and device.    Please have 2 boxes 1 for simulator and a second for device. For device have an initial value of "169.254.0.1"
Answer: 4411.0

User story: For singing a BB10 app the CLI command needs just a single keystone password.    The user will prior to using Ti Studio be expected to have installed the BB NDK and registered their signing keys. The command below is what a user will have run the STORAGE_PASSWORD    "./blackberry-signer -register -csjpin SIGNING_PIN -storepass STORAGE_PASSWORD PATH_TO_RDK_KEYS.csj PATH_TO_PBDT_KEYS.csj"    
Answer: 1139362.0

User story: "The idea is to have no Mobile Web related code or constant in com.appcelerator.titanium.mobile and com.appcelerator.titanium.mobile.ui plugins. The subtasks will capture the work needed in the various areas to make this happen.  "
Answer: 42851.0

User story: "After the discussion with Tony, Max, and Shalom, we decided the first action item is to define the source map API contract for connecting the original alloy source with the generated code. In the wiki page, we should spell out the specific calls (with parameters) Studio will make to alloy and the expected return values. There should be code samples for each call, and if the returned value is a JSON string, the expected syntax of the string should be clearly stated. This will allow us to decouple the work on Studio and Alloy sides, and we will return to modify the page if additional contract is needed or existing ones should be amended.  "
Answer: 9725.0

User story: Steps To Reproduce:    1. Go to File>Import>General>Existing Folder as NewProject>Next to import a project (attached zip).  2. Run Project in debug mode using iphone simulator.    Actual:     "Requested SDK version does not have an assigned commands-handler." error message appears.  On opening tiapp.xml and saving same resolves the issue.  On windows 8 "Null Pointer" exception appears.  refer snapshot    Expected:     Project must be imported and run without any error.
Answer: 13558.0

User story: "To provide better troubleshooting for provisioning issues, we need to log more information about the available provisioning profiles and the process of loading the profiles from the filesystem and the cache"
Answer: 4151.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "JSON uses text rule based scanners for parsing, partitioning and colorization.    This is a performance issue for larger files. JSON is very simple to lex/scan and using a JFlex based scanner for parsing at the least should be relatively straightforward."
Answer: 42940.0

User story: In order to monetize our platform and modules we would like "enterprise" modules to only work with the professional studio version.    Some new license scheme will have to be created in order to accomplish this
Answer: 3148.0

User story: "Similar to TISTUD-2944, where we updated the alloy update style sheet, we need to do the same for the modules update style sheet. Right now the text in the module details is large and not consistent.    [EDIT]  The module JSON file should be updated to direct a release-notes page. This page should later be read by the release notes system and be applied with the same stylesheet we use for the rest."
Answer: 39738.0

User story: "The itunes version check is no longer necessary, since the requirement of v10 is standard, and the platform no longer requires the itunes version check.    Studio needs to remove the version check from the Publish iOS simple and full wizards"
Answer: 27468.0

User story: "Release Notes with Studio RC build will be very useful in situations where major changes are being made.  Say for example: the node.ACS being made external plugin.  "
Answer: 322210.0

User story: "Integrate CLI functionality into Studio UI for Titanium SDK updates.    The CLI has many features such as:    1. being able to download any stable sdk  2. being able to download latest version from any branch"
Answer: 162546.0

User story: We would like to deprecate rhino and discourage people from using it, and the suggestion is to disable the "Android Runtime" combo-box in tiapp.xml when the selected SDK is 3.0.0+. User could still go into the source and change it manually, and we won't prevent them from doing that.  
Answer: 2759.0

User story: "Update CLI calls to reflect intended use for iOS.    pass in --platform ios instead of 'iphone/ipad'  pass in --device-family every time"
Answer: 534493.0

User story: "In Windows 8 the Node.ACS menu options are not added to the file menu in the Studio (extended) perspective. They exist and are functional in the default Studio perspective.     Steps to reproduce:  1. Start studio with Node.ACS plugin installed.  2. Enter the default studio perspective ( Window > Open Perspective > Studio )  3. Look at the File menu.  4. Change to the Studio (extended) perspective ( Window > Open Perspective > Studio (extended) )  5. Look at the File menu.    Expected Results:   The two File menus should match.    Actual Results:  The Node.ACS commands are missing.    Note: This does not happens for the App Explorer context menu."
Answer: 326253.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Steps to Reproduce:    1. Create Titanium Module Project.  2. Select Publish > ...    Actual Result:    There is the "Run Web Deployment Wizard..." option.    Expected Result:    The web deployment wizard option does not apply to Titanium Module project and should be filtered out.  
Answer: 1427.0

User story: "Studio added logic that runs titanium select before any CLI operation that specifies an SDK, to work around an issue with the CLI. That issue has now been resolved in TIMOB-11883"
Answer: 282556.0

User story: "Studio needs to adopt the CLI command to replace prereq.py and provisioner.py (provisioning profiles).    The command is: titanium info -o json -t ios    It returns certficates and provisioning profiles, as well as information used by prereq.py (keychains, wwdr, etc)    Only data missing is the itunes version, see referenced ticket "
Answer: 282588.0

User story: "After we have alloy samples from ALOY-412, we should integrate them in Samples view, with Alloy as a top level category and individual samples underneath.  "
Answer: 468081.0

User story: The command to call "acs list" under a project dir to show an app info has been deprecated; instead, we should run "acs list <appname>". The acs change is in the latest git.    We should verify the syntax we call to "acs list" in Studio and make appropriate changes.  
Answer: 3851.0

User story: "Steps To Reproduce:  1. Build an application with CLI enabled    Actual:  Can't tell whether CLI was used    Expected:  To be able to log whether CLI is enable or disabled"
Answer: 289634.0

User story: "Titanium handles require slightly differently than Node/CommonJS. The value could be a module id for a native module or CommonJS module that exists int he project or the SDK itself. We need to be able to handle these cases."
Answer: 25917.0

User story: We should be able to index NodeJS/npm install's node modules. We can query npm for the install paths and then index all the modules we find underneath.    We'd need a way to attach these loadpaths/indices to a project. Our current load provider support re-uses the index for the project, which isn't really correct - and it is assumed to return a lit of files to index, which we can do, but it may be easier to just return the directories.    Ideally the NodeJS install as a whole would be a single "entry" (like a JRE/KDK for JDT) and it resolves to it's various paths and is indexed to it's own index/indices. Then the projects just add them to their list of indices to search/query.
Answer: 28694.0

User story: "We'd like to provide CA for alloy APIs. We need to look into whether we can simply index the alloy source with the JSDuck comments to do so. We may need to extend our SDoc support to cover more tags provided by JSDuck (https://github.com/senchalabs/jsduck)     If we can simply index the JS files with the JSDuck comments, then we can pretty easily fold this into our general node modules indexing, since the source will be available in the alloy module (/usr/local/lib/alloy/Alloy)"
Answer: 30234.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "To make things easier for users we should offer to download and unzip the NodeJS source for them. That way they don't need to google it download it and then hook up the location."
Answer: 20313.0

User story: Once the user is able to set the path to the NodeJS source folder we need to be able to index it to get the details of the core modules under lib. These are straight JS files, so we can index them using our current mechanism. This should be treated like a 3rd-party library that can be attached to JS projects (much like an external JAR for JDT, possibly even just attaching "Node" to a project entirely which would be like attaching a JDK so it attaches the core modules form source and the $NODE_PATH from the binary install).
Answer: 24476.0

User story: "NodeJS's core modules are defined in JS files under the lib subdir of the Node source package. This is not installed when the binary is. If the user has a source package on their system, we should allow them to point to it so we can look up those core modules.    This would involve setting up a preference constant to use as the key to store the path, as well as the UI fields to set/edit it in the Node preference page (which already exists and has a field for setting the path to the binary install)."
Answer: 4273.0

User story: "When creating a new Node.ASC project, the Studio creates a new Server setting in the Servers view.    # When deleting the project, the server is there to stay.   # When launching the server via the Run menu, and then deleting the project, the server is still running.    Expected:  Shut down the server and remove it when needed."
Answer: 12909.0

User story: "When creating a new Node.ACS project, a new server is being added to the Servers view.    # Create a new Node.ACS project.  # Open the Studio's Servers View.  # Click to edit the port number for the newly added server.  # Launch the project's 'Run -> Local Node.ACS Server'.    Result:  The console indicate that the server is running. However, the port is not the same as the one that was defined.    Changing the port again and re-launching does not make any difference. The Server settings and the server that runs seem as un-connected.  "
Answer: 12912.0

User story: "Currently, when a Node.ACS project is being created, the Studio adds a local server settings in the Servers view.    # Create a new Node.ACS project.  # Open the Studio's Servers view.  # Delete the created server.  # Click the project and select the 'Run' option to launch a 'Local Node.ACS Server'    The launch happens, even without the server in the servers view, and no server is being recreated.    Expected:  A recreation of the local server."
Answer: 12917.0

User story: "Add a link in dashboard to install Node.ACS into Studio (need a mock up). We also need to check a portal action exists to install plugins from a specific url.  "
Answer: 189181.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Titanium SDK's usage of {{require}} is slightly different than what NodeJS/CommonJS uses as it has an implicit base path of {{<project>/Resources}}    An example:  {code}  var r = require('http');  {code}    In Node, we'd load the core 'http' module. In Titanium we'd look for {{<project>/Resources/http.js}}. Additionally, Titanium merges the platform-specific subfolders of Resources. So...  {code}  var taskWindow = require('ui/TaskWindow');  {code}    Would look up {{Resources/iphone/ui/TaskWindow.js}} and {{Resources/android/ui/TaskWindow.js}}    Additionally you can specify a native Titanium module id to load."
Answer: 23205.0

User story: "The current version we host is 0.8.3. We should update to the latest 0.8.14 to avoid issues like NODEJS-493."
Answer: 22.0

User story: We need to provide content assist for the list of property names for a given element in TSS files.    {code}  "Window": {      backgroundColor: '#fff'  }  {code}    {{backgroundColor}} is the token we'd suggest.    We should take the string which is the key of the surrounding object, convert it to a fully qualified type name (see TISTUD-2783), then query the list of properties for that type.    If the string is not the name of a type, but is a class or id, we need to query the class/id index from the view files to resolve it to the type it is hanging off.
Answer: 110619.0

User story: We'll need to begin indexing alloy's XML files to record the list of classes and ids used. This will then be used for TSS code assist.    The involves adding a new IndexBuildParticipant for XML files. In the participant we may filter when we activate to only projects with alloy nature and files under app/views/. The participant would parse the XMl file and traverse the AST to get the class/id attribute info.    When we record a class or id reference, we will likely also want to record the fully qualified type name of the element it is on.    {code}  <!-- index.xml -->  <Alloy>    <Window> <!-- implicit id of "index" -->      <Label id="myLabel"/>    </Window>  </Alloy>  {code}    In this case we'd record that index.xml has a Titanium.UI.Label with an id value of "myLabel". The type is required to determine the property list in TSS content assist, as well as content assist in controller JS. The type namespace mapping is the same as in TISTUD-2783.    Please note that the top-level widget (the child under the {{<Alloy>}} tag) in a view has an implicit id of the file's basename, so the top-level {{Window}} of index.xml would have an id of "index").
Answer: 30123.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We need to offer up content assist for the keys of the JSON-like objects in TSS files. This ticket specifically addresses offerring up the list of classes and IDs found in the view files.    {code}  <!-- index.xml -->  <Label id="myLabel"/>    // index.tss  "#myLabel": {      text: 'some text'  }  {code}    The {{"#myLabel"}} token is what we'd suggest. IDs use a {{#}} prefix like in CSS, and classes use {{.}}.    The list of classes and ids is found by querying the indexed values from TISTUD-2798.    app.tss should query all files. For other tss files we can limit the scope to just the associated view (same hierarchy and basename).
Answer: 109187.0

User story: We need to offer up content assist for the keys of the JSON like objects in TSS files.    {code}  "Window": {      backgroundColor: '#fff'  }  {code}    The {{"Window"}} token is what we'd suggest. The list of elements to suggest is the same list of types of elements we'd suggest in the XML view files from TISTUD-2783. Please see that ticket for the list of types.
Answer: 106370.0

User story: "Once we have a proper parser we can use it to highlight syntax errors. This will involve creating a build participant that simply grabs the context's AST, asks for the SyntaxErrors and hooks them as problems to the BuildContext. See {{JSParserValidator}}"
Answer: 100610.0

User story: "Once we have a TSS editor, we'll need to hook up coloring. This involves setting up partitions, a partition scanner, and token scanners for the partitions. We can look to {{JSONSourceConfiguration}} as the example to copy and slightly modify. We can likely re-use the lexer/grammar that the TSS parser uses."
Answer: 102074.0

User story: "Once we have a TSS grammar and lexer, we need to create a TSS editor and associate it with *.tss files. We should remove the old association between JSON and *.tss."
Answer: 90456.0

User story: "We need to generate a TSS Parser. See the PEGJS grammar here: https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs    We'll need to generate an LALR grammar from that and then use beaver to generate a parser. We may be able to simply copy the JSON.grammar and modify slightly to handle the changes that alloy introduces."
Answer: 98270.0

User story: "We need to generate a TSS lexer to feed the parser. See the PEGJS grammar here: https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs    We'll need to extract a JFlex TSS.lex file from the rules there."
Answer: 98267.0

User story: "We need to provide Content Assist specific to Alloy view XML files. They use a standard *.xml file extension. We'll need to add an Alloy XML Editor and hook up a specialized content assist processor so that for *.xml files in an alloy project (under the app/view/ tree) we have the Alloy-specific CA hooked up."
Answer: 18764.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Alloy uses XML files to define views. We should provide content assist for the attributes of elements.  {code:xml}  <Alloy>    <View class="my_class" id="myLabel" onClick="" />  </Alloy>  {code}    For attribute CA we need to look up the properties for the given element's type in the JS index, as well as the events.    To look up the type name, we take the element name as the type name and determine the namespace prefix. The default prefix is {{Titanium.UI.}}. If there is an {{ns}} attribute, use it's value as the namespace. Alloy will provide us with the exceptions to the rule for namespace mappings.    e.g.  {{View}} -> {{Titanium.UI.View}}  {{Label}} -> {{Titanium.UI.Label}}  {{<View ns="Ti.Map"/>}} -> {{Titanium.Map.View}}  {{Toolbar}} -> {{Titanium.UI.iOS.Toolbar}}    The list of attribute name proposals is:  # The list of properties of the type  # The list of events of the type. Each event name is transformed to be {{"on" + Character.toUppercase(event.name().charAt(0)) + event.name().substring(1);}} - i.e. "click" -> "onClick"  # The common set of attributes: {{class}}, {{id}} and {{ns}}.    It should be noted that the {{Alloy}} element may only have {{class}} and {{id}} attributes. The special {{Require}} element may have {{class}}, {{id}}, {{src}}, and {{type}}.
Answer: 18775.0

User story: "Alloy uses XML files to define views. We should provide content assist for the elements (tags).  {code:xml}  <Alloy>    <View />  </Alloy>  {code}    The list of elements is defined as Titanium.UI.* types. There will likely be a need to further refine/filter the subtypes that make sense. Additionally Alloy uses some non-standard namespace mappings for some elements, so there are tags which are not Titanium.UI.* such as {{Toolbar}} which is mapped to {{Titanium.UI.iOS.Toolbar}}.    Lastly, the root tag is {{Alloy}} and you can have {{<Require>}} tags."
Answer: 15678.0

User story: "Node.ACS: Titanium Project Service Publish missing Web Deployment Wizard option. See screenshot.    Steps to Reproduce:    1. Create Titanium Project.  2. Add New Node.ACS Service to project.  3. Select Publish > ...    Actual Result:    There is no 'Run Web Deployment Wizard...' option with the other ACS options.    Expected Result:    Titanium Project Services should have same deployment options as Node.ACS Projects. 'Run Web Deployment Wizard...' should appear for both."
Answer: 17365.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Allow studio to recover from failed node.js module updates.    For example:    {code}  I updated the cli at the same time as updating studio and the cli update failed, resulting in a missing /usr/local/bin/titanium alias. Any further runtime-related studio commands started to fail (run on simulator). Checking for updates showed no updates available.  {code}    Can we change our node module detection to include the alias?    Steps to Reproduce:    1. Fail a node module update (or just delete the node module alias).  2. Check for Titanium updates.    Actual Result:    No updates found. Build scripts fail with missing node module alias errors.    Expected Result:    Updates found."
Answer: 80506.0

User story: "We want the base Titanium Studio continue to include Node.ACS feature, but have a separate update site defined for Node.ACS so it could update on its own without updating the whole Studio. We should also verify it will still work when later on we update Studio overall.  "
Answer: 7134.0

User story: "Based on the new image attached to TIMOB-10886, update the default image for samples and templates. Marking this for 3.0.0, as we'll need a new Studio build to get this into user's hands."
Answer: 81151.0

User story: "The below changes are required in the Titanium update wizard to improve the user experience -    1) Change the wizard image on the top to look like an installer image.  2) Add user id field to the password sudo page.  3) Gray out 'Titanium SDK' field in the Installer main page to indicate that it is mandatory and as the user can not de-select it. Also, the text of NodeJS should dynamically switch to 'NodeJS (required)' if the user selects any of components (acs, alloy, or cli)."
Answer: 13088.0

User story: "Add support for the packaging command via the CLI extension.    V1:  {code}  project-dir/build.py  Working directory: [project-dir]  {code}    V2:  {code}  titanium build --package [project-dir]  {code}  "
Answer: 2486036.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "While doing Windows 8 testing I was running TISTUD SDK Acceptance Debugger I see the output to the console but the debug session does not break on the breakpoint.    Steps to reproduce (from test):  1. Enter code in Titanium Project app.js:   {code}  Ti.API.trace('Ti.API.trace');   Ti.API.debug('Ti.API.debug');   Ti.API.info('Ti.API.info');   Ti.API.warn('Ti.API.warn');   Ti.API.error('Ti.API.error');   Ti.API.info('Ti.include.module.js');   Ti.include('module.js');   Ti.API.info('require.module');   require('module');   Ti.API.info('Ti.UI.Window.url');   var win = Ti.UI.createWindow({url:'module.js'});   win.open();   {code}  2. Enter code in Titanium Project Resources/module.js and add breakpoint on line:  {code}   Ti.API.info('module.js'); // breakpoint   {code}  3. Run in Debug in Simulator or Emulator.    Expected results (from testcase):  All Messages should log to console. The breakpoint should be hit for all scopes (i.e., include, require, and url).    Actual results:  Messages are output to console, but the session does not break on the breakpoint."
Answer: 1037.0

User story: "Steps To Reproduce:  1. Fresh Install studio 3.0  2. Goto Configure tab. And Observe Mobile Web Image with Question Mark(?) sign with details to configure on right.[Refer Screenshot]  3. Now click on iOS or Android Image. (Pls. do not change any other settings)  4. Now click on Mobile Web image once again.    Actual: Image refreshes without any change in configuration settings, thereby removing Question Mark image.  Expected: (?) image must not disappear on toggling between images."
Answer: 378506.0

User story: "Do the same thing that was done in previous demo"
Answer: 107015.0

User story: "Hook up to content assist"
Answer: 105675.0

User story: "Content assist that shows the generic codes would be a good way to filter codes."
Answer: 105680.0

User story: "Dashboard > Configure > MobileWeb > 'here' opens General Browser Preferences instead of MobileWeb sdk runtime preferences."
Answer: 28866.0

User story: "Allow users to update or install studio without dead links or incomplete updates."
Answer: 10671.0

User story: "Titanium update wizard's progress monitor dialog does not have any impact after the cancel button is pressed - as we do not have support either rollback or partial installations at this moment.    So, the progress monitor dialog should not be cancelable as there is no cancel action associated with it."
Answer: 394921.0

User story: If the Titanium CLI outputs "Hello!\b?", Studio should show "Hello?", not "Hello! ?".  
Answer: 250412.0

User story: "The appdirect call to return the module updates info now contains module guids so we can map the modules to the installed modules. Unfortunately the current portal call to retrieve module info does not contain guids. The call needs to return multiple guids for modules with both iOS and android components, since the guids may differ in those instances."
Answer: 15801.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: I'm not sure if CLI wants us to be setting global values in config to match or not, but I'm guessing by default we should sync up the values for things like Android SDK path. If a user sets the path in Titanium Studio we should pass that along to the CLI to store as well. We may also need to do the reverse on startup - look up what CLI has in it's config and push that into our prefs (with some sanity check to see if the value is valid - or at least "more valid" than what we have set).
Answer: 353131.0

User story: "This is not a regression issue.  Steps To Reproduce:  1. Download 2.1.2 studio installer and upgrade it to 3.0  2. Delete plugin files from /usr/local/lib/node_modules folder.  3. Go to Help > Check for Titanium Updates. From the window install, alloy, CLI and acs updates.    Actual: After successful installation of all plugins, File > New > Node.ACS option does not appear.  Expected: File > New > Node.ACS option must appear."
Answer: 134286.0

User story: "On a clean install of Studio, the user is prompted to install NodeJS. For a majority of Studio users, NodeJS is unfamiliar to them and its association with Studio. We should provide more context on why we're installing NodeJS - It's a requirement for CLI/Studio"
Answer: 89368.0

User story: During a clean install, I got the following errors/windows for Studio (see screenshot). The errors complain about "NPM not installed", which means nothing to the new user, and there's a prompt for install NodeJS (which would install NPM).    What should happen is the Alloy and Node.ACS jobs should check for NPM/NodeJS, if it's not installed, it should be able to register as listeners to a NodeJS notifier. When the NodeJS install is complete, it can notify the listening jobs to restart their installations
Answer: 4352.0

User story: Currently we're checking Titanium CLI for update at startup, but not for Alloy and Node.ACS, so user would have to manually run "sudo npm install ..." from command line to update. We should add them to the check-for-update process as well.  
Answer: 1459.0

User story: "The Studio now has a 'Clear' option in its main preference page. The user can reset all the 'do not show again' hidden messages and have them re-appear when needed.  We should consolidate all the areas where we have a dedicated preference for a specific message, and use this preference key to store and check for the property.  (for example, the NodeACS deploy menu shows one of those messages)    See DialogUtils#openIgnoreMessageDialogInformation"
Answer: 52056.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Got a request from CLI team to add two optional attributes to the plugin element.  "
Answer: 15360.0

User story: "With the new splash screen layout, there is blank empty space to the right hand side of the splash screen when logging in. We should move the progress bar to that area to make it more equally spaced"
Answer: 64.0

User story: We currently have a script living under the SDK's iphone/provisioner.py that loads a provisioning profile given a filepath argument to the .mobileprovision file.  There doesn't appear to be an equivalent in the new CLI for this, though {{titanium info}} does list provisioning profiles by type ("development", "distribution", "adhoc").
Answer: 373129.0

User story: "This is not a regression bug.    Steps to reproduce:    1)Open Titanium Studio.  2)Open/Create  a Titanium Mobile project -> Android   3)Open context menu by right clicking on that project in Titanium Studio.  4)Observe that debug as -> 'android device' icon is unavailable.     Actual result:  In context menu list, debug as -> 'android device' icon is unavailable.    Expected result:    In context menu list, debug as ->'android device' icon should be available.    Screenshots attached.  "
Answer: 533678.0

User story: Add a checkbox to the iOS debug on device wizard to "Run in the background". Upon finish, the launch configuration will behave similar to performing an iOS debug on device launch shortcut
Answer: 9955.0

User story: "The page should link or contain the following pieces of information:  -Debug on Device network types  -How to install app (using iTunes sync, manual install in iTunes, manual install in Xcode"
Answer: 380230.0

User story: "When performing the debug on iOS device using the wizard, the status will be displayed as the app is built and installed. When the 'Start app' step is the current step, we need to remove the step control and replace it with an animated gif of an app starting on a device."
Answer: 642624.0

User story: "While in the debug perspective, the file > New menu does not contain the usual options (Titanium Project, Titanium Module, Web Project, etc.).    Steps to reproduce:  1. Open Titanium Studio  2. Switch to the Debug Perspective (Window > Open Perspective > Debug)  3. Open the New Menu Dropdown (File > New)    Expected result:  This menu should match the Studio Perspective's choices.    Actual result:  Only the generic Project and File choices appear."
Answer: 426732.0

User story: "Description:  Unable update to latest Nightly version of TiStud.    Screenshot is attached.(updating_failed.png)  log is attached. (log.txt)  details from error message is attached.(error_details.txt)    Steps to reproduce:  Update Studio to latest (3.0.0.201209211310) Nightly version (http://preview.appcelerator.com/studio/ )    Actual result:  Getting Error message.    Expected result:  Update successful."
Answer: 185.0