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: "When getting the status of a plugin where the version is a semver range, it will scan all plugins for a match by name and version. The order of the registered plugins is whichever order they were loaded. The list of plugins must be sorted in order to deterministically find the plugin.    If you have @appcd/plugin-titanium v1.6.0 and v1.8.1 installed, getting the status for {{^1.6.0}} should return v1.8.1.    {code}  appcd exec /appcd/plugin/status/@appcd/plugin-titanium/^1.6.0  {code}"
Answer: 12.0

User story: "The Titanium CLI needs bi-directional communication with the Titanium plugin, however the Appc Daemon dispatcher is not capable of supporting true bi-directional data flow, but rather just single request, multi-part responses.    To work around this, we need the Titanium CLI to locate the Appc Daemon, start it, ensure the Titanium appcd plugin is registered, and call a terminal discovery endpoint. From there, the Titanium CLI will connect to the terminal session endpoint via a WebSocket."
Answer: 21992.0

User story: The "ti new" command (and "ti add") need to create projects and components based on a template. A general purpose template toolkit would standardize template structure,  make it easy to add templates to other Node.js-based products, and get more people battle testing the library.    The template library specification can be found here: https://techweb.axway.com/confluence/display/pe/Proposal%3A+Project+Template+System.
Answer: 50474.0

User story: "We need a shared Node.js-based library for interacting with the AMPLIFY platform. This library handles:    * Auth  * Orgs  * Titanium app support  * ACS app support    For auth, it will simply be a wrapper around amplify-auth-sdk, then mix in the org information, which is currently all done in the amplify-auth-sdk and slated for removal.    For orgs, the code can be taken from amplify-auth-sdk."
Answer: 113670.0

User story: "While the daemon supports Node 10, we should update the core to Node 12 so that we can use the latest features such as workers.    Node.js doesn't gain us much as far as removing Babel transpilation. We could switch over to ES modules, but we still need to transpile for dynamic imports and optional chaining. We probably cannot remove Babel until Node 14 goes LTS in late 2020."
Answer: 71940.0

User story: "Each appcd package has a changelog, but there's no high-level release notes that consolidates the changelogs. It would be beneficial to have a tool that pulled determined Appc Daemon releases and merge the release notes per version."
Answer: 793.0

User story: "Document Appc Daemon releases and their plugin API versions.    For the meantime, this can go in the markdown docs in the repo."
Answer: 872.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 time has come to remove support for Genymotion. The Android emulator has matured and thanks to advances in virtualization technology, it is quite fast. Secondly, Genymotion is not free and it's not like they ever gave us any licenses. Thirdly, we don't want to maintain a second emulator technology, especially one that has only does x86 emulation and often causes incompatibility issues with Titanium native modules.    1. Remove the [code|https://github.com/appcelerator/appc-daemon/blob/bf20fec94c74e055e4359a8e123539054c4cb228/packages/appcd-core/src/server.js#L482-L486] in appcd-core that copies the Genymotion config from the Titanium CLI's config to the appcd config. Bump minor.    2. Deprecate [@appcd/plugin-genymotion|https://github.com/appcelerator/appcd-plugin-genymotion].    3. Remove all references to Genymotion and VirtualBox in [@appcd/plugin-android|https://github.com/appcelerator/appcd-plugin-android]. Bump major.    4. Remove all references to Genymotion in [@appcd/plugin-system-info|https://github.com/appcelerator/appcd-plugin-system-info]. Bump major.    5. Remove all references to Genymotion and VirtualBox in [@appcd/plugin-titanium|https://github.com/appcelerator/appcd-plugin-titanium]. Bump major.    Since we're removing data from the info, this is breaking change and everything (except appcd itself) must have a major version bump."
Answer: 180267.0

User story: "The Appc Daemon's plugin system allows plugins to specify which appcd version they are compatible with, however we have to ship new plugins for each major plugin version whenever we bump the appcd major version regardless if the plugin system actually changed.    Since the plugin system rarely changes, we shouldn't couple plugins with the appcd version, but rather a separate plugin API version.    For example, the iOS appcd plugin 1.x is compatible with every appcd version, but iOS appcd plugin 2.x requires appcd version 3.x because of changes to appcd-detect that is passed into each plugin."
Answer: 190.0

User story: "The alloy command in appc cli should be retired. "
Answer: 151784.0

User story: h5.Description    We're bumping the daemon to 2.x, so we need to bump all the plugins to support this, pretty much find and replace {{"appcdVersion": "1.x"}} with {{"appcdVersion": "1.x || 2.x"}}
Answer: 5238.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 Appc Daemon has telemetry enabled by default. It currently sends 4 different events: {{appcd.server.start}}, {{appcd.server.shutdown}}, {{appcd.plugin.added}}, and {{appcd.plugin.removed}}. Most of these events include data that may violate the GDPR (General Data Protection Regulation).    h4. Collected Data    The {{appcd.server.start}} event includes {{process.argv}} which leaks the user's username. {{process.argv}} will be removed from the payload.    The {{appcd.plugin.added}} and {{appcd.plugin.removed}} events include each plugin's path which also leaks the user's username. All plugin paths will will be removed and a {{packageName}} will be added.    We collect this data to track usage and versions of the Appc Daemon and its plugins. We can use this data to determine if we can deprecate versions, platforms, features, and be able to track what plugins and versions are being used so we can focus testing and integration.    h4. Disabling Telemetry    Telemetry can be completely disabled by running:    If you have Appc Daemon globally installed:    {code}  appcd config telemetry.enabled false  {code}    If you have the recent Appc CLI:    {code}  appc appcd config telemetry.enabled true  {code}    Also note that we have ticket DAEMON-254 to prompt for opt-in first run, but still defaults to enabled."
Answer: 2293.0

User story: "Need to go through the appc-daemon repo and all plugins and write up release notes for v1.1.0."
Answer: 36917.0

User story: "h5.Description    The gulp-util package has been deprecated, https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5. We should probably move away from it following the advice in the linked blogpost. Although as stated there this probably isn't super high priority as we only use .log and .colors"
Answer: 1928.0

User story: "It's possible for a cert to have a name that cannot be decoded to an unsupported character sequence. We need to wrap each cert parsing in a try/catch so that we just skip the cert and move on."
Answer: 19.0

User story: "It has been requested that there be a video about the Appc Daemon that describes what it is, how it works, and what the future holds for the daemon.    An outline will need to be written. Diagrams will need to be diagrammed. Screens will need capturing. Audio will need to be recorded. Video will need to be edited. Special effects will need to have special effects."
Answer: 25142.0

User story: "h5.Description    This ticket should cover both appc-daemon, and the *lib modules we have (maybe use appveyor for the lib modules)    Currently on Jenkins we test on osx or linux. It would be nice to also add Windows into the mix for this. Reviewing the current Jenkinsfile I imagine we would want to maintain running install and check on non-windows and then just add Windows to the test matrix. Maybe even expanding the tests section to run on osx, linux and windows in parallel"
Answer: 1140887.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 daemon needs a layer between the Dispatcher and WebSocket requests that understand the appcd WebSocket protocol. This "bridge" is responsible for request parsing and error handling.    This bridge must support a ReadableStream Dispatcher response. Each "chunk" of stream is a new response to the WebSocket client. The appcd WebSocket protocol may need to be extended to include a "fin" property, which is not to be confused with the WebSocket "fin" property.
Answer: 23311.0

User story: "The AMPLIFY Platform appcd plugin (@appcd/plugin-amplify) is responsible for authentication. It contains services authenticating against Axway ID and retrieving, refreshing, and invalidating access tokens.    This plugin eventually will also contain the entitlements service."
Answer: 2238550.0

User story: "The new webpack support needs an official getting started guide which covers the following aspects:    - Prerequisites (Installing appcd and @appcd/plugin-webpack)  - Creating a new project with the webpack template  - Webpack related changes    - Aliases    - platform specific files    - Using NPM modules (including them for transpilation in Babel?)  - FAQ  - Short introduction/examples to plugins/hooks"
Answer: 74638.0

User story: "https://github.com/appcelerator/titanium_mobile/blob/0144d77a1b203496bb935b84a65debc099ee18d7/apidoc/Titanium/Geolocation/Android/Android.yml#L80   {{name: Ti.Geolocation.PROVIDER_GPS,}} should be {{name: Ti.Geolocation.Android.PROVIDER_GPS,}} was missed when these were moved"
Answer: 88078.0

User story: "There are some inconsistencies in the Geolocation docs in that they do not match fully on Android    Also fix the various warnings produced from the docgen script that will cause invalid links in the docs site"
Answer: 58176.0

User story: "Review assigned tasks for doc day: Ti.UI.TextField and Ti.UI.ScrollView. Check through the spelling, grammar and links"
Answer: 88178.0

User story: "I think we should publish below page with the Studio GDPR changes. This will gave a fair idea for the users on the fields which we are tracking if they agree to send the studio usage data.    https://wiki.appcelerator.org/display/tools/Studio+Analytics+Events"
Answer: 71430.0

User story: "When going to https://wiki.appcelerator.org/pages/viewpage.action?pageId=29002574, it says  {quote}  This documentation relates to previous versions of Titanium.    To see the latest documentation, visit [docs.appcelerator.com|http://docs.appcelerator.com/titanium/latest/].  {quote}    But the docs link leads to http://docs.appcelerator.com/titanium/latest/ which does not exist. It should instead link to https://docs.appcelerator.com/platform/latest/#!/api"
Answer: 9084.0

User story: "There are currently a slew of warnings in the docgen script due to the usage of Ti over Titanium when referring to APIs/Classes, and using incorrect namespaces for APIs.    More info in the PR https://github.com/appcelerator/titanium_mobile/pull/9961"
Answer: 14752.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: "For the Tech Preview 1 of Titanium Angular, we need a getting started guide. This needs to include:    * How to create a new Angular project  * Explain the project structure  * Notes about Routing in Titanium & Angular  * Current limitations and workarounds to known problems"
Answer: 42792.0

User story: Can we improve the documentation on "Using Studio From Behind a Proxy"    Here is the current link  https://docs.appcelerator.com/platform/latest/?mobile=/guide/Using_Studio_From_Behind_a_Proxy    We basically need to incorporate the documentation which mentioned here https://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-preferences.htm     !proxy_docu.png|height=330,width=700!      Below is the modified content from https://docs.appcelerator.com/platform/latest/?mobile=/guide/Using_Studio_From_Behind_a_Proxy    *How to configure Proxy Settings in Appcelerator Studio*    To configure your proxy settings once Studio has started, open the Preferences window and navigate to Network Connections:    # From the menu bar, select Windows > Preferences on Windows, or select Titanium Studio > Preferences or Appcelerator Studio > Preferences on Mac OS X.  # Navigate to General > Network Connections.  # Select “Manual” from Action Provider drop-down list     !network_connections.png|height=250,width=500!   # Select the Proxy entry that you would like to edit, for example, HTTP, and click Edit...  # In the Host and Port fields, specify the name or IP address and port number of your proxy server.    !proxy_details.png|height=330,width=500!   # If you have authentication enabled, check the Requires Authentication box and type in your proxy User and Password.  # Click OK to apply your settings.  # Restart Studio. All Internet traffic will be directed via this proxy.
Answer: 696194.0

User story: "Rename text fromm Titanium Platform Overview to Titanium SDK Overview"
Answer: 77736.0

User story: "We need a very simple app that shows step by step on how to create an app, build it and finally deploy it  While we already have samples here (https://wiki.appcelerator.org/display/guides2/Titanium+Samples)  But we have to break it down something like this:  1) Creating the frontend  2) Connecting to the backend  3) Use the module/ call the native API  4) Deploy"
Answer: 90816.0

User story: Currently within the Titanium SDK tile, we can see some duplications in the following links:    Titanium SDK Getting Started  Titanium SDK Guide  Welcome To Titanium!  Titanium Platform Overview    The intension here is to make the on-boarding journey very simple and easy to follow.  We can probably just have one link for "Getting Started" and have the following headings:    Getting Started  * Introduction to Axway Appcelerator Mobile Solution Platform  * Quick Start   ** Prerequisites  ** Installation  ** First Titanium App    Kindly follow the attached word document for more details
Answer: 111052.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, the "getting started" page is in App Developer -> Titanium SDK tile.  There should be a new tile within App Developer, which states " Welcome to  Axway Appcelerator Mobile Solution Platform" and within that tile we should have the "getting started" page.
Answer: 38978.0

User story: The swagger doc ( url or json)  generated for MBS APIs should be included in the documentation .   http://docs.appcelerator.com/arrowdb/latest/#!/api    Swagger url : https://admin.cloudapp-enterprise.appcelerator.com/arrowdbapi/#/    "Arrow DB" should be replaced as "Mobile Backend Service" in the Swagger spec.   
Answer: 737158.0

User story: In the API developer tile , rename AMPLIFY Appcelerator Services to "Mobile Analytics"    and also rename the following sub-topics     1)Analytics to "Usage Analytics"  2)Performance to "Performance Analytics"  3) Test to "App Test"
Answer: 54825.0

User story: "In the doc.axway.com, we see a tile called App Developer. We need to add API Builder, API Runtime and Mobile Backend Services components to App Developer same as API Developer"
Answer: 28852.0

User story: "Review the following sources for information about Daemon (launches with SDK 7.0.0 this November):  * https://github.com/appcelerator/appc-daemon/tree/master/docs  * https://wiki.appcelerator.org/display/tools/Initial+Daemon+launch+considerations"
Answer: 29221.0

User story: "Complete a documentation survey of the App Developer products (SDK, CLI, Studio, and Alloy) with the following goals in mind:  * Look for old or outdated content  * Look ways to organize the documentation better  * Content themes  * Review our Google analytic data to which pages are the most popular, assess said pages, and determine which ones need updating  * Review our Google analytic data for commonly searched terms and assess which pages could address this concern    From all this data, generate a list of pages that should be updated, created, or archived and present it to Eric Merriman."
Answer: 11651.0

User story: "This story collects all issues that I have discovered in the first two weeks of the Zoomin soft launch.  # https://techweb.axway.com/jira/browse/ZDP-119  #* https://mantis.suite-sol.com/mantis/view.php?id=16975 - Confluence redirect macro doesn't work  # -https://mantis.suite-sol.com/mantis/view.php?id=17129 - Broken link in Appcelerator CLI How-to page-  # https://mantis.suite-sol.com/mantis/view.php?id=17130 - Anchor links don't work on Windows 7 using IE 11  # -https://mantis.suite-sol.com/mantis/view.php?id=17211 - Broken links in Nodes in Flow page-"
Answer: 89481.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: "    1. Globally replace *“Appcelerator Platform”* with *“AMPLIFY(tm) Appcelerator Services”.    2. In the page https://docs.appcelerator.com/platform/latest/#!/guide/Appcelerator_Platform add a highlight box in the top of the page – “Appcelerator Platform is available as a service referred as App Builder through the AMPLIFY(tm) platform.”  The highlighted box should also appear in Quick Start    http://docs.appcelerator.com/platform/latest/#!/guide/Quick_Start  "
Answer: 14474.0

User story: "Chuck is getting a few requests to make changes to the API docs. Brian will need to train him on how to do this."
Answer: 14251.0

User story: "As we were branding {{Appcelerator Studio}} as {{Axway Appcelerator Studio}} with the 4.10.0 release, we need to incorporate a couple of changes in the documentation.    Here - https://docs.appcelerator.com/platform/latest/#!/guide/Appcelerator_Studio_Release_Notes  Can we change the text from {{Appcelerator Studio Release Notes}} to {{Axway Appcelerator Studio Release Notes}}    Here - https://docs.appcelerator.com/platform/latest/#!/guide/Appcelerator_Studio  Change header text from {{Appcelerator Studio}} to {{Axway Appcelerator Studio}}    Here - https://docs.appcelerator.com/platform/latest/#!/guide/Using_Studio_From_Behind_a_Proxy  We need to update the below 2 images, which contains new splash screen and proxy configuration dialog. Looks like the documentation is having the old proxy configuration dialog which was changed long time ago.   !splashscreen1.png|thumbnail!    !Proxysetup.png|thumbnail!     Here -  https://docs.appcelerator.com/platform/latest/#!/guide/Updating,_Changing,_Uninstalling_Studio  Need a text change from {{Check for Appcelerator Updates}} to {{Check for Axway Appcelerator Updates}}    Need to change Appcelerator Studio icon wherever it's required.  https://docs.appcelerator.com     !AxwayAppceleratorStudio.bmp|thumbnail!  !ax-stud-dock.1.png|thumbnail!         "
Answer: 26315.0

User story: Hello,    The *"applicationDataDirectory"* property seems not to be available on Windows - but it is. Here is the documentation [link|http://docs.appcelerator.com/platform/latest/#!/api/Titanium.Filesystem-property-applicationDataDirectory]. It is showing *"applicationDataDirectory"* property available for Android, iOS and mobile web.     Thanks
Answer: 1089813.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: "This ticket is a gateway ticket to track all the requests and progress made on these tickets as they relate to issues assigned to me to fix or resolve various Zoomin styling and/or functionality problems.     ZDP ticket list:  * https://techweb.axway.com/jira/browse/ZDP-118 - done  * https://techweb.axway.com/jira/browse/ZDP-117 - done  * https://techweb.axway.com/jira/browse/ZDP-116 - done  * https://techweb.axway.com/jira/browse/ZDP-115 - done  * https://techweb.axway.com/jira/browse/ZDP-112 - done  * https://techweb.axway.com/jira/browse/ZDP-111 - done  * https://techweb.axway.com/jira/browse/ZDP-110 - done  * https://techweb.axway.com/jira/browse/ZDP-109 - done  * https://techweb.axway.com/jira/browse/ZDP-108 - done  * https://techweb.axway.com/jira/browse/ZDP-107 - done  * https://techweb.axway.com/jira/browse/ZDP-106 - done  * https://techweb.axway.com/jira/browse/ZDP-105 - done  * https://techweb.axway.com/jira/browse/ZDP-104 - rejected  * https://techweb.axway.com/jira/browse/ZDP-103 - done  * https://techweb.axway.com/jira/browse/ZDP-101 - done  * https://techweb.axway.com/jira/browse/ZDP-100 - done  * https://techweb.axway.com/jira/browse/ZDP-98 - done  * https://techweb.axway.com/jira/browse/ZDP-97 - done  * https://techweb.axway.com/jira/browse/ZDP-96 - done  * https://techweb.axway.com/jira/browse/ZDP-95 - done  * https://techweb.axway.com/jira/browse/ZDP-94 - done  * https://techweb.axway.com/jira/browse/ZDP-93 - done  * https://techweb.axway.com/jira/browse/ZDP-92 - done  * https://techweb.axway.com/jira/browse/ZDP-91 - done  * https://techweb.axway.com/jira/browse/ZDP-90 - done  * https://techweb.axway.com/jira/browse/ZDP-89 - done  * https://techweb.axway.com/jira/browse/ZDP-88 - done  * https://techweb.axway.com/jira/browse/ZDP-87 - done  * https://techweb.axway.com/jira/browse/ZDP-86 - done  * https://techweb.axway.com/jira/browse/ZDP-76 (ZDP-85 duplicates this one)  * https://techweb.axway.com/jira/browse/ZDP-84 - done  * https://techweb.axway.com/jira/browse/ZDP-83 - rejected"
Answer: 174282.0

User story: "The [Android Module Project|https://wiki.appcelerator.org/display/guides2/Android+Module+Project] page in our Wiki needs to be updated to cover the new Android Library feature.    Important parts that need to be mentioned:  * Where to place them  * How to resolve Android Library dependencies  * Workaround issues with Studio  * Resolving possible duplicate library conflicts  * Current limitation with our bundled support libraries"
Answer: 4364.0

User story: "h5.Description    For ws-local and wp-device, liveview usage is straight forward like other platforms, for wp-emulator it requires a custom --liveview-ip to be set. Find and review the liveview docs, updating where necessary"
Answer: 10526.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: "# Test the Zoomin plugin for Confluence  # Communicate with the Zoomin teams on my progress  # Document any features, workflows, known issues, and anything else that is noteworthy  # Share my final workflow documentation with the Axway tech writers once it is finished"
Answer: 212982.0

User story: "Create a document that lists all the methods of documentation collaboration with each team that you work with.  Meet with your team and document the strategy (both previous and new if necessary) in a series of pages by product.  For example:  * Documentation Collaboration Strategy 2017  ** Documentation Collaboration Strategy 2017 - Alloy Framework  ** Documentation Collaboration Strategy 2017 - API Builder Tools  ** Documentation Collaboration Strategy 2017 - API Runtime Services  ** Documentation Collaboration Strategy 2017 - Appcelerator CLI  ** Documentation Collaboration Strategy 2017 - Appcelerator Dashboard  ** Documentation Collaboration Strategy 2017 - Appcelerator Platform Services  ** Documentation Collaboration Strategy 2017 - Appcelerator Studio  ** Documentation Collaboration Strategy 2017 - ArrowDB and Push  ** Documentation Collaboration Strategy 2017 - Titanium SDK    Questions to be asked when meeting with the respective teams to discuss documentation collaboration:  How will your team communicate the following items?  # New documentation requests?  # Documentation changes (requests for content, images, and links)?  ## Big modifications? Small changes?  # Document archival and/or removal?  # Document review requests?  # APIDoc modifications?  # Product release schedules, dates, and changes?  # Product release note content? Publishable vs non-publishable content?  ## Product dependencies and component versions updates?  ## Platform-specific information?  ## Community contributors (non-employee recognition)?  ## Known issues?  ## API changes?  ## Breaking changes?  # Cross-product updating?  # Document name changes, navigation, and/or page hierarchy modifications?  # Internal software changes (e.g. product documentation linking, styling, etc.)?  # Publishing documentation to the public-facing web site(s)? This should be automatic in every request but some documentation may be time or customer sensitive.  # Source(s) of truth (source documentation)? User, meetings notes, wiki (unpublished), Github, email, other? If other, please elaborate.  # If any changes are made to the way we handle documentation requests, how will they be communicated with the team?     Documentation types:  * guides/tutorials/overviews  * release notes  * API docs    Format:  Question: ...  Historically, we did ....  Suggestion: we should ... and enforce it by ...."
Answer: 256657.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: "Need to update the documentation for Prerequisites  http://docs.appcelerator.com/platform/latest/#!/guide/Prerequisites    Update TitaniumCompatibilityMatrix:  http://docs.appcelerator.com/platform/latest/#!/guide/Titanium_Compatibility_Matrix-section-src-29004837_TitaniumCompatibilityMatrix-JavaDevelopmentKit    And wherever is required."
Answer: 53963.0

User story: "Review any API Builder videos that was created as part of the latest release.  RDPP tickets:  * https://techweb.axway.com/jira/browse/RDPP-1086"
Answer: 23141.0

User story: "Document the following features mentioned in these tickets:  # TIMOB-23760  # TIMOB-23759  # TIMOB-23833  # TIMOB-24063"
Answer: 55312.0

User story: "Following ArrowDB and Push documentation pages need to be reviewed and possibly updated for the upcoming release of APIM+ 7.5.3:    Getting Started QuickStart Guide - [https://wiki.appcelerator.org/display/guides2/Getting+Started+QuickStart+Guide]  Using the REST API - [https://wiki.appcelerator.org/display/guides2/Using+the+REST+API]  Authentication - [https://wiki.appcelerator.org/display/guides2/Authentication]  ArrowDB SDKs - [https://wiki.appcelerator.org/display/guides2/ArrowDB+SDKs]  Titanium SDK and ArrowDB - [https://wiki.appcelerator.org/display/guides2/Titanium+SDK+and+ArrowDB]  Appcelerator Platform Services SDK for Android ArrowDB and Arrow Push - [https://wiki.appcelerator.org/display/guides2/Appcelerator+Platform+Services+SDK+for+Android+ArrowDB+and+Arrow+Push]  Appcelerator Platform Services SDK for iOS ArrowDB and Arrow Push - [https://wiki.appcelerator.org/display/guides2/Appcelerator+Platform+Services+SDK+for+iOS+ArrowDB+and+Arrow+Push]  ArrowDB SDK for Node.js - [https://wiki.appcelerator.org/display/guides2/ArrowDB+SDK+for+Node.js]   Custom Objects and Fields - [https://wiki.appcelerator.org/display/guides2/Custom+Objects+and+Fields]  Relational Fields - [https://wiki.appcelerator.org/display/guides2/Relational+Fields]  Search and Query APIs - [https://wiki.appcelerator.org/display/guides2/Search+and+Query+APIs]  Admin Access - [https://wiki.appcelerator.org/display/guides2/Admin+Access]  Atomic Increment Operator - [https://wiki.appcelerator.org/display/guides2/Atomic+Increment+Operator]  Troubleshooting Guide - [https://wiki.appcelerator.org/display/guides2/Troubleshooting+Guide]"
Answer: 230223.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: "Review API Runtime Services documentation for the following pages and confirm whether or not any updates are necessary for the upcoming release:    API Runtime Services Best Practices - [https://wiki.appcelerator.org/display/guides2/API+Runtime+Services+Best+Practices]  API Runtime Services Command-Line Interface Reference - [https://wiki.appcelerator.org/display/guides2/API+Runtime+Services+Command-Line+Interface+Reference]  Migrate an Application to Arrow Cloud 1.2.0 - [https://wiki.appcelerator.org/display/guides2/Migrate+an+Application+to+Arrow+Cloud+1.2.0]  In-place App Upgrading - [https://wiki.appcelerator.org/display/guides2/In-place+App+Upgrading]  Preventing Man-in-the-middle Attacks for API Runtime Services API Calls - [https://wiki.appcelerator.org/display/guides2/Preventing+Man-in-the-middle+Attacks+for+API+Runtime+Services+API+Calls]"
Answer: 39052.0

User story: "We need a new page in the documentation wiki for API Builder for API Builder -> API Builder CLI.  This page should link to API Runtime Services -> CLI page until API Builder gets its own CLI."
Answer: 50558.0

User story: "Following API Builder documentation pages need to be reviewed for any updates or changes in regards to the next release:    Connectors - [https://wiki.appcelerator.org/display/guides2/API+Builder+Connectors]  API Builder Docs - [https://wiki.appcelerator.org/display/guides2/API+Builder+Docs]  Associate API Builder Applications with Client Applications - [https://wiki.appcelerator.org/display/guides2/Associate+API+Builder+Applications+with+Client+Applications]  Migrating Node.ACS Applications to API Builder - [https://wiki.appcelerator.org/display/guides2/Migrating+Node.ACS+Applications+to+API+Builder]  Guide for API Builder SDK - [https://wiki.appcelerator.org/display/guides2/Guide+for+API+Builder+SDK]  "
Answer: 39023.0

User story: "Following documentation pages for API Builder needs updating:    Arrow Project -> Artifacts -> Models: [https://wiki.appcelerator.org/display/guides2/Arrow+Models]  Arrow Project -> Artifacts -> APIs: [https://wiki.appcelerator.org/display/guides2/Arrow+APIs]  Arrow Project -> Artifacts -> Blocks (Legacy): [https://wiki.appcelerator.org/display/guides2/Arrow+Blocks]  API Builder Console - [https://wiki.appcelerator.org/display/guides2/API+Builder+Console]  "
Answer: 43331.0

User story: "We need a new page in the documentation wiki for API Builder for API Builder -> Swagger Specifications.  Please reach out to Jamie Peabody/<USER>for technical details."
Answer: 31561.0

User story: "We need a new page in the documentation wiki for API Builder for API Builder -> Code Blocks.  Please reach out to Jamie Peabody/<USER>for technical details."
Answer: 31516.0

User story: "We need a new page in the documentation wiki for API Builder for API Builder -> Schemas.  Please reach out to Jamie Peabody/<USER>for technical details."
Answer: 43333.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 a new page in the documentation wiki for API Builder for API Builder -> Flows.  Please reach out to Jamie Peabody/<USER>for technical details."
Answer: 31573.0

User story: "We need a new page in the documentation wiki for API Builder for API Builder -> API Endpoints.  Please reach out to Jamie Peabody/<USER>for technical details."
Answer: 31506.0

User story: "The Dashboard and CLI are essential components for any user of API Builder. As such this information should be ported over to the Axway docs portal as well, so that a person using that doc repo can get all the information needed to use the product right there."
Answer: 30243.0

User story: "The following tasks needs to be reviewed on all the docs Lisa has generated or modified for the Arrow documentation split project:  * headers with links  * content correctness (comparing content against it's Github source)  * heading levels  * Odd page titles (colons, extra hyphens, etc)  * Correct and operational links  * Correct code sample formatting (wide code samples inside a table)  * Spelling/grammar  * Moving any comments to the JIRA ticket so they won't be visible once the pages go live    Previously, the following items have already been identified and needs reviewed accordingly:  * Review the Android SDK link on Getting Started: QuickStart Guide. I believe Lisa marked this one because she wasn't sure the URL.  * There is one page that doesn't have a localized image. The image sourced is called verify_new_user.png and its from the arrowdb/latest/guides/android page?  * ArrowDB and Push has a link to http://docs.appcelerator.com/cloud/latest/ which is the outdated site. I'll look for the current site and provide you with the correct URL."
Answer: 8824.0

User story: "I did some updates to the docs:  - Update all platform icons to retina size  - Replace outdated icons  - Fix dead links"
Answer: 709744.0

User story: "Please see si-356 for more deetails .we should document this requirement "
Answer: 154980.0

User story: "we have seen strange issues with nfs server, we should document always rebooting systems when redeploying the cluster "
Answer: 154919.0

User story: "Currently the Node support says that we support Node.js 10.X or later. This needs to be changed to be 4.2.0 as the minimum, with a max version of probably 6.X.    I am unsure if we need to keep a historical list of supported Node.js versions (similar to the Xcode and Ti SDK compatibility matrix) but it should be something like the below. I am basing the minimum version numbers off what we would declare as a minimum in Studio, so it might be that some pieces do work with a unlisted version.      ||Release Version||Min Node||Max node||  |6.0.0-latest|4.2.0|6.X|  |5.1.0-6.0.0|0.12.7|4.X|"
Answer: 1068892.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: "Google has transitioned from GCM to FCM technology for push.    The process is different now, and there are two ways to get a key:  1) Start in firebase, and generate a new project  2) In firebase, import your GCM-enabled project and generate a key.    We seem to support FCM at the present, but Google may continue to make changes."
Answer: 1354685.0

User story: "Review the current state of the Arrow Builder documentation and consider what is changing in 1.10.0.    https://wiki.appcelerator.org/display/guides2/Arrow+Builder"
Answer: 66631.0

User story: "Create drafts of all the new pages of all the new (and old) features (either new or reskinned).,"
Answer: 69424.0

User story: "Create an outline of the new UI based on information provided by Tyrus and the temp build."
Answer: 7267.0

User story: Specify supported Arrow Model Field data types    Online docs (Guide) for models/fields (http://docs.appcelerator.com/platform/latest/#!/guide/Arrow_Models) claims that:    "The field type (e.g., ‘string’). Type can be any valid JavaScript primitive type. Type can be specified as a string (e.g., ‘string’) or by the type class (e.g., String)."    From the screen shot below, we support primitive type plus others (e.g. array, date)
Answer: 10934.0

User story: "h5.Description    Upgrading V8 means recompiling native android modules, We updated our core set in TIMOB-19794 but as the community will need to do this too we should document how to do it.    From Chris' comment on that ticket it's basically the below, all of the below refer to properties in the manifest file. The user must be using NDK11 (NDK12 might work but I think NDK11 is what we're going with), and either set that in Studio or by using ti config android.ndkPath    {code}  bump the module's version up to the next major (i.e. 2.3.1 -> 3.0.0)  bump the module's apiversion to 3 (for Android)  bump the minsdk to 6.0.0 (for Android)  {code}    Also there is a change documented in this commit https://github.com/appcelerator/titanium_mobile/pull/8306/commits/6580b5ee080cbd9cfd96f0dbdc6e31390c72a20d I think this isn't a new in 6 thing but seeing as the templates were only updated there might be a few modules still using the old code    {code}  import org.appcelerator.titanium.util.Log;     import org.appcelerator.titanium.util.TiConfig;  {code}    {code}  import org.appcelerator.kroll.common.Log;  import org.appcelerator.kroll.common.TiConfig;  {code}"
Answer: 629373.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 contribute alloy templates via rubles, add the following block to bundle.rb:      {code:java}  project_template "Alloy Template Test" do |t|      t.type = :titanium_mobile      t.location = "templates/slider.zip"      t.description = "Test Alloy templates"      t.tags = ['Alloy']  end  {code}      The type and tags need to be what are shown. The location points to the zip that contains files to be added or overwritten after the default alloy project is created.    While creating a zip file make sure your zipping only Alloy project contents.    https://jira.appcelerator.org/browse/TISTUD-8597  
Answer: 15022.0

User story: "Update and publish https://wiki.appcelerator.org/display/~<USER>Arrow+Cloud+1.5.3+Release+Note "
Answer: 31357.0

User story: "Based on a report generated by validateAll.sh, there are several dozen yaml files that contain numerous errors."
Answer: 16042.0

User story: "Create and/or update release notes for all products"
Answer: 61.0

User story: "On https://docs.appcelerator.com/platform/latest/#!/guide/iOS_Launch_Files-section-46245490_iOSLaunchFiles-OptionB:UseacustomStoryboard, it says that for classic apps the custom storyboard must go in {{Resources/ios}}, but it's actually {{platform/ios}}."
Answer: 49.0

User story: "Gather and publish CLI 5.5.0.RC release note."
Answer: 7039.0

User story: "Gather and publish the SDK 5.5.0.RC release note."
Answer: 7040.0

User story: "Gather and publish release note for Dashboard 4.9.0."
Answer: 5996.0

User story: "see nodejs-2478"
Answer: 1139.0

User story: - Visit http://docs.appcelerator.com/platform/latest/#!/api/Arrow.Block  - Just above "Properties" section, there is the line "Alternatively, you can define your Blocks using JavaScript files. For details, see the Arrow Block guide."  - The link Arrow Block guide doesn't exist.     Please link to the right content
Answer: 4853.0

User story: For the release notes for 5.5.0, there's few worthy mentions and things to do:    https://wiki.appcelerator.org/display/guides2/Titanium+Compatibility+Matrix#TitaniumCompatibilityMatrix-Xcode  This compatibility Matrix has to be updated such that:  |Titanium SDK Version|Min Xcode Version|Max Xcode Version|  |5.0.0 - 5.3.1|6.0.X|7.3.x|  |5.4.0|7.3.x|7.3.x|  |5.5.0|7.3.x|8.0.x|  |6.0.0 - latest|8.0.x|8.x.x|    And these:  - Team id is now required in the tiapp.xml when building an app with a watch extension and Xcode 8.  - projects will have "SWIFT_VERSION" set to "3.0"  - Removed old watchos2 template in favor of existing watchos2-objc template.  - Min iOS SDK version is set to 8.0 by default if not explicitly set in the tiapp.xml when compiling using Xcode 8.
Answer: 22330.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: "Appcelerator Studio is only available in 32-bit version. However, it can be Installed in 64-bit and 32-bit OS environments. Since studio is a 32-bit, it requires 32-bit Java run-time environment to launch the Appcelerator studio.    During studio installation, it detects and installs 32-bit JDK if it's not found in the system, but it won't set that as a default Java environment.If you are unable to launch the studio in Windows OS 64 bit machines, then probably, studio was unable to find the 32 bit JDK version.    Please find the error in the screenshot which occurred due to invalid JDK bit version.  !Studio_launch_issue.png|thumbnail!    If your default Java environment is 64 bit and if you want to set 32-bit Java to Appcelerator studio, then you can add below argument in the *AppceleratorStudio.ini*  file.  It can be found in the Installation directory.      {code:java}  -vm  C:\Program Files(x86)\Java\jdk1.7.0_71\bin\javaw.exe  {code}  "
Answer: 124664.0

User story: "If you visit http://docs.appcelerator.com/platform/latest/#!/guide/User_Interface_Deep_Dives, the link to get started at the bottom of the page jumps directly to tableView, passing ListView.     Also, there is no mention of ListView on the summary page."
Answer: 3367.0

User story: "The admin parameter is missed in the doc http://docs.appcelerator.com/arrowdb/latest/#!/api/Users-method-create"
Answer: 9254.0

User story: "Axway people need good understanding of how our cluster works to be able to work with it.    To share knowledge in effective way we need better documentation.    Please, create diagram of running production cluster with nodes and services and links between them.    [~<USER> Please suggest tools and clipart/styles to use. So our documentation will be consistent for all products and teams. "
Answer: 46036.0

User story: "currently the doc still says 25M as limit it should be changed to 100m    http://docs.appcelerator.com/arrowdb/latest/#!/api/Files still mentions 25M  http://docs.appcelerator.com/arrowdb/latest/#!/api/Photos doesn't mention it today "
Answer: 354.0

User story: Work with various developers to get the https://wiki.appcelerator.org/display/PartnerDocs/Partners+Home space/guide organized and finalized into a PDF format that can be delivered to Axway.    Background: the content in the fore mentioned space needs to be delivered to Axway in standardized PDF (see attachments). Once the PDF has been generated, it needs to be uploaded to Sphere where the Product Manager will approve the PDF file. I believe there is a tool called Webliv that will be used to upload this document to it can automatically be pushed into Sphere. (Speak with Gerard Grimaldi as he is the Sphere Product Manager.) Once everything is in "place" and permissions granted/set, the document can be uploaded to Webliv.
Answer: 184199.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: "With the Installr app integration, studio users are able to upload the generated app to app preview.    iOS App preview  https://jira.appcelerator.org/browse/TISTUD-8009     Android App preview:  https://jira.appcelerator.org/browse/TISTUD-8010  "
Answer: 258194.0

User story: "nodejs-2435 has sample code. also please make sure to use node 0.12.7 or above "
Answer: 738647.0

User story: "h6. Issue Description    LisView Docs are only showing windows info.     http://docs.appcelerator.com/platform/latest/#!/api/Titanium.UI.ListView"
Answer: 119697.0

User story: "currently geo search is buried in https://docs.appcelerator.com/arrowdb/latest/#!/guide/search_query without a tag.     we have users not being able to find out how to do geo search from     https://docs.appcelerator.com/arrowdb/latest/#!/guide/geo  https://docs.appcelerator.com/arrowdb/latest/#!/guide/customfields    It would be nice if this can be clarified. "
Answer: 285349.0

User story: If we went through the link below    http://docs.appcelerator.com/platform/latest/#!/guide/SSL_Certificate_Store_Support_for_HTTP_Clients, in which it says (for iOS) we need to include require a module called *com.certtest* And it says the following lines:    {code}  // References a file called server.p12 in the Resources directory    var cert = Ti.Filesystem.getFile(Ti.Filesystem.resourcesDirectory, "server.p12”);  / Call the module method and send the HTTPClient object  // to set the clientCertificateIdentity property  certificateStore.loadP12Cert(httpClient, cert, 'password');  httpClient.open("GET", url);  httpClient.send();    {code}     There should be detailed decription about  p12 certificate and how can we find the module  in the documentation.      
Answer: 1441190.0

User story: "h6. Issue description    Persistent demo app link returns a 404 http://docs.appcelerator.com/platform/latest/#!/guide/Choosing_a_Persistence_Strategy_for_Your_Application-section-29004899_ChoosingaPersistenceStrategyforYourApplication-Properties    Broken link: https://github.com/<USER>Persistence    Screen shot attached. "
Answer: 1230.0

User story: "The self-install project has had a lot of re-work done to it since it began. https://github.com/appcelerator/arrowcloud-deploy/  Epic -> https://jira.appcelerator.org/browse/SI-16    So far it is in a pre-beta/alpha state https://github.com/appcelerator/arrowcloud-deploy/releases/tag/v0.0.1    The main documents we have on the Self-Install project are:   https://wiki.appcelerator.org/pages/viewpage.action?pageId=43318008  https://wiki.appcelerator.org/display/cls/How+to+use+the+Arrow+Self+Install+Tool  https://wiki.appcelerator.org/display/PartnerDocs/VMware+Configuration  https://wiki.appcelerator.org/display/DevOps/vSphere+Web+Client+Image+Deployment  https://wiki.appcelerator.org/display/cls/Creating+An+Amazon+Web+Services+Cluster+for+the+Self+Install+Tool    "
Answer: 2617.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 wonder if we should generate the API reference from the current (now 5_2_X) branch instead of master?    *Pros*    * We wouldn't confuse the user with upcoming changes in general.  * In particular renames of constants are problematic. The constant itself would show _since_ version, but the properties where they can be used do not. Only if the user links through to the constant reference would he see _since_, but with no way to find the constant for older versions.    *Cons*    * Early adopters wouldn't have a reference of upcoming changes.  * Changes to API references would need to be pushed to both master and current branch, which will without a doubt not always happen - in particular with community contributions. "
Answer: 927837.0

User story: "We have a compatibility matrix for Titanium here:  http://docs.appcelerator.com/platform/latest/#!/guide/Titanium_Compatibility_Matrix    But now we have the Unified CLI which embeds versions of the Titanium, Alloy and ACS CLI, things have become more complicated.    We need a compatibility matrix that tells you:    * Which Unified CLI cores are compatible with which Titanium SDKs.  * Which Unified CLI cores include which version of Alloy.  * Which Unified CLI cores are compatible with which NodeJS versions.    And some I probably forget."
Answer: 253929.0

User story: "TIMOB-20489 requires module developers to use the CLI to build instead of the (for some time already) deprecated {{build.py}} from Ti 5.2.1 on. The guides need to updated for this.    * http://docs.appcelerator.com/platform/latest/#!/guide/iOS_Module_Project-section-43288810_iOSModuleProject-BuildandPackagetheModule  * http://docs.appcelerator.com/platform/latest/#!/guide/iOS_Module_Quick_Start-section-43288582_iOSModuleQuickStart-BuildandPackagetheModule  * http://docs.appcelerator.com/platform/latest/#!/guide/Android_Module_Project-section-43289002_AndroidModuleProject-BuildandPackagetheModule  * http://docs.appcelerator.com/platform/latest/#!/guide/Android_Module_Quick_Start-section-43289022_AndroidModuleQuickStart-BuildandPackagetheModule    Some questions I'm sure [~<USER> can answer:    * When will {{build.py}} be removed from newly generated projects?  * Should we say that {{build.py}} is deprecated or remove?  * How exactly should {{ti build}} be used to build iOS (and Android?) modules?  * What if you use the Unified CLI? Is is {{appc run}} or {{appc ti build}}?  * What would be the exact steps to upgrade a module from using {{build.py}} to {{ti build}}?  * What additional steps need to be taken for modules that relied on the {{platform/iphone}} bug fixed by TIMOB-19694 which caused TIMOB-20489?"
Answer: 328764.0