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: "http://developer.android.com/google/gcm/gs.html    https://github.com/realpaul/titanium_mobile_modules/blob/86d31c25dc652b9d631e6401587feefa1213214d/android/cloudpush/documentation/index.md    https://wiki.appcelerator.org/pages/viewpage.action?pageId=37527848      Requires update to Ti.CloudPush and Cloud docs."
Answer: 7387.0

User story: "For updates to the Titanium SDK, Studio, etc."
Answer: 33409.0

User story: "We want to publish our analytics architecture out to the community:    https://wiki.appcelerator.org/display/pe/Ti+Analytics+Architecture    as a child under    https://wiki.appcelerator.org/display/guides2/Appendices    before doing so, we need to sanitize it slightly:    * We don't want to mention paid raw data export service (may change anytime)   * 1 hour inactivity period (we may change the duration)  * other potentially-private information    Once the page is created, please pass it along to [~<USER> and [~<USER> to confirm the page is ready for public consumption."
Answer: 10353.0

User story: "  "
Answer: 30193.0

User story: "Need to either recreate the project or edit the tiapp.xml and manually supply the cloud keys"
Answer: 2607.0

User story: "http://docs.appcelerator.com/"
Answer: 2652.0

User story: "(project in (11418,10034,10711,11115,11413) AND (project in (10711) OR project in (11413)) AND fixVersion in (15531,15532,15535,15536) AND labels in (release-note))  "
Answer: 2900.0

User story: "- Dynamic Styling  - ListView  - Module XML element"
Answer: 23185.0

User story: "Missing a lot of documentation for Titanium.UI.iOS.DocumentViewer"
Answer: 1476.0

User story: "In the older JSON format, we supported superclass/type information about each API (for example that Ti.UI.Button extended from Ti.UI.View).  In the new(er) JSCA format, this information isn't present.    For the new Ti.next project, we're treating the JSCA file as the core source of truth for the API and generating the API interface and implementation files from the JSCA file (treating it similar to IDL).      We need this information to properly provide inheritance and other type information."
Answer: 366199.0

User story:   ACS query  project in ("Appcelerator Cloud Services") AND fixVersion in ("Sprint 2013-12", "Sprint 2013-11", "Sprint 2013-10", "Sprint 2013-09", "Sprint 2013-08") AND labels=release-note ORDER BY Rank ASC    Node.ACS query  project in ("Node.ACS") AND fixVersion in ( "Sprint 2013-11", "Sprint 2013-10") AND labels=release-note ORDER BY Rank ASC
Answer: 5874.0

User story: Document "ignoreSslError" property for Titanium.UI.WebView API. Currently Android-only.    
Answer: 27467.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 Passbook module needs to be added to deploy.sh so the module's docs get generated and hosted with the Ti API docs."
Answer: 3215050.0

User story: "Items to note:  * Android Camera behavior change.  * Min iOS and Android SDK version changed to 5.x and 2.3.3, respectively."
Answer: 57201.0

User story: "Need a document describing the Appcelerator Dashboard."
Answer: 31682.0

User story: "The Newsstand module needs to be added to deploy.sh so the module's docs get generated and hosted with the Ti API docs."
Answer: 14634.0

User story: "Cleaning up servers and I noticed several hundred errors being dropped by docs.appcelerator.com. See attached output."
Answer: 263450.0

User story: "There will be a change, CLOUDSRV-2325, that <script> tag inside email_template body or subject will be removed.  Will need a documentation that users shouldn't be inserting any <script> tag inside body or subject of email_template, for security reason."
Answer: 2717.0

User story: ACS Like documentation does not describe how to pass session id to the server in a REST API call - suggest to update the docs    http://cloud.appcelerator.com/docs/api/v1/likes/create    describes the create like    No way to know how to use the session id    According to Wei (and I tested this to be working with Wei's suggestion):    "Use _session_id and make sure to pass it in URL"    e.g.    xhr.open("POST", "https://api.cloud.appcelerator.com/v1/likes/create.json?key=xxxxxxxxx&_session_id="+Alloy.Globals.sessionid);   xhr.send("custom_object_id="+id);
Answer: 260848.0

User story: "Related bugs include TIMOB-12103, TIMOB-13361 but not much info there. See Eric and Chris for more."
Answer: 26106.0

User story: "For TISTUD-1921, we need to be ble to point to a remote service (created by another user), much the same way we point to a service created by the current user.    In lieu of a mechanism, we should document the process for doing this manually."
Answer: 83523.0

User story: "Added to existing node docs site here:    https://github.com/appcelerator/node-acs-docs/pull/8/files    Port these changes to new doc site."
Answer: 21769.0

User story: "Update CLI reference with new platforms (tizen, blackberry) and check options."
Answer: 201664.0

User story: "Network now shown on iOS debug on device dialog. Update screenshot (and text if appropriate).    See TIMOB-11838 for info."
Answer: 8438.0

User story: "We should generate the parity report as part of every build. A like candidate is part of the CI loop after the documentation is generated. We can link to this on the build website."
Answer: 982588.0

User story: "Document the new ListView Module. This includes:    * Creating and editing a guide similar to http://docs.appcelerator.com/titanium/latest/#!/guide/TableViews  * Creating and editing a guide explaining how to transition from TableView to ListView"
Answer: 24029.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 manifest file that gets created for all new projects is not used and should be removed from the create project command.    Deprecate in 3.1.0 release notes; remove support in 3.2."
Answer: 24181.0

User story: "This is a reminder as much as anything, but we need to begin having a conversation with the docs team about documenting the code processor    This could be started with the documentation located here: https://github.com/appcelerator/titanium-code-processor"
Answer: 216154.0

User story: "The documentation for requires() (http://docs.appcelerator.com/titanium/latest/#!/api/Global-method-require) should include information about where files need to be located in an Alloy project. From the Appcelerator Q&A and my own testing, the CommonJS modules should be in app/lib and everything else then works as it should."
Answer: 15715.0

User story: "When there is an ACS update detected in Studio, we would open an update dialog with release notes information (please see the screenshot in TISTUD-2513), but currently the content is hard-coded in Studio and pretty minimal. The suggestion is to have ACS provide a change log page that will get updated each time a new version is pushed. The link could be https://github.com/appcelerator/nettle/blob/master/CHANGELOG.md, and the content could be something like the following:    {code}  0.2.43  --------    * Updated widgets, added new button-grid widget.    * Removed node-appc dependency.    0.2.42  --------    * reinvented the world  {code}    "
Answer: 222344.0

User story: "The process itself is pretty simple--we can post-process the JSDuck output to create a downloadable version of the docs that uses an index.html instead of index.php so users can access it from a local drive.    However, to make this scalable, we should incorporate it into the tools so that we can build this without a lot of added effort."
Answer: 747446.0

User story: According to Marco Ferreira, "I noticed when deploying the app to the device (adhoc and installing with iTunes) the app icon always gets the gloss, which means its not respecting the UIPrerenderedIcon property in tiapp.xml."    Basically, if you use a custom info.plist in an iOS project that has values found in the tiapp.xml, some stomping can occur. Custom plists, based on the oinked ticket, are discouraged.
Answer: 14492.0

User story: Based on TIMOB-11752, we "fixed" the issue as a side effect of fixing a different issue involving a memory leak. Although globals are now supported, they are discouraged and deprecated. We should note this in the documentation that they may no longer be available at any point.
Answer: 55886.0

User story: "Separate the Alloy Documentation into separate topics"
Answer: 51.0

User story: "This task covers:    * updating the release notes   * generating the documentation package  * pushing to staging and prod  * checkin of final release notes to git    This bug can be closed when the release notes are checked in.  "
Answer: 100046.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 encompasses the following subtasks    * Update guides to show Tizen as a platform option (where relevant)  * Ensure that the Tizen platform support makes it into the API docs  * Create a getting started guide similar to the one for [BlackBerry|http://docs.appcelerator.com/titanium/latest/#!/guide/BlackBerry_Support]"
Answer: 83955.0

User story: "The new code processor feature inside Titanium Studio will provide information on errors and warnings encountered while validating a user's source code."
Answer: 87739.0

User story: "The guide [here|http://docs.appcelerator.com/titanium/latest/#!/guide/BlackBerry_Support] needs to be updated with the latest information on configuring and installing BlackBerry projects"
Answer: 122315.0

User story: "This new feature allows for Studio users to debug Node.ACS applications."
Answer: 164051.0

User story: "This new feature allows for Studio users to get content assist when creating alloy applications. It unclear if this goes into a new section on Alloy, or in the existing content assist section (http://docs.appcelerator.com/titanium/latest/#!/guide/Displaying_Content_Assist)"
Answer: 69432.0

User story: "This new feature allows for Studio users to debug Alloy applications."
Answer: 71921.0

User story: "The new SDK Builder replaces the existing SCons functionality. We will likely need to update at least the following two documents:    * http://docs.appcelerator.com/titanium/latest/#!/guide/Building_the_Titanium_SDK_From_Source  * http://docs.appcelerator.com/titanium/latest/#!/guide/Pull_Request_Guide"
Answer: 345746.0

User story: "A guide explaining how to use the new LiveView tool inside Studio."
Answer: 181672.0

User story: "A guide explaining how to use the new profiling tool inside Studio."
Answer: 77894.0

User story: "Document the new Google Maps V2 Module. This includes:    * Reviewing the existing API documentation  * Creating and editing a guide that describes how to use the new module (similar to http://docs.appcelerator.com/titanium/latest/#!/guide/Native_Maps_and_Annotations)"
Answer: 27375.0

User story: "Document the new Facebook Module. This includes:    * Reviewing the existing API documentation  * Creating and editing a guide that describes how to use the new module"
Answer: 47484.0

User story: "Document the new ListView Module. This includes:    * Reviewing the existing API documentation  * Creating and editing a guide similar to http://docs.appcelerator.com/titanium/latest/#!/guide/TableViews  * Creating and editing a guide explaining how to transition from TableView to ListView"
Answer: 63766.0

User story: "Update Matrix to Xcode 4.6 and iOS 6.1."
Answer: 202855.0

User story: To enable crawling by our internal nutch crawler, we need to generate a sitemap-like-file that lists the "ugly" URLs (i.e., using _escaped_fragment_ format). This is different from the format we'd produce for an actual sitemap, which should use the "pretty" URLs (using #!).
Answer: 11347.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: "Some changes related to validate -- no more isValid method, which is used in one example.  Need to review the backbone changelog for info."
Answer: 878104.0

User story: "ALOY-402 contains a series of deprecated APIs that will be removed in Alloy 1.0.0, which is to coincide with the Titanium 3.0.2 release. The guides and API docs need to reflect this. Fortunately, I don't think there will be a ton of effort needed by the TIDOC team on this. I think most of the included deprecated APIs have already been removed/replaced in the guides/examples, and the regen of the API docs will rely solely on me removing the old APIs from the Alloy code, which includes the inline docs.    We just need to make sure there's no references to these old APIs anymore as they pass from deprecated to deleted."
Answer: 33834.0

User story: "Web console shows the error:    QUOTA_EXCEEDED_ERR: DOM Exception 22: An attempt was made to add something to storage that exceeded the quota.    This also occurs on vanilla JSDuck, like docs.sencha.com, and appears to be because in private browsing mode, Safari advertises local storage, but won't let the app write to it. See, for example:    https://github.com/appendto/amplify/commit/a1f4517d4d4b4ba8cfbc680fb7632dca4b5f5ede    For a possible solution.    As a workaround--don't browse in private mode, and the docs should work fine.    "
Answer: 2533175.0

User story: Do to the fact that Backbone eventing needs to be removed from Alloy-generated Titanium proxies for its GA (ALOY-455), we also need to remove any references to proxies using Backbone eventing in the documentation as well. Removing the entire "Event Handling" section found here would need to be done: http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Controllers-section-34636384_AlloyControllers-EventHandling    In addition, any other place in the Alloy guides where Backbone eventing via on(), off(), or trigger() on proxies needs to be removed as well. Again, this should coincide with the 3.0.2 release.
Answer: 19495.0

User story: "See review comments here:    https://github.com/appcelerator/titanium_mobile/pull/3603    "
Answer: 46672.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: "*IMPORTANT*: Calling destroy() will be critical for preventing memory leaks in alloy code that employs model-view binding.    We will be adding a *destroy()* function to all controllers. Under the hood this will be added as:    {code:javascript}  exports.destroy = function() {      // auto-generated destroy code  }  {code}    In its initial form, the destroy() function will be used only to remove event listeners tied to global and local references to models/collections, which are created when model-view binding is employed. A typical example of using it would be when you close a controller's window if it or any of its UI components used model-view binding.    {code:javascript}  $.win.on('close', function() {      $.destroy(); // clean up binding  });  {code}    This will prevent any possible memory leaks, specifically when making bindings against a global model (Alloy.Models) or collection (Alloy.Collections).  "
Answer: 18470.0

User story: "Namely...  * datetime is replaced by moment.js  * can accept a few Ti.UI.Window and Ti.UI.TableView properties in markup  * '--platform' option for alloy generate command  "
Answer: 28771.0

User story: "Currently, we use JSDuck's built-in support for Google's crawlable AJAX web sites spec. However, the HTML snapshots are generated at a page level--so every property and method under Ti.UI has a unique URL, but generates exactly the same HTML snapshot. This leads to somewhat random search results.    It would be better if:    http://docs.appcelerator.com/titanium/3.0/#!/api/Titanium.UI.View    Returned the full page, and    http://docs.appcelerator.com/titanium/3.0/#!/api/Titanium.UI.View-method-animate    Returned a snapshot of just the animate method.    This would also facilitate using google custom search for our site search, since methods, properties and events would be properly indexed (by their own contents, instead of by the contents of the parent object).    This would also ensure that the preview text associated with the URL is more accurate.  "
Answer: 55680.0

User story: I have a few high-level "rules" for Alloy development by which developers should abide. These don't correspond to specific APIs or parts of Alloy, but are instead general rules that Alloy developers should be aware of, or at the very least, that we have documented. Here's the brief list:    * - Developers should not use double underscore prefixes on variables, properties, or function names. They are reserved for use in Alloy. If you use them, there is potential for conflicts and unexpected behavior.  * - Javascript reserved words cannot be used as IDs. At this time this listing can be found here: https://github.com/appcelerator/alloy/blob/master/Alloy/common/constants.js#L54-L64    That's it for now. Once an area in the guides is designated for these types of rules, I will more directly submit to those guides.
Answer: 466.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 page at http://docs.appcelerator.com/titanium/latest/#!/guide/Icons_and_Splash_Screens is missing many of the Android screen sizes/densities, at least one of the splash screen size recommendations is wrong, and it has incorrect information on icon size. It also does not include any information on Android tablet dimensions.    See http://developer.android.com/distribute/googleplay/quality/tablet.html#use-tablet-icons for icon information    See http://developer.android.com/design/style/metrics-grids.html for at least some info on size and density values, though those will have to be mapped to Titanium's directory names for resources."
Answer: 23578.0

User story: "Node.ACS supports node.js 0.8.14 and above. We haven't tested 0.9.0 and above which are the developer versions. Please include this information in http://docs.appcelerator.com/titanium/3.0/#!/guide/Node.ACS"
Answer: 11291.0

User story: "When exporting the wiki content, the document contains some weird formatting artifacts that need post-processing.    Unfortunately, the new Confluence version does not appear to have corrected this issue."
Answer: 2619293.0

User story: "The installation/quickstart needs to be rationalized. Currently, way too long and wandering. Plus, it's unclear what's required for CLI use versus Studio use. Split into two streamlined paths--one for CLI and one for Studio."
Answer: 175578.0

User story: update the modules documentation to include the Android commonJS "Native" module, similar to what is outlined here  http://docs.appcelerator.com/titanium/2.1/#!/guide/iOS_Module_Development_Guide-section-29004946_iOSModuleDevelopmentGuide-BuildingJavaScriptNativeModules
Answer: 33481.0

User story: "All the usual rigamarole."
Answer: 11672.0

User story: "Keep the docs updated for new features added in 0.3.1 and 0.3.2."
Answer: 13938.0

User story: "Document this new feature for 0.3.2.     May slip out of this sprint if the feature comes together late in Sprint 23."
Answer: 39917.0

User story: "Edit current model docs, add more examples, address any questions that have come up in the mailing list, and prepare for the new model-view binding feature (which will be a separate ticket)."
Answer: 39874.0

User story: "Work with IT to see if we can crawl the docs when we generate with -seo option to JSDuck."
Answer: 9960.0

User story: "Right now, description is a meta tag, so it gets shuffled in after the default value. That looks wrong, so we should fixify it."
Answer: 38796.0

User story: "Add installation and setup instructions for BB tools.    I expect this task will involve some installation testing, so allowing extra time for trial and error."
Answer: 51884.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 Alloy quick start is in a one-off location: http://projects.appcelerator.com/alloy/docs/Alloy-bootstrap/index.html    Eventually it would be nice to have this accessible as part of the docs.appcelerator.com site. The current twitter bootstrap format of the quick start causes problems with the current JSDuck documentation. In talks with <USER>he indicated that a new experimental approach to the inclusion of content for docs.appcelerator.com might allow for the alloy quick start to be shown in its current format. This however will likely require some significant effort on the part of the TIDOC team. "
Answer: 413488.0

User story: "Currently, we have a three-line, static footer at the bottom of the docs site  (http://docs.appcelerator.com/titanium/latest/).     The existing footer was created to match our corporate website style. But it takes up a lot of spaces, and our corporate style has now changed to put the footer at the bottom of the scrollable content, rather than fixed at the bottom of the browser window.     I would like to have a less obtrusive footer. I'd like to get mockups of a few approaches for approval by The Powers That Be.    Alternatives I can think of are:    - A version of the current header (or whatever corporate is using this week), attached to the bottom of the main content. This would need to be adjusted to fit in a narrower space than the current footer.    - A single-line fixed footer, like the very understated footer on the sencha docs:    http://docs.sencha.com/ext-js/4-1/#!/api      "
Answer: 1333600.0

User story: "The Screen sizes in the Distribution guides for Android and iOS do not take into account all resolutions    http://docs.appcelerator.com/titanium/latest/#!/guide/Distributing_Android_apps    http://docs.appcelerator.com/titanium/latest/#!/guide/Distributing_iOS_apps    The iOS sizes have been updated on the wiki: https://wiki.appcelerator.org/display/guides/Distributing+iOS+apps"
Answer: 8742.0

User story: "This may be installed automatically if users are using Studio (verify this), but users who are using scons and not using Studio will need to install Node.    Also, may need to configure the npm node_modules install location to avoid permission errors--for example, setting prefix to $HOME so everything is installed relative to the user's home so they don't need to run npm as root or chmod the install location to be globally writable.    For example, add:    NPM_CONFIG_PREFIX=$HOME  export NPM_CONFIG_PREFIX    To your .bash_profile and add $HOME/bin to your path.      "
Answer: 32834.0

User story: "Task for Arthur"
Answer: 12028.0

User story: "This task covers:    * updating the release notes   * generating the documentation package  * pushing to staging and prod  * checkin of final release notes to git    This bug can be closed when the release notes are checked in.  "
Answer: 27802.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 task covers:    * updating the release notes   * generating the documentation package  * pushing to staging and prod  * checkin of final release notes to git    This bug can be closed when the release notes are checked in.  "
Answer: 6602.0

User story: "Create a wiki page that lists:    * Curent pre-requisites for debugging on device  * Known common problems and ways to resolve them  * Use cases and workflows for iOS and Android. Some examples:  ** Device doesn't connect the first time. Timeout and reconnect option?  ** Network connection drops altogether. Currently there is no reconnect option as part of the protocol  ** Itunes not set up correctly.  ** Network not set up to support broadcast (http://en.wikipedia.org/wiki/Broadcasting_(networking))  ** IPv6 does not support broadcast, and instead supports multicast: http://en.wikipedia.org/wiki/IP_multicast. if we are using Bonjour, perhaps this is fine (see http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml)  ** ADB fails to connect    The document should suggest the areas in which our implementation is currently lacking, and the ways in which we can improve the experience."
Answer: 65206.0

User story: "Some tools error out on non-ASCII input. This mostly seems to be related to writing out output from the Python scripts.  "
Answer: 2684291.0

User story: "We should add some templates to pretty-print these at the end of the release notes.    "
Answer: 11553.0

User story: "Initial document for new CLI."
Answer: 48997.0

User story: "Break one-pager into separate QuickStart, APIs, CLI Reference, and Examples sections."
Answer: 37762.0

User story: "A nicely formatted list, for release to developers."
Answer: 20655.0

User story: "We should add some templates to pretty-print these at the end of the release notes.    "
Answer: 27367.0

User story: "Add release notes describing known issues, fixes, etc. for iOS 6."
Answer: 15517.0

User story: "referencing TIMOB-10885, the new iPhone 5 has a taller screen. Adding a specially-named splash screen to the project forces the app into working in this new mode rather than having black bars at top and bottom.    "
Answer: 16594.0

User story: "Need to set up CI build for documentation."
Answer: 905335.0

User story: "This document (https://wiki.appcelerator.org/display/guides2/Debugging+on+iOS+Devices) needs to be moved as a child of https://wiki.appcelerator.org/display/guides2/Debugging+Mobile+Applications after the 2.1.3 release."
Answer: 59648.0

User story: "Need to add navigation (pulldown) for switching doc sites.   Probably out of scope for 3.0; will re-evaluate next sprint."
Answer: 92352.0

User story: "We believe updating to the latest version of JSDuck may resolve several issues in our current doc system, including crashes on some iPad browsers and enabling search for guides content."
Answer: 14737.0

User story: "http://docs.appcelerator.com/titanium/2.0/index.html#!/api API Documentation missing SDK version. Screenshot attached."
Answer: 285407.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 current title in the browser bar for docs.appcelerator.com is "Appcelerator Titanium Mobile". It seems that is a bit too limiting given the scope of the documentation which I expect will ultimately reside there for 360, ACS, etc.    Suggestion is to remove the "Mobile" and replace with "Documentation"
Answer: 591072.0

User story: "In the generated docs, we shouldn't be seeing any links to the wiki (except perhaps to the community wiki). Links to guides, guides2, etc., should be flagged as errors as an additional safety precaution."
Answer: 100800.0

User story: "Android supports only one map per application, while iOS supports multiple. Our docs should reflect this. This is an Android limitation not Titanium. (While there are hacks/workarounds for Android native, we don't implement any of them as they all come with their own problems.)    Adding a second map throws:  java.lang.IllegalStateException: MapView already created. Android can support one MapView per Application.    Test with:    {code}  var win = Ti.UI.createWindow({   backgroundColor:'#000',   navBarHidden: true  });  var m1 = Ti.Map.createView({   height: '50%',   width: Ti.UI.FILL,   top: 0, left: 0,   region: {latitude:33.74511,longitude:-84.38993,animate:true,latitudeDelta:0.04, longitudeDelta:0.04},   userLocation: false,   regionFit: true  });  win.add(m1);    var m2 = Ti.Map.createView({   height: '50%',   width: Ti.UI.FILL,   top: (Ti.Platform.displayCaps.platformHeight / 2), left: 0,   region: {latitude:37.337681,longitude:-122.038193,animate:true,latitudeDelta:0.04, longitudeDelta:0.04},   userLocation: false,   regionFit: true  });  win.add(m2);  win.open();  {code}  "
Answer: 1399.0

User story: "In Android:  - Titanium.Map.SATELLITE_TYPE -> hybrid map  - Titanium.Map.HYBRID_TYPE -> nothing happens.    To test open KS:  Base UI -> Views -> Map View -> Menu Button -> Hyb and Sat    Tested in Android Emulator APIs 2.2  and Droid Device running 2.2.2    Helpdesk Ticket: http://support.appcelerator.com/tickets/KTM-16476-116/homepage"
Answer: 584915.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: "IOS has a new feature that allows dragging and dropping annotations on the map. This needs a doc update."
Answer: 15785.0

User story: "There are some obvious colors that we can use for backgrounds or anything, and some not so obvious.  It would be very useful to document all of the colors available, string values.    For iOS we have the following:  - black  - gray  - darkgray  - lightgray  - white  - red  - green  - blue  - cyan  - yellow  - magenta  - orange  - purple  - brown  - transparent  - stripped (iPhone only)  - aqua  - fuchsia  - lime  - maroon  - pink  - navy  - silver  - olive  - teal    For Android we have the following:  - black  - red  - purple  - orange  - gray  - darkgray  - lightgray  - cyan  - magenta  - transpare  - aqua  - fuchsia  - lime  - maroon  - pink  - navy  - silver  - olive  - teal           "
Answer: 10353.0

User story: h4. Problem description  Sometimes, when the users are implementing commonjs, they get into an error:    "too deep recursion".    We need to tell them about how to workaround it with:     {code}  <property name="ti.android.threadstacksize" type="int">32768</property>  {code}    This was necessary for Rhino support. Since we've removed Rhino, we can now deprecate this property.
Answer: 794913.0

User story: "Someone's gotta write em, yup?"
Answer: 7159.0

User story: "It should be documented that Android will only support integer values for the Slider  properties: value, min, max, maxRange, and minRange. If we are given a floating point value  it will be rounded down into an integer.  "
Answer: 111.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: "Various guides need to be updated to include Mobile web information. These include the following, each of which should probably be created as a sub-task to this ticket:    * [Supporting Multiple Platforms in a Single Codebase|https://wiki.appcelerator.org/display/guides2/Supporting+Multiple+Platforms+in+a+Single+Codebase]  ** Add Ti.Platform.name/osname values  ** Add Resources/mobileweb overrides directory info  * [Layouts, Positioning, and the View Hierarchy|https://wiki.appcelerator.org/display/guides2/Layouts%2C+Positioning%2C+and+the+View+Hierarchy]  ** Add pertinent info on positioning, etc. in mobile web  * [Event Handling|https://wiki.appcelerator.org/display/guides2/Event+Handling]  * [Icons and Splash Screens|https://wiki.appcelerator.org/display/guides2/Icons+and+Splash+Screens]  * Probably need to add limitations and specifics of local data storage to https://wiki.appcelerator.org/display/guides2/Working+with+Local+Data+Sources  * Media limitations (e.g. camera) in https://wiki.appcelerator.org/display/guides2/Working+with+Media+APIs  * Document the geolocation limitations and considerations, plus any mapping issues  * Add information in https://wiki.appcelerator.org/display/guides2/Integrating+Web+Content that covers iframe issues, cross-domain scripting and security issues, etc.  * [Modules|https://wiki.appcelerator.org/display/guides2/Using+Modules] section needs to note that mobile web can use only pure JS modules    (Changes that require an entire new section are covered in their own tickets.)  "
Answer: 54284.0

User story: "Titanium/Yahoo/Yahoo.yml"
Answer: 1396868.0

User story: "Titanium/XML/Attr.yml  Titanium/XML/CharacterData.yml  Titanium/XML/Document.yml  Titanium/XML/DocumentType.yml  Titanium/XML/DOMImplementation.yml  Titanium/XML/Element.yml  Titanium/XML/Entity.yml  Titanium/XML/NamedNodeMap.yml  Titanium/XML/Node.yml  Titanium/XML/NodeList.yml  Titanium/XML/Notation.yml  Titanium/XML/ProcessingInstruction.yml  Titanium/XML/Text.yml  Titanium/XML/XML.yml"
Answer: 1396874.0

User story: "Titanium/Utils/Utils.yml"
Answer: 13185.0

User story: "Titanium/UI/iPhone/ActivityIndicatorStyle.yml  Titanium/UI/iPhone/AnimationStyle.yml  Titanium/UI/iPhone/iPhone.yml  Titanium/UI/iPhone/NavigationGroup.yml  Titanium/UI/iPhone/ProgressBarStyle.yml  Titanium/UI/iPhone/RowAnimationStyle.yml  Titanium/UI/iPhone/ScrollIndicatorStyle.yml  Titanium/UI/iPhone/StatusBar.yml  Titanium/UI/iPhone/SystemButton.yml  Titanium/UI/iPhone/SystemButtonStyle.yml  Titanium/UI/iPhone/SystemIcon.yml  Titanium/UI/iPhone/TableViewCellSelectionStyle.yml  Titanium/UI/iPhone/TableViewScrollPosition.yml  Titanium/UI/iPhone/TableViewSeparatorStyle.yml  Titanium/UI/iPhone/TableViewStyle.yml"
Answer: 1396874.0

User story: "-Titanium/UI/iPad/DocumentViewer.yml- --> moved to iOS namespace  Titanium/UI/iPad/iPad.yml  Titanium/UI/iPad/Popover.yml  Titanium/UI/iPad/SplitWindow.yml"
Answer: 803771.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 following modules still need to be updated:    Titanium/UI/iOS/3DMatrix.yml  Titanium/UI/iOS/AdView.yml  "
Answer: 139835.0

User story: "Titanium/UI/Clipboard/Clipboard.yml"
Answer: 171165.0

User story: "Titanium/UI/Android/Android.yml"
Answer: 31581.0

User story: "Titanium/UI/2DMatrix.yml  Titanium/UI/ActivityIndicator.yml  Titanium/UI/AlertDialog.yml  Titanium/UI/Animation.yml  Titanium/UI/Button.yml  Titanium/UI/ButtonBar.yml  Titanium/UI/DashboardItem.yml  Titanium/UI/DashboardView.yml  Titanium/UI/EmailDialog.yml  Titanium/UI/Font.yml  Titanium/UI/ImageView.yml  Titanium/UI/Label.yml  Titanium/UI/Notification.yml  Titanium/UI/OptionDialog.yml  Titanium/UI/Picker.yml  Titanium/UI/PickerColumn.yml  Titanium/UI/PickerRow.yml  Titanium/UI/ProgressBar.yml  Titanium/UI/ScrollableView.yml  Titanium/UI/ScrollView.yml  Titanium/UI/SearchBar.yml  Titanium/UI/Slider.yml  Titanium/UI/Switch.yml  Titanium/UI/Tab.yml  Titanium/UI/TabbedBar.yml  Titanium/UI/TabGroup.yml  Titanium/UI/TableView.yml  Titanium/UI/TableViewRow.yml  Titanium/UI/TableViewSection.yml  Titanium/UI/TextArea.yml  Titanium/UI/TextField.yml  Titanium/UI/Toolbar.yml  Titanium/UI/UI.yml  Titanium/UI/View.yml  Titanium/UI/WebView.yml  Titanium/UI/Window.yml"
Answer: 48663.0

User story: "Titanium/Stream/Stream.yml"
Answer: 60726.0

User story: "Titanium/Platform/DisplayCaps.yml  Titanium/Platform/Platform.yml"
Answer: 51177.0

User story: "Titanium/Network/Socket/Socket.yml  Titanium/Network/Socket/TCP.yml"
Answer: 5479.0

User story: "Titanium/Network/BonjourBrowser.yml  Titanium/Network/BonjourService.yml  Titanium/Network/HTTPClient.yml  Titanium/Network/Network.yml  Titanium/Network/TCPSocket.yml"
Answer: 1396873.0

User story: "Titanium/Media/Android/Android.yml"
Answer: 50175.0

User story: "Titanium/Media/Media.yml      Titanium/Media/VideoPlayer.yml    Titanium/Media/AudioPlayer.yml      Titanium/Media/Sound.yml       Titanium/Media/AudioRecorder.yml      Titanium/Media/Item.yml      Titanium/Media/MusicPlayer.yml "
Answer: 191369.0

User story: "Titanium/Map/Annotation.yml  Titanium/Map/Map.yml  Titanium/Map/View.yml"
Answer: 13195.0

User story: "Titanium/Locale/Locale.yml"
Answer: 86162.0

User story: "Titanium/Gesture/Gesture.yml"
Answer: 54761.0

User story: "Titanium/Geolocation/Geolocation.yml"
Answer: 60736.0

User story: "Titanium/Filesystem/File.yml  Titanium/Filesystem/FileStream.yml  Titanium/Filesystem/Filesystem.yml"
Answer: 1396879.0

User story: "Titanium/Facebook/Facebook.yml  Titanium/Facebook/LoginButton.yml"
Answer: 31471.0

User story: "Titanium/Database/Database.yml  Titanium/Database/DB.yml  Titanium/Database/ResultSet.yml"
Answer: 5594.0

User story: "Titanium/Contacts/Contacts.yml  Titanium/Contacts/Group.yml  Titanium/Contacts/Person.yml"
Answer: 62954.0

User story: "Titanium/Codec/Codec.yml"
Answer: 159304.0

User story: "Titanium/App/Properties/Properties.yml"
Answer: 13202.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Titanium/App/iOS/BackgroundService.yml  Titanium/App/iOS/iOS.yml  Titanium/App/iOS/LocalNotification.yml"
Answer: 13203.0

User story: "Titanium/App/Android/Android.yml  Titanium/App/Android/R.yml"
Answer: 13204.0

User story: "Titanium/App/App.yml"
Answer: 13205.0

User story: "Titanium/API/API.yml"
Answer: 35698.0

User story: "Titanium/Android/NotificationManager/NotificationManager.yml"
Answer: 50186.0

User story: "Titanium/Android/Calendar/Alert.yml  Titanium/Android/Calendar/Calendar.yml  Titanium/Android/Calendar/CalendarProxy.yml  Titanium/Android/Calendar/Event.yml  Titanium/Android/Calendar/Reminder.yml"
Answer: 51406.0

User story: "Titanium/Android/Activity.yml  Titanium/Android/Android.yml  Titanium/Android/Intent.yml  Titanium/Android/Menu.yml  Titanium/Android/MenuItem.yml  Titanium/Android/Notification.yml  Titanium/Android/PendingIntent.yml  Titanium/Android/R.yml  Titanium/Android/RemoteViews.yml  Titanium/Android/Service.yml"
Answer: 160769.0

User story: "Titanium/Analytics/Analytics.yml"
Answer: 57226.0

User story: "Titanium/Accelerometer/Accelerometer.yml"
Answer: 140909.0

User story: "Titanium/Blob.yml  Titanium/BlobStream.yml  Titanium/Buffer.yml  Titanium/BufferStream.yml  Titanium/Event.yml  Titanium/IOStream.yml  Titanium/Module.yml  Titanium/Proxy.yml  Titanium/Titanium.yml"
Answer: 206977.0

User story: "Global/Global.yml  Global/String/String.yml"
Answer: 52790.0

User story: "Ti.UI.Window.orientationModes has unique behavior on Android that should be documented.  Specific attention should be payed to the treatment of reverse orientation modes and how the combination of orientation modes work.  For more details on the Android specific behavior, please contact <USER>"
Answer: 634.0

User story: "See parent issue for requirements."
Answer: 25582.0

User story: "document the Ti.UI.TextArea.scrollable property"
Answer: 1146.0

User story: "<USER>wrote:  {quote}Could you take a look at this ticket when you get the chance?  It's basically a chore to add platform notes for the mobile web platform.  I believe the format should be something like https://github.com/appcelerator/titanium_mobile/blob/master/apidoc/README.md  but I would double check with Marshall.  {quote}  "
Answer: 634111.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: *Story*    As an organization using an Indy Network, I need to adopt the Transaction Author Agreement at the time my legal team approves it, rather than coordinating closely with the network administrators for when to cut-over to a new agreement.    Current TAA flow   * Network governance adopts a TAA, and then publishes it on a web site.   * Users of the network can review the TAA.   * After the advisory period has expired, it is published to the ledger and immediately enforced and the old agreement is immediately retired.    Problems   * Users of the network have to wait to adopt the new TAA until the advisory period has expired and it is on the ledger even if they have already accepted it.   * Users of the network have to immediately switch versions of the TAA in their software at the time the new TAA is on the ledger.   * Users of the network can't store their acceptance in their software configuration until the TAA is on the ledger and the official hash is available.    Revised TAA flow   * Network governance adopts a TAA, and it enters the public advisory period.   * It is immediately put on the ledger.   * When the new agreement's public advisory period has ended and the old agreement is no longer acceptable, network governance marks the old agreement as retired.    *Acceptance Criteria*   * When a new TAA is put on the ledger, old agreements are not automatically rejected. Marking a TAA as "retired" is done in a separate transaction from adding a new TAA.   * A transaction that includes acceptance of any non-retired TAA should be accepted by the ledger.   * A query to the ledger for the TAA which does not specify a specific version should always return the newest TAA.   * Documentation is updated.    *Notes*   * The number of acceptable TAAs is determined by the network admin based on when agreements are marked as retired. It is expected that only one TAA will be active most of the time, but during a transition period two TAAs may be active. It is expected that there will never be more than two TAAs active at a time. However, we don't need to enforce that on the ledger.   * The current logic that a TAA can be accepted the day before it gets on the ledger (due to clock skew) should be preserved.
Answer: 41252.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: "*Story*   As a developer or QA analyzing load test results, I need to have all common errors and exception already grepped and reported, so that I can understand faster what's going on.    It would save a lot of time if load script automation could grep all common errors and exception in logs (each Node logs and journalctl).         *Acceptance criteria*    The result of load tests need to have the following information (as a report):   * How many transactions have been written on every node   * How many transaction expected to be written (from the load script point of view)   * How many view changes happened   * Graphs from each nodes   * Metrics summary from each node (`get_metrics` output)   * Get validator info result from each node   * Journalctk analysis:   ** output all exceptions (if any)   * Logs analysis:   ** All ERROR log messages   ** The following patterns:   *** `blacklisting`   *** `invalid BLS signature`   *** `request digest is incorrect`   *** `has incorrect digest`   *** `time not acceptable`   *** `incorrect state trie root`   *** `incorrect transaction tree root`   *** `has incorrect reject`   *** `error in plugin field`   *** `incorrect audit ledger`   *** <to be continued......>"
Answer: 41942.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: *Story*  As a transaction author, I need my transactions to be written to the ledger preserving me as the author without my needing to accept the responsibilities of an endorser so that I can focus on my business. Instead, I will have a business relationship with an endorser who will endorse my transactions.    *Goals*  * It is easy to tell from the ledger who is the endorser and who is the transaction author for each transaction.  * A transaction author can use a different transaction endorser for future transactions, including updates to attribs and key rotations.  * The transaction must use the author key to sign the transaction author agreement regardless of whether an endorser signature is also needed.    *Acceptance Criteria*  * Analyze the work required.  * Raise issues for completing the work.    *Notes*  * The transaction author field is intended to be used for all future permissions.  * The endorser field only needs to be recorded in order to:  ** Allow auditability, that the transaction was written with correct permissions  ** Allow the network administrator to bill the endorser for the write  * Sub-endorsers or chains of endorsers would be desirable for a global network, but are not required at this time. We recognize that in the future adding multiple levels of endorsers or delegated endorsers could be a breaking change.  ** Endorsers could be a list, but it would still require the transaction author to know all endorsers at the time the transaction is created. That list could be built off-ledger by sharing a draft transaction.  * Suggested user flow:  ** Transaction author identifies the need for creating a transaction  ** Transaction author identifies which endorser they want to use  ** Transaction author includes the DID of the endorser in the transaction, and signs the transaction.  ** Transaction author passes the signed transaction to the endorser  ** Endorser adds their signature  ** Endorser submits the multi-signed transaction to the ledger  ** If the endorser will not accept the transaction, and the transaction author wants to try a different endorser, the transaction author must recreate the transaction in order to include the new endorser DID.  * Token holders can also choose to "endorse" third party transactions so that they get submitted to the ledger. See [ST-508|https://sovrin.atlassian.net/browse/ST-608]
Answer: 16409.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: "*Story*  As an administrator of an Indy network, I want to be able to configure auth_rules such that new network users can write their own nyms to the public ledger so that the ledger can be managed in a completely decentralized way.    *Acceptance Criteria*  * The ledger can be configured so that new DIDs can be anchored without a signature from an entity already on the ledger.  ** The configuration happens in auth_rules.  * The transaction that anchors the DID is signed with the DID that will be added to the ledger.  ** This ensures that any transaction author agreements are signed.  ** This ensures that someone cannot anchor a DID that they do not control with their private keys.    *Notes*  * It is expected that decentralized public write access allows unknown users to anchor their own nym to the ledger if they provide payment through a payment plugin without going through an endorser for approval.  * Allowing anonymous users to anchor nyms will avoid certain ledger checks for validity that could reduce the system's resilience to denial of service attacks, but we don't consider that to be a significant risk. Other levels of DOS protection needs to be instituted by the network administrators regardless of the ledger checks, such as firewall rules to blacklist hostile connections.  * We considered whether we should allow transactions besides nym creation to be allowed without on-ledger signatures because use cases with peer DIDs that could benefit. We decided against doing this work because we don't have customer demand or clear requirements.  * We also considered whether transactions should be allowed without any signatures at all for some development use cases, as previously considered in INDY-2170. But we similarly decided not to do this work without clear demand.  "
Answer: 16173.0