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: "The packages installer provides an ability to add plugins, in order to handle the pre-requisites of Studio. Building the packages plugin from XCode takes a couple of seconds now.     - Find out the command to build the packages plugin to integrate into installer.  - Add a <USER>job to build the plugin bundle."
Answer: 4362.0

User story: "As the JSON references are spread out everywhere, we need to consolidate all the required classes from socketio into json.simple. Also, we need to refactor the referencing classes to make sure they point to json.simple now."
Answer: 64863.0

User story: "Trials as a concept is being removed from Dashboard for its 3.0.0/On-Demand release.      Studio is calling the api/v1/user/trial endpoint to retrieve information about the org's trial status.    For the time being, it will return a benign payload, but the call to it should eventually be removed."
Answer: 4598.0

User story: "Importing an existing AppC studio into it is created with the Project Natures of Alloy (primary) and Web. It needs to be Alloy (primary) and mobile. "
Answer: 1238.0

User story: "This ticket is to encapsulate any changes needed by Studio to support APPTS-6273. Some environments may not have an ACS/Node.ACS, so the Studio use cases should take this into account."
Answer: 70903.0

User story: "In case Node.ACS CLI is not installed on the machine, then we would like to defer its installation until it is actually required. So, we should not prompt to install during the update wizard dialog either during the startup or even if the user check for updates.    However if it is already installed on the machine, then we do need to check for its updates."
Answer: 17475.0

User story: "In case Node.ACS CLI is not installed on the machine, and if the user tries to publish a acs app, then Studio should prompt for Node.ACS CLI installation before we publish the app."
Answer: 31480.0

User story: "In case Node.ACS CLI is not installed on the machine, and if the user tries to launch an existing acs app onto local server, then Studio should prompt for Node.ACS CLI installation before we launch the project."
Answer: 22700.0

User story: "There are many cases were specific certs or keys need to be generated in order for features to work or builds to be created.    Appcelerator Studio should provide ways to simplify these tasks for the end user.    EX -  * Google Map Key (SHA1)  * Google Keystore  * Apple Certs for development and distribution builds  * etc."
Answer: 180326.0

User story: "As every user doesn't use Node.ACS projects, there is no need to install node.acs CLI until the users are actually working with node.acs projects. So, if node.acs CLI is not installed, and the user attempts to create a node.acs project, then we should prompt and install acs CLI before we create the project."
Answer: 28599.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've had to upgrade the mac build agent so we can sign using v2 signatures on Mac 10.9.5+. As a result, our build agent needs some setup work done to get it re-signing the installers properly again, as right now it's silently failing.    See TISTUD-1952"
Answer: 6125.0

User story: "Looks like there's new syntax (import and export) and new behavior for this.    http://www.2ality.com/2014/09/es6-modules-final.html"
Answer: 2193961.0

User story: We're getting killed with customer issues getting the proxy set up. The easiest fix for this is to bypass auth and then just set the proxy provider to "native" and restart. But we should already be using the native provider by default. Why isn't that working? Is it just not getting loaded? We need to figure that out and fix it.
Answer: 28768.0

User story: "The 360 Appcelerator Services can be enabled while creating projects or from TiApp.    In either of those situations, we need to verify for the organization membership plan and only then let the Test and Performance services to enable if the membership plan has privileges."
Answer: 40386.0

User story: "The membership plans are associated with the organization. So when Studio receives information about organization, it contains the details of membership plan name/id associated with that organization.    So, the organization model should parse and store the details of the membership plan, as all the services can query for the plan and figure out enabling the services."
Answer: 32093.0

User story: "The membership plans are associated with organization rather than with the user. So, if the user is part of multiple organizations, then we need to determine whether they have access to Test/Performance services by looking at the membership plans of all their organizations.    If any of the membership plan is eligible for Test/Performance services, then we should allow them to install or update these services."
Answer: 50757.0

User story: "Add a hyperlink detector to navigate from keys in JS to strings.xml definition."
Answer: 59350.0

User story: "Add a hyperlink detector to navigate from keys in TSS to strings.xml definition."
Answer: 61677.0

User story: "Add a hyperlink detector to navigate from keys in TSS to strings.xml definition."
Answer: 31787.0

User story: "Add a hyperlink detector to navigate from keys in JS to strings.xml definition."
Answer: 40139.0

User story: "We need to start indexing the usage of translation keys in JS files so we can support F3/hyperlinks for navigating the relationship with their definitions in strings.xml files.  See https://github.com/FokkeZB/ti-i18n/tree/master/test/source"
Answer: 29980.0

User story: "We need to start indexing the usage of translation keys in Alloy TSS files so we can support F3/hyperlinks for navigating the relationship with their definitions in strings.xml files.  See https://github.com/FokkeZB/ti-i18n/tree/master/test/source"
Answer: 13400.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: "Once we've moved to 64-bit builds in the installer and the ability to upgrade from 32-bit builds to 64-bit builds, we can remove generating 32-bit builds on Mac entirely."
Answer: 17278.0

User story: "Since we plan to phase out the 32-bit builds of Studio, we should move the installer/DMG to include the 64-bit build."
Answer: 686.0

User story: "From Mountain Lion onwards, OS X was a full 64-bit operating system.    https://discussions.apple.com/message/22067745    We currently build and ship a 32-bit Titanium and Appcelerator Studio, but it would be good to deprecate that build and instead only build the 64-bit version.    Is it possible to take an installed 32-bit Appcelerator Studio and upgrade it to the 64-bit version without needing a re-install?"
Answer: 181495.0

User story: "In XCode6, the list of simulators are different from the traditional way. It has simulators as iPhone 4s, iPhone 5, iPhone 6, iPad Retina etc for each iOS version. In case if the XCode supports 3 iOS versions, then it will show almost 23 simulators.    Having them to show all 23 simulators in one list will be confusing to the user. So, we need to categorize (through multi level menu) the simulators based on the version, similar to Simulator device menu."
Answer: 55774.0

User story: "I believe we can stop creating a 32-bit version of Studio (and only do a 64-bit version)    http://support.apple.com/kb/ht5444    I think we could actually get rid of it now, but it’s inconvenient to do so for a minor release:    http://www.everymac.com/mac-answers/os-x-mountain-lion-faq/macs-compatible-incompatible-with-os-x-mountain-lion.html"
Answer: 43297.0

User story: "Looking at Tony's screencast, Studio was less than helpful in terms of CA once trying to require the module and exposing the methods/apis. We need to investigate why it's failing to be useful here!"
Answer: 116912.0

User story: When an alloy element has multiple classes, it generates a warning saying "The class 'class1 class2' is not referenced in any style rules", and when a style in the TSS only appears in elements that have multiple styles, it generates a warning "Unused TSS class styling rule: .class1"    {code:xml}<Label class="class1 class2"/>{code}    ^^^ The class 'class1 class2' is not referenced in any style rules    {code:javascript}".class1": { color: "#F00" }{code}    ^^^ Unused TSS class styling rule: .class1
Answer: 4404.0

User story: "Since Titanium or Appcelerator Studio does not have explicit dependency on CoffeeScript plugins, they need to be pulled out from the RCP applications and a new update site should be made available to install the CoffeeScript plugins on top of RCP."
Answer: 33037.0

User story: "Once the user submits to publish the app, we need to invoke the AirWatch APIs to publish and parse the response to show the response back to the user."
Answer: 943.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: "Once the user inputs the credential details in the register dialog, it would have created a publish target based on the credentials. However, we need to authenticate the target based on the user input and return the appropriate error message."
Answer: 18285.0

User story: "Create a new register publish target dialog to allow users to input user/pwd/host/alias, similar to existing mobileiron register dialog."
Answer: 18288.0

User story: "Add a preference page to allow Add, Edit or Delete the AirWatch publish targets.    Though we have the basic infrastructure to create the pref page for publish providers, it might need to provide the table columns, label provider and publish target comparator."
Answer: 18290.0

User story: "test this again"
Answer: 1693317.0

User story: "When a crittercism module is enabled for a mobile app, Studio currently injects code into app.js to explicitly load the module.    The new crittercism module have the auto-load functionality and so, Studio no longer is required to inject the code into app.js file.    Since we force users to update the crittercism module to latest version at every startup, we don't need to provide the backward compatibility for the older versions of crittercism module."
Answer: 1711786.0

User story: "Nukona is a separate feature and one we don't ship in titanium by default. It should be moved out to its own repo so it doesn't constantly rebuild when we check in to titanium core. I'm not even sure it does anything right now."
Answer: 219.0

User story: "Testflight is a separate feature and one we don't ship in titanium by default. It should be moved out to its own repo so it doesn't constantly rebuild when we check in to titanium core."
Answer: 221.0

User story: "We currently have the openshift code in the titanium core repo. It has no dependencies on titanium at all right now (just studio3 core), and it's highly inactive in terms of development. We also don't ship it as part of titanium studio. We should just move it out to it's own repo so it doesn't constantly rebuild when we do checkins related to titanium."
Answer: 221.0

User story: "It appears that the OpenShift Jenkins builder is no more. We should re-createdit."
Answer: 8024.0

User story: "As part of 3.3.0 release, Merge titanium_studio_dashboard repo from development to release and master"
Answer: 8904.0

User story: "As part of 3.3.0 release, Merge titanium_studio_360 repo from development to release and master"
Answer: 8905.0

User story: "As part of 3.3.0 release, Merge titanium_studio_rcp repo from development to release and master"
Answer: 8906.0

User story: "As part of 3.3.0 release, Merge titanium_studio repo from development to release and master"
Answer: 8906.0

User story: "As part of 3.3.0 release, Merge Studio3 repo from development to release and master"
Answer: 8906.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 have our jobs set up differently between release/master and development (different number of builds, different dependencies). Once we being merging the code over we also need to merge the build definitions on <USER>from development to release."
Answer: 8444.0

User story: Findbugs (and the Jenkins plugin) defaults to using "priority" for sorting issues into high/normal/low. The reality is that "priority" was defined as closer to "confidence level" in the way it's used.  With Findbugs 2.0 they introduced "rank" which is the notion of how "scary" a bug is. I'd argue that's a better thing for us to track and determine the high/normal/low values and thresholds to use.    The plugin doesn't let you change how the mapping is done, so I looked at the source and it appears to be:  1-4: High  5-9: Normal  10+: Low.    (Compare this to Findbugs definition: scariest (rank 1-4), scary (rank 5-9), troubling (rank 10-14), and of concern (rank 15-20).)
Answer: 14498.0

User story: "Once the mainline builds and PR builders are recording code coverage results, we should enforce that the PR doesn't pass unless it builds, passes all the tests and doesn't drop coverage from the current level on the target merge branch."
Answer: 14761.0

User story: "We should enable tracking code coverage on the PR builders."
Answer: 14732.0

User story: "Once we have code coverage recorded for the three normal builds that run unit tests, we should enforce the coverage never drops like we do for nightlies. This way we can catch if a commit will break the build because of this earlier in the process."
Answer: 14747.0

User story: "We currently record code coverage for nightly builds and PHP/Ruby. We should add code coverage to the normal development branch builds:  - studio3-core-development  - appcelerator-core-development  - titanium-core-development  "
Answer: 14734.0

User story: A user can also hook up a project to Node.ACS using our "Deploy provider" mechanism. When they do so under 360 we need to be able to prompt them for the service name, org and environment (based on if the project is 360 or not we may have some of this data already). Then we need to pass the org and env id down to the underlying acs new call.
Answer: 1541.0

User story: "We allow adding a node acs service underneath an existing project (definitely Ti Mobile projects, maybe any project nature?). When we do this we have a command handler which eventually call acs new. In 360 we need to override the handler and prompt user for org/env and pass that down to acs new call."
Answer: 1524.0

User story: "I need to port over the manual signing to happen for master/release windows installer builds (because they're not yet on Advanced Installer). I also need to fire off a build on each, so that the full artifacts are signed properly now that we renewed the certs."
Answer: 1197.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 found out that I can hook up the internal build agents to the new external build master, so now let's do that with our mac build agent and then migrate the mac installer jobs over to the new setup. Then we don't need to do any sort of funky split sync jobs or monitoring URLs to trigger installer builds."
Answer: 145.0

User story: "We have been operating with an exploded copy of an old version of the client library. We've since made changes to the code and haven't pushed a PR upstream (specifically around proxies and the httpclient code). We need to submit a PR to push that upstream, then update our copy of the client (we also need their fixes that handle non-JSON server responses)."
Answer: 18697.0

User story: "h3.Description  Auto complete does not work in Appcelerator Studio 3.2.1 with a brand new project and a brand new workspace.    h3.Reproduction  Download the latest version of Studio (3.2.1.201402061120) and install  Create a new workspace  Create a new project  Open the XML or TSS file and try to get Mobile Code Complete suggestions    Result: No suggestions or non-titanium suggestions will be made  Workaround: Project > Clean > Clean All Projects"
Answer: 36007.0

User story: "<USER>is planning on rewriting the module create scripts to move away from the legacy python to the new titanium CLI. We'll need to update our code to call this new command to generate module projects now."
Answer: 30328.0

User story: "The download button on the new setup is busted. It probably does some form submission to a server to get the download URL, when we should be able to bake that logic into client-side Javascript to get the correct URLs."
Answer: 1816.0

User story: "We need to set up a build node on a Windows AWS box in the new infrastructure to transition the installer builds over to the new setup."
Answer: 15419.0

User story: "AirWatch integration will be eventually rolled into Appcelerator Studio 3.3.0. In the mean time, it should be installable only to Appcelerator Studio, not Titanium Studio."
Answer: 96026.0

User story: "Using the API in https://wiki.appcelerator.org/display/tools/AirWatch+Integration to add a publish provider for Airwatch.  Could reference our Nukona and Testflight implementations."
Answer: 100450.0

User story: "Using the API in https://wiki.appcelerator.org/display/tools/AirWatch+Integration to publish the package to Airwatch app store. The information needed could be retrieved from the project itself and the publishing wizard."
Answer: 133430.0

User story: "Add the corresponding feature, builder, and Jenkins job to publish AirWatch integration plugin(s) to an external update site so it could be installed on top of Studio 3.2.0. The feature will eventually be folded into Appcelerator Studio."
Answer: 96229.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: A very long time ago, Max hooked up Chromium to work as an SWT browser for us. I think the original reasons were that we wanted a bleeding edge browser embedded in Studio, and we had issues with videos in the Dashboard.    Since that time, its been many years and now Eclipse even supports WEBKIT based browsers on some systems in the same way as Mozilla browsers.    We should investigate if we can "get away" with removing our use of it. It adds roughly 80Mb in install size on my Mac. And I'm not sure we even really need it anymore.
Answer: 7434.0

User story: "After all the style elements are indexed, then the View file need to validate the missing style elements of 'class' and show any annotations if the class definitions are missing the corresponding style file or in the global file."
Answer: 9729.0

User story: "Studio has to index all the style element sections defined in the TSS file. Currently Studio has only knowledge about the list of the id/class(es) referenced from the View file. However, it has to parse and store the information of all the id/class sections for each TSS file in order to show any annotations of unused elements.    The indexer should differentiate the Id and class elements, and might need to store the style elements correspondingly.    "
Answer: 5751.0

User story: "If a user defines style element such as 'class' for the a UI element in the View file, there is no way to let user define the style element block directly in the style file.    Currently, they have to manually switch back to style file and then create the style data block using the 'class' element defined for the UI element.    It would be easy for the user for a quick fix kind of mechanism, where they can press something similar to Cmd/Ctrl + 1 on the class element value, and then create the style block in the tss file."
Answer: 30467.0

User story: "I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build.    Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds)."
Answer: 50276.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've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build.    Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds)."
Answer: 50750.0

User story: "I've already succeeded in making both compile/build and unit test run in one job with the studio3 PR builder. We should do the same for the normal studio3 job. That way we can eliminate one job; reduce disk usage; speed up the combined time (at least partially); avoid having to use the hack postbuild script to force build status on the core build from the test build.    Only wrinkle is dealing with retaining artifacts. I think we can just specify to retain only the last build's artifacts to save on disk space and still get the time/test result trends (by keeping lots of builds)."
Answer: 54575.0

User story: "We turned off code coverage to speed up build time for our core unit test builds (i.e. studio3 and titanium core). Since then we've moved to Jacoco, which is supposed to be faster. We should consider turning it back on and recording the time difference for impacts, so that we could possibly enable enforcement of code coverage on PR builds."
Answer: 119367.0

User story: "We currently still run emma code coverage on our php unit tests. We've already moved to Jacoco for the nightly builds, we should do the same for all builds that do code coverage."
Answer: 47424.0

User story: "We currently still run emma code coverage on our ruby unit tests. We've already moved to Jacoco for the nightly builds, we should do the same for all builds that do code coverage."
Answer: 46245.0

User story: "Right now our unit test suite for titanium is messed up in that it relies on installing the titanium feature, which is in the RCP, to then run. This is because titanium-core doesn't contain the alloy or acs plugins. They are broken out to separate features which live underneath the umbrella feature in the RCP repo.    So we need to fix that up by doing one of the following:    * Remove the ACS/Alloy features and their separate builds, and just include the plugins in our titanium-core feature.    * Move the ACS/Alloy features and their associated unit tests out to their own repository. Break out unit test jobs for each."
Answer: 1623.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: Set up the Github Pull Request Builder plugin to proactively try to compile, unit test and enforce code coverage results on open pull requests. See https://wiki.<USER>ci.org/display/JENKINS/GitHub+pull+request+builder+plugin    We'll need to install the plugin, set up a job on <USER>to play with this feature, try opening some PRs on a repo to test it. We'll likely want to start 'small" by just compiling and verifying that works (and making sure it's fast and doesn't try to archive artifacts or copy binaries anywhere, etc). Then add on unit testing and code coverage and then code coverage min/max thresholds based on the development job that for the same repo, etc.
Answer: 14278.0

User story: "Currently we only record code coverage on nightly builds for display/info purposes. We should set minimum thresholds which fail the test build (and therefore end up disallowing pushes/syncs to QE/Beta/RC) if we don't meet the value. We should also enforce that the minimums rise every time we raise our coverage level - so that we effectively enforce our code coverage must not get worse over time (and hopefully will only increase, rather than stay flat)."
Answer: 2940.0

User story: "If a user includes event handler for the a UI element in the View file, currently there is no indication that the event handler is a valid method.    The user will only get to know about undefined handler while launching the app on device/simulator. Since, we already have the indexed methods from the javascript files of the project, we should be able to figure out the referenced method is valid and then, show a warning, if it not defined."
Answer: 14611.0

User story: "If a user defines style element such as 'id' for the a UI element in the View file, there is no way to let user define the style element block directly in the style file.    Currently, they have to manually switch back to style file and then create the style data block using the Id defined for the UI element.    It would be easy for the user for a quick fix kind of mechanism, where they can press something similar to Cmd/Ctrl + 1 on the id value, and then create the style block in the tss file."
Answer: 40198.0

User story: "If a user includes event handlers for the a UI element in the View file, there is no way to directly create the event handler in the controller file.    Currently, they have to manually switch back to controller file and then create the event handler.    It would be easy if the user is able to Cmd/Ctrl + Click the event handler method referenced in the View file to directly create the method in the controller file."
Answer: 37742.0

User story: "Titanium Studio Version: 3.2.0.1387411434-7T78382kDVJ0Gx5G on Windows 7    Toolbar doesn't have drag bars, right click does not bring up the menu window so it cannot be edited. This started after upgrading to latest 3.2.    "
Answer: 1884004.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: Sometimes in addition to know the exact "ti info" commands Studio calls, we also want to know the output at the time it is executed, since the output may change when running the same command later on. This ticket is to introduce a new scope to show the output in Studio log when enabled.  
Answer: 8790.0

User story: "It would be a huge time saver if you would consider adding WYSIWYG UI functionality with drag and drop.  You could also organize the libraries by platform so folks would know not to grab a UI element that would not work on a given OS.  If you Google WYSIWYG for HTML you will see a lot of hits.  This functionality is highly coveted and would further separate you from the rest of the pack.  Just my two cents ..."
Answer: 1313801.0

User story: "h5. Description:  The Geocoder Sample has warnings on the following files, all of which are warning of unused styling components    app/styles/addAddress.tss  app/styles/index.tss  app/styles/map.tss      h5. Steps to reproduce:  1) import the geocoder sample  2) Open the file app/styles/addAddress.tss  3) Open the file app/styles/index.tss  4) Open the file app/styles/map.tss    h5. Result:  All have warning indications of unused styling items    h5. Expected Result:  No warnings"
Answer: 166937.0

User story: "Add support for running on Windows simulator."
Answer: 466856.0

User story: "Add support for running on Windows device."
Answer: 468515.0

User story: "Add support for packaging to Windows store in Studio.  "
Answer: 470722.0

User story: "h5.Desctiption  Mobile Web Configuration does not detect installed web browsers.    h5.Steps To Reproduce  1. Set a Web Browser as your system default.  2. Open Studio Dashboard    h5.Expected Result  Mobile Web Configuration should be set up    h5.Actual Result  Mobile Web Configuration shows no default web browser."
Answer: 32.0

User story: "I've attached a screen capture I took of launching Titanium Studio (3.2.0.201312191547) and creating a mobile app new project on my MBP. Dashboard takes about 30 seconds to finish loading, and project creation takes ~ 3 minutes.    Notes:  - I launch into a new workspace, and don't have any other Eclipse software installed.  - The video didn't capture it, but while the Dashboard screen is loading the cursor is a spinning beach ball and Studio won't respond.  - Occurs on every launch/project creation, in the same session, or after restart, etc.    This might some weird system configuration issue on my part, but thought I'd file for tracking purposes."
Answer: 44887.0

User story: "This presumes Genymotion has already been installed. This is for adding any necessary support around the UI to configure and run Genymotion emulators"
Answer: 167996.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. Build an app for distribution  2. Install using adb push /built_apk/ /sdcard/  3. Browse to the apk on the phone and install  4. Run a debug build of the same app from studio    Expected:  The app should fail to install, and we should see an error why    Actual:  Build fails, and Studio falls back to old python scripts"
Answer: 37291.0

User story: Currently for Alloy samples, we call "alloy new" to create the default app and then unzip the sample content on top of it, but for Geocoder sample in 3.2.0, due to the complexity related to ALOY-891, we decide that it will contain the full-fledged app in a zip, and we will define the sample using our existing sample extension point.
Answer: 63.0

User story: "I tried a fresh Windows 8 install, and the Platform Configuration Wizard popped up _before_ the update dialog to install Titanium SDK, CLI, etc. We need those installed to be able to do platform configuration. So we need the wizard to only open after those get installed."
Answer: 23222.0

User story: From Ingo: "I notice the sublime default background is not quite as dark. Can we "lighten" the dark theme a bit to make it match? I think it will make the white text a bit easier to read."  
Answer: 192789.0

User story: In the output of "ti info -o json" for CLI 3.2.0, it will contain a section "ios" > "devices". We should display this list in place of "iOS Device", and when one is invoked, pass the id value in the \--device\-id flag to "ti build" command.  
Answer: 1477.0

User story: Currently when user installs additional Android SDKs from the "Install SDKs" button in Android preference page, we don't show a EULA dialog. We should make it consistent with installing from platform configuration wizard.  
Answer: 12963.0

User story: "Currently we collect AVDs in our AndroidSDKLocator and treat them as SDKEntities (which is wrong in the first place). We then specify the AVD id when we launch an emulator.    We need to move to using device ids. So we need to grab the list of devices from CLI on-demand (since they can change any time) when needed (i.e. when we show a combo box to select one), and we need to pass along the device id on the command line when launching.    This will also involve updating the launch configs and their UIs to select the device id rather than avd-id."
Answer: 11356.0

User story: In the output of "ti info -o json" for CLI 3.2.0, it contains a section "android" > "devices", where it contains info such as id, name, model, and manufacturer. We should display this list in place of Android Device, and when one is invoked, pass the id value in the \--device\-id flag to "ti build" command.  
Answer: 10323.0

User story: In the output of "ti info -o json" for CLI 3.2.0, it contains a section "android" > "emulators", where it contains info such as id, name, model, and manufacturer. We should display this list in place of Android Emulator, and when one is invoked, pass the id value in the \--device\-id flag to "ti build" command.  
Answer: 10335.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 new CLI for Android build no longer requires Android 2.3.3. User would still need it for pre-3.2.0 Titanium SDKs, but we don't need to install 2.3.3 by default in the platform configuration wizard. This is to not have the checkbox selected by default, make it selectable, and remove the info icon next to the version.  "
Answer: 1001.0

User story: "Eclipse 4.x provides CSS styling to theme the visual appearance. We should take advantage of it and incorporate with or replace our existing theming support as necessary. This is the umbrella ticket for the feature.  "
Answer: 12645.0

User story: Note:  *not* regression, occurs in Studio 3.1.3  Although Xcode path different via Studio Preferences and Terminal, projects compile for iOS simulator and device.      h5.To reproduce  1. Studio>Preferences>Studio>Platforms>iOS  Observe Xcode path in "iOS SDK Home" window  h5.Actual result  /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs  via Terminal  {code}  xcode-select -print-path  /Applications/Xcode.app/Contents/Developer  {code}
Answer: 118386.0

User story: "Set new defaults for e4 and editor themes? dark with dark or light with light.    maybe different defaults for TiStud vs AppcStud. Seems like community may prefer dark themes, enterprise light."
Answer: 9940.0

User story: "The old theming hack and the new e4 themes do not play nice together. We should remove the option to apply the old theming outside the editor entirely."
Answer: 6968.0

User story: "We should have a dark e4 theme for users to choose from."
Answer: 8706.0

User story: Add the e4 theme picker to our pref page (and label clearly one as "Overall" and other as "Editor") - so the user can modify themes/colors from the same place.
Answer: 4060.0

User story: "The new UI has a drop down for mode, but we also wanted to add packaging to it. Technically packaging is not a mode. So we need to find some way to add that on as well."
Answer: 16503.0

User story: "We are deprecating FastDev in SDK 3.2.0+ Thus, we should remove the option to launch with FastDev enabled "
Answer: 17306.0

User story: "Investigate and fix issues Studio has with Maverick."
Answer: 10247.0

User story: "The current base is Eclipse 4.3.0. 4.3.1 was released in September, so it makes sense to update Studio to use the latest version.  "
Answer: 33146.0

User story: "h3. Steps to Reproduce A section should exist in the tiapp.xml configuration GUI to select themes if they exist.    h3. Actual Result themes must be configured manually in the config.json file  h3. Expected Result this could be abstracted to the tiapp.xml and easily managed through the associated interface"
Answer: 383639.0

User story: "See screenshot. There is a dark line under the global toolbar that we should try to remove or re-theme as part of TISTUD-5477.  "
Answer: 20153.0

User story: "Once we clean up the global toolbar and add the new UI for device profile, we should re-enable global toolbar for the simple perspective.  "
Answer: 16907.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: "It is unlikely user would use Studio to browse local filesystem, and Titanium development is very much project-based, so we should remove the node for Titanium/Appcelerator Studio. We will still keep it for Aptana Studio.  "
Answer: 38979.0

User story: "The feeling is App Explorer doesn't add compelling value and feels redundant next to Project Explorer. We will hide/deprecate it from default Studio perspectives but keep the plugin.  "
Answer: 5689.0

User story: "Studio should install npm packages locally into a folder accessible to the user without sudo permissions (to avoid problems described at TISTUD-5428)    In order to accomplish this -    1) Currently we set global flag for any npm package installation. Mark all actions with npm packages without global to make them local installations.  2) The npm packages can not be installed/queries in the .titanium or .npm folders under home directory. The folder name can not start with dot.  3) Remove the check for alias bin files in the /usr/local directory - as the local installation will not create symlink files in /usr/local directory.  4) Cleaning the cache sometimes requires sudo permissions - so we still need to prompt for password. However, use this password only for cleaning the cache.  "
Answer: 43069.0

User story: "We currently include JDK6 in Studio installer. Since we confirmed Studio and SDK work with JDK7, we should update the version.  "
Answer: 61968.0

User story: "To improve the background transition from the main platform section to settings section, a suggestion is to add a gradient in the middle.  "
Answer: 9667.0

User story: In the initial page, "Configure" makes more sense as an action than "Finish".  
Answer: 3083.0

User story: "When all selected platforms are done configuring (or the process got canceled), we should change the Hide button to Close and remove Cancel.  "
Answer: 8610.0

User story: # Make the Advanced Settings text and arrow right-aligned  # Move the arrow to the right of the text  # Modify the text to say "Settings" when collapsed and "Hide" when expanded  # Make the status center-aligned  # Remove warning icon for "Not Yet Configured"
Answer: 679.0

User story: "Currently we are only selecting Android 2.3.3 by default. Instead, we should select it and the most popular version, currently 4.1.x (36.6% as of 09/04/13), and make the most popular one the default.   "
Answer: 392.0

User story: "In 3.2.0, users could select platforms that they haven't configured Studio with yet, and the concern is that it could cause confusion if user doesn't see the Install button and wonders why he/she can't run the app from menus after selecting the platform in tiapp. The suggestion is when tiapp editor is saved, if there are unconfigured platforms selected, we prompt users so they could setup the platforms there.  "
Answer: 4101.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: "Since we are downloading and installing Android, BlackBerry, and Tizen SDKs directly from the platform config wizard, we need to display the respective EULAs for user to accept. This ticket is to implement the UI for accepting EULA.    We will open a separate dialog for EULA when user clicks Finish to configure the list of selected platforms. The dialog will just contain a large multi-line text field where it contains the EULA text for each platform in sequential order. The dialog will have two buttons - Accept and Decline, and user doesn't need to scroll down to the bottom of the text to have Accept enabled. When accepted, we will move to the progress page; when declined, we will close the platform config wizard."
Answer: 77726.0

User story: "Currently we auto-check the platform entry in platform config wizard when user modifies any fields in Advanced Settings section. However, this creates the following situation:    1. Uncheck Android, expand Advanced Settings section and check one of the uninstalled Android versions (e.g. 4.2); this will make Android correctly checked.  2. Then uncheck Android again and uncheck the same Android version (e.g. 4.2); the Android platform will become checked again, even though we are actually back to the original state when the wizard first opened.    Expected result: we should only auto-check the platform entry when the state is different from the original."
Answer: 14038.0

User story: "Currently we save platform SDK paths in InstanceScope; that means the settings are per workspace, and each time user switches to a new workspace, they need to re-configure the platform SDK paths.    The suggestion is to save platform SDK paths in ConfigurationScope so they persist per installation. We need to make sure we migrate existing paths from InstanceScope so users don't need to re-configure after update, and once we make the change, the auto-launch of platform configuration wizard should happen per installation instead of per workspace as well.  "
Answer: 37504.0

User story: When we finished configuring a platform, we should update the status area to display two lines: the regular check mark and latest installed version on top, and the installation location below. The Settings text and arrow should remain hidden.    If the installation is canceled, we should show "Canceled" status but without any icon.
Answer: 18590.0

User story: "When we finish configuring a platform, we update the status and its icon in the middle, but the cancel icon and progress bar on the right still remain. They should be hidden at this point. Similarly when user cancelled the operation, we should hide the progress bar once the cancellation process is done as well.  "
Answer: 4507.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: "Currently we show all the platforms, but it feels confusing to me in seeing the other platforms that I didn't choose to configure there. User could feel they can still do something with the other platforms in the mean time even though they always indicated they are not interested in them at this point. We should just show the selected platforms and their progress instead."
Answer: 15843.0

User story: "When we move into the progress page, we should update the description to indicate we are now configuring for the selected platforms."
Answer: 8668.0

User story: "Related to TISTUD-5326. For iOS, currently there is no Advanced Settings section, and the visual indicator will appear in its place, making the UI feel inconsistent. The suggestion is to line it up on the right as indicators for other platforms are."
Answer: 148562.0

User story: Application with fastdev enabled in the tiapp.xml when executed in emulator, Fastdev server doesn't run.  Fastdev is enabled and server runs with android 2.3.3 on emulator. Issue occurs with Android version 4.1 and later.    Steps to reproduce:  1. Create a default project in the appcelerator studio.  2. Add <property name="ti.android.fastdev" type="bool">true</property> in the tiapp.xml.  3. Run the app with Android 4.1.2 on emulator.    Expected:  App should run with fastdev server running.  Should get log as " Fastdev server running, deploying in Fastdev mode"    Actual:  Getting log as "Fastdev enabled but server isn't running" on the console.
Answer: 27236.0

User story: "When AppC Studio first launches and checks for updates on Windows, one of the items that fails is the code processor install because git is not installed.  Git needs to be installed first."
Answer: 101090.0

User story: "Currently we add Android versions into a two column grid layout so the sorting looks a bit odd:  {code}  4.3 4.2  4.1 3.2  ...  {code}    Switch to column sorting:  {code}  4.3 3.1  4.2 2.3  4.1 2.2  3.2  {code}"
Answer: 1885.0

User story: "In the tiapp editor, instead of showing a platform as diabled when it is not configured, we should enable them, and when user selects one and saves the editor, we will prompt to indicate the platform(s) are not yet configured and ask if they would like to configure them. When user selects yes, we will open the platform configuration wizard with the unconfigured platforms that user has selected checked by default."
Answer: 177044.0

User story: "In the new module project wizard, instead of disabling a platform when it is not configured, we should enable all, and when user choose a unconfigured platform (for module project, only one platform could be selected), we will prompt to indicate that platform is not yet configured and ask if they would like to configure it. When user selects yes, we will open the platform configuration wizard with the selected platform checked by default."
Answer: 54225.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 new mobile project wizard, instead of disabling a platform when it is not configured, we should enable all, but only check the ones user already configured by defaul. When user selects one or more unconfigured platforms and proceeds, we will prompt to indicate those platforms are not yet configured and ask if they would like to configure them. When user selects yes, we will open the platform configuration wizard with the unconfigured platforms that user has selected checked by default."
Answer: 33842.0

User story: "If this is the first time user has launched Studio after installation, we should prompt the platform configuration wizard after Studio starts. For subsequent launches, we should not prompt.  "
Answer: 15704.0

User story: "To be consistent with other platform preference pages, we should have a Configure button for BlackBerry, and it will open the new platform configuration wizard with BlackBerry selected.  "
Answer: 4254.0

User story: "To be consistent with other platform preference pages, we should have a Configure button for Tizen, and it will open the new platform configuration wizard with Tizen selected.  "
Answer: 4254.0

User story: "The Configure button currently opens the dashboard. With the platform configuration wizard implemented, it should open the wizard instead, with only Android item checked by default."
Answer: 1780.0

User story: "The Configure button currently opens the dashboard. With the platform configuration wizard implemented, it should open the wizard instead, with only iOS item checked by default."
Answer: 1779.0

User story: "If you right-click in a file opened in the editor that is inside a git attached project, the entry for Team > Show In Resource History is disabled."
Answer: 20172.0

User story: "According to a variety of tickets, it _appears_ that JDK 7.0 should work for both Studio and SDK, but we currently require JDK 6. We should confirm JDK 7 works as expected, or correct (if possible) the reasons that prevent it from working."
Answer: 18689.0

User story: If a user adds a new remote but doesn't perform an action that would actually fetch or hit the remote, git doesn't "grab" the list of branches at that remote. When a user adds a remote through studio we can pass a flag that forces an immediate fetch to help alleviate this.
Answer: 11.0

User story: "See https://wiki.appcelerator.org/display/tools/Platform+Configuration+Workflow+in+Studio#PlatformConfigurationWorkflowinStudio-V2 and TISTUD-5051 for the details.  "
Answer: 197181.0

User story: There are users and partners that have not been able to get the Field Service App to work.  It turns out many of them is because they didn't look at the ReadMe.  I believe that if we state it in the description, then more users will actually look at the readme and this should increase the overall success of the Field Service App.    "Please read the ReadMe file in order to complete the configuration of the application."  Or something like that.
Answer: 25904.0