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: {code:xml}  <apikit-soap:config name="soapkit-config" wsdlUrl="tshirt.wsdl" serviceName="Service"                                    portName="Port" mtomEnabled="true" soapVersion="SOAP11"/>   <apikit-soap:flow-mappings>              <apikit-soap:flow-mapping operation="createPerson" flowRef="newPerson"/>  <apikit-soap:flow-mapping operation="getPerson" flowRef="retrievePerson"/>          </apikit-soap:flow-mappings>  </apikit-soap:config >  {code}  
Answer: 6127.0

User story: "Define output UX    This is related to the icon shown in Studio Mule app:    https://github.com/mulesoft/mule-tooling-soapkit/tree/develop/org.mule.tooling.soapkit.contribution/icons"
Answer: 87532.0

User story: "SOAP Proxy Server is responsible for validation input payload when it is configured to do that."
Answer: 121382.0

User story: "The idea is that WSC and SoapKit reuse SOAP code as much as possible"
Answer: 370043.0

User story: "According to this MULE Issue, https://www.mulesoft.org/jira/browse/MULE-13593, privileged extensions with a custom executor were affected to run as non-blocking.      This Mule Commit fixes this problem, https://github.com/mulesoft/mule/commit/25ec2b5fff15d9e6e63b9920fab06e02087e043f    We have to take a look on this commit and made SOAPKit non-blocking   "
Answer: 31613.0

User story: "When a .wsdl file is selected a ComboBox must be filled with all the available services and when a service is selected another Combo should be populated with the PortTypes exposed by that services.  "
Answer: 3567.0

User story: "We need adapt SoapKit Router and Fault Processors to Mule 4. In this first stage, we will migrate both processors but with a dummy implementation."
Answer: 25983.0

User story: "As a requirement for API Gateway, APIKit for SOAP must have a proxy element, which would be in charge of validating the requests agains the wsdl specification, but not routing to any flow.   The API Gateway will use it as part of their auto generated proxies.   The use case is the following:  Each proxy will have an xml config template, which will consist in only one flow, with a listener, the proxy element, a requester and an error handler. There will not be any resource flow to redirect, as all the request will go to the requester, after being validated."
Answer: 840927.0

User story: "Support SOAP XML signature signing and verifying"
Answer: 471185.0

User story: "We need to remove the *address* and the possibility to *add Interceptors* in Server Configuration"
Answer: 1414.0

User story: "Subflow metadata"
Answer: 10102.0

User story: "Fix output stream handling     //TODO Review Find out why XMLStreamReader is closed o can not be transformed to String"
Answer: 8118.0

User story: "Integrate SOAPkit for M3 and M4 with Amplitude in order to get usage metrics"
Answer: 368350.0

User story: "Make soapkit work without SOAP action"
Answer: 13412.0

User story: "Toady Mule SOAP Service only supports the client implementation. "
Answer: 63225.0

User story: "POC on Soapfault 2.0"
Answer: 52885.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: "Remote WSDL metadata"
Answer: 28478.0

User story: "Add Attachments management in SOAPKIT"
Answer: 34376.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: "create apikit for soap 1.1.6 release note"
Answer: 1.0

User story: "Remove modules and rearrange packages    * Define Soap Server API  * Remove commons module  * Rearrange Soapkit module packages and classes"
Answer: 61519.0

User story: "This Mule extension will be developed using the Mule 4 Privileged API (unlike APIKit). Today Mule 4 API allows access to flows in order to route messages, manage metadata and configuration, all resources are necessaries in SOAPKit extension.     The scope of this Story creates the new extension module with a basic implementation of Router and Fault. Ideally, use the CXF Server Proxy in in order to router flows, in order hands all flows executions is running inside CXF"
Answer: 63423.0

User story: "Fix protocol headers roundtrip"
Answer: 4236.0

User story: "We will Release     Soapkit Tooling Release 1.2.1, this release uses Soapkit 1.1.4 Runtime Extension"
Answer: 32996.0

User story: "We need provide metadata for Studio Datasense"
Answer: 30535.0

User story: "We need to create a Specification for ApiKit for SOAP Migration into Mule 4 to avoid implementations problems since there are many technical differentes between Mule 3 and Mule 4 "
Answer: 3.0

User story: "SOAP Server Validation Enable Support"
Answer: 45699.0

User story: "Java 11 support APIkit for ODATA"
Answer: 100827.0

User story: "h2. Studio-OData events for Amplitude    We're planning to log certain events of the OData Tooling in Studio so we can measure the adoption of the extension and the final user experience.     Following are the events we're planning to log:   # _OData plugin Installation_: when a user clicks on Help->Install New Software and installs the OData extension   # _Scaffolder_: when someone right clicks on the _OData.raml_ file and clicks _Generate Odata API from RAML types__  __    _     * _Errors from scaffolder:_ we want to detect how often the Scaffolder process is failing, and the reasons for that failure    _Re-Scaffolder_: when someone runs the scaffolder again and the api.raml already exists."
Answer: 8616.0

User story: "Investigate how to load OData extension from APIkit"
Answer: 1775.0

User story: "* Resolve vulnerability CVE-2018-8039 on mule 4"
Answer: 20098.0

User story: "Spike: Support Odata for Mule 4         Create a spec     "
Answer: 270.0

User story: "To be able to scaffold a new app, a new menu option was added to Studio 6 by creating a plugin.    Migrate this plugin to be used in Studio 7"
Answer: 72264.0

User story: "Create a spec for OData extension for Mule 4    and share it with:    * Connectors   * La Greca   * <USER>  * Matias Coaker"
Answer: 18465.0

User story: "- Odata run Sonar in Jenkins (contact Paca)--> coverage?  - Odata: fix smells "
Answer: 543158.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: "Requests other than Service Document nor Metadata must be processed by APIkit Router. In those cases, OData Router must translate the request to one readable by APIKit, delegate the processing to APIKit Router and finally translate the response to the requested format"
Answer: 13319.0

User story: "The service root URI identifies the root of an OData service. The service document is required to be returned from the root of an OData service to provide clients with a simple mechanism to enumerate all of the collections of resources available for the data service.    For instance: http://services.odata.org/OData/OData.svc/    Similar to metadata (ODATA-18), expose the service document under the path _*/odata.svc*_"
Answer: 2859.0

User story: "* Resolve vulnerability CVE-2018-8039 on mule 3"
Answer: 20099.0

User story: "The entities are defined in the odata.raml file. In order to scaffold OData based apps, the plugin must parse the odata.raml file and generate the root raml (api.raml) adding the corresponding resources for the entities.    Migrate this functionality to be used in Studio 7 and Mule 4."
Answer: 53647.0

User story: "Implement phase 1 of IBM MQ based on the initial spec"
Answer: 21322.0

User story: MEL expression language is currently provided by the runtime and available to every component without extra configuration.  This implies that users can use MEL expressions everywhere by just adding the "mel:" prefix to their expressions.  As MEL is provided for compatibility reasons, the right approach is to provide MEL support on the compatibility plugin instead of in the runtime. So users can onlyuse MEL on EE and only when they are migrating from 3.x.
Answer: 23060.0

User story: "Domain bundle consist of a domain artifact and the set of applications that belong to that it.  Deployment service must support the deployment of domain bundles, this implies:  * Detecting new bundles  * Redeploy domain/applications when a new domain bundle is found  * Notify the deployment status of domain bundles  * Provide an API to request deployment of domain bundles from the deployment service"
Answer: 32120.0

User story: "Consistent with scatter-gather and using ForkJoinStrategies but operating on split parts instead of routes."
Answer: 299520.0

User story: "Support provisioning/replacement of configuration to the application when deploying.    When an application is getting promoted from one env to another (Dev -> QA or QA -> Prod), the devops need to be able to change connection provider configuration.    The idea is that the devops get a list of all the connection configurations and it's able to redefine the connection parameters during deployment.    This task is to define how the runtime manager (or any client) can get the set of connection providers that may require changing connection parameters and also to be able, during deployment, to provide those new parameters and the runtime must be able to apply them."
Answer: 31655.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: "Scripting plugin was added as privileged in order to provide access to privileged transformer classes as the plugin provide scripting transformer that requires access to it.    Scripting transformer must be removed and usages replaced by scripting component, after that, the scripting plugin can be removed from the privileged API     "
Answer: 4427.0

User story: "Upgrade ahc and grizzly to 1.13 and 2.3.31 respectively"
Answer: 206.0

User story: "All the packages exported on the Mule container must contain the api package.  Currently, there are packages that do not say api. For example org.mule.runtime.module.artifact.  This task is to fix only all the packages that are intended to be exported. Some internal packages are begin exported now, but just temporarily, so those packages will be manage in a different issue."
Answer: 18926.0

User story: "Temporarilly adding spring-module as privileged enable to provide access to privileged classes.    This must be removed and make classes part of the API or avoid to use them from the plugin"
Answer: 5846.0

User story: "There are scenarios, where a plugin A must be extended on another plugin B, and to be able to do it, iB must use some A classes that makes no sense to be available on the A's public API.    To avoid exposing those classes, will be better to have a privileged API that the plugin A can define to enable extension on those scenarios. Similar to what is supported on container's modules."
Answer: 5569.0

User story: "In order to upgrade to the latest Amazon SDK on Cloudhub, minimum Jackson version required is *2.6.6* "
Answer: 73174.0

User story: "Change the default value for output type field in the HTTP Request (advance > other setting > output type field) from Any to Stream"
Answer: 85791.0

User story: "Create the basic structure to setting the configuration necessary for integration tests."
Answer: 10.0

User story: "Reusable streams related with previous steps"
Answer: 68023.0

User story: Consider the following scenario (payload is an InputStream with JSON format):    {code:xml}  <choice>      <when expression="#[payload.aFiled == 'a']>            ...      </when>      <when expression="#[payload.aFiled == 'b']>            ...      </when>  </choice>  {code}    DataWeave would have to parse the input stream twice, which would cause performance issues if the same input stream must be accessed several times.    We need to add a mechanism that DataWeave can use to correlate and InputStream (string, or whatever) with it's parsed representation.     We need to be careful with the mechanism to use to avoid memory leaks.
Answer: 383136.0

User story: "Migrate Tests from JMS transport to JMS Extension"
Answer: 457857.0

User story: "Generic typing (List<T>)"
Answer: 148418.0

User story: "Function typing"
Answer: 148419.0

User story: "Since a dw script can be quite large, it would be ideal to load them from a file."
Answer: 443708.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: "- Redefine DW current components    - set-payload vs dw:transform    - Make DW components as part of core namespace."
Answer: 102369.0

User story: "Review new won't be supported in EL. Need to evaluate the impact and define how to approach the fact that 'new' won't be accepted in the EL."
Answer: 1037127.0

User story: "Define bindings to use in Mule 4"
Answer: 61911.0

User story: "Define API to do type inference for bindings (functions and variables) "
Answer: 329779.0

User story: "Define how to define EL functions from modules"
Answer: 164378.0

User story: "Define how to do beans lookup. One way this was done was using the app global which exposed the registry."
Answer: 311286.0

User story: "Define the UX for enricher that uses MEL. We need to review how now having the enricher affects us considering the 3.x use cases."
Answer: 1140656.0

User story: "Define a way to hook to the default EL in Mule"
Answer: 59435.0

User story: "Add support on the SDK for receiving MEL expressions without getting the string evaluated.    This features was supported in DevKit as described here:   https://www.mulesoft.org/jira/browse/DEVKIT-245    This will be supported both for @Parameters and Operation arguments, when they are annotated with _@Literal_  When @Literal is used, ExpressionSupport should be _SUPPORTED_."
Answer: 53399.0

User story: "This is related to consolidation of dataType in mule/ext-api/mule-commons."
Answer: 299782.0

User story: "Create new Transformation Service.    This issue should be updated and split into different stories once these improvements have been analyzed."
Answer: 1771374.0

User story: "Work on proposal different aspects of potential MuleEvent/MuleMessage improvements for Mule 4. e.g. originalPayload, Message/Event relationship, exceptionPayload etc."
Answer: 67402.0

User story: "Support bootstrap properties"
Answer: 10278.0

User story: "Spike: Karaf vs. Felix"
Answer: 15856.0

User story: "This includes:  - Performance Due Diligence  - Creating a new MuleMessageBuilder etc.  - Updating uses."
Answer: 73077.0

User story: "Cleanup MuleSession, moving anything that can be moved to compatibility module and ensure it's not exposed as part of mule-api."
Answer: 382789.0

User story: "As a user, I want to be able to see the details for my exchange.    * Should list destination queues  * Should allow me to go to manage the Exchange"
Answer: 1951142.0

User story: "Add tests"
Answer: 17326.0

User story: "Apikit needs to be forked for different releases.  Also is now a key part of api-led connectivity. HTTP modulo includes RAML functionality already.  If not in HTTP module then as APIKit, but either way consider incorporating into mule."
Answer: 2041678.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: There are use cases, including http proxying where it is necessary to copy http headers from inbound to outbound during the request and from inbound to outbound during the response.  Currently to achieve this, while ensuring the correct behaviour of requestor/listener the following is required:    {code:xml}  <response>      <copy-properties propertyName="*"/>      <remove-property propertyName="Content-Length"/>      <remove-property propertyName="Transfer-Encoding"/>      <remove-property propertyName="Keep-Alive"/>      <remove-property propertyName="Connection"/>      <remove-property propertyName="MULE_*"/>      <remove-property propertyName="X_MULE*"/>      <remove-property propertyName="x-mule*"/>      <remove-property propertyName="http.*"/>  <response/>  <copy-properties propertyName="*"/>  <remove-property propertyName="Content-Length"/>  <remove-property propertyName="Transfer-Encoding"/>  <remove-property propertyName="Keep-Alive"/>  <remove-property propertyName="Connection"/>  <remove-property propertyName="MULE_*"/>  <remove-property propertyName="X_MULE*"/>  <remove-property propertyName="x-mule*"/>  <remove-property propertyName="http.*"/>  {code}    There are really two things being done here, other than the copying of properties:  * Firstly it is necessary to remove Content-Length, Keep-Alive, Connection and Transfer-Encoding.  * Secondly, in this type of use case you don't generally don't want Mule's internal properties to be sent out from the Flow, just because you need to copy the incoming http headers.    The current solution is very verbose, and has a significant performance impact:    *Proposal 1*  Implement a single InterceptingMessageProcessor to do all of this in one component.  {code:xml}  <http:proxy-headers/>  <http:requester/>  {code}    *Proposal 2*  Use just   {code:xml}  <copy-properties propertyName="*">  <remove-properties propertyName="MULE_*"/>  <http:requester/>  <copy-properties propertyName="*"/>  <remove-properties propertyName="MULE_*"/>  {code}  The http listener/requestor should be ignoring/remove the other properties.  This means:    - HTTP Requestor should not send http.* properties in outbound headers.  - HTTP Listener should not respond with http.* properties in outbound headers.  - HTTP Listener/Requestor should correctly handle connect, keep-alive, content-length and transfer-encoding properties such that the correct behaviour of listener/requestor as configured is not compromised.    *Proposal 3*  Same as proposal 4 but add functionality to <copy-properties>    {code:xml}  <copy-properties propertyName="*" excludeMuleProperties="true">  <http:requester/>  <copy-properties propertyName="*" excludeMuleProperties="true"/>  {code}    *Proposal 4*  Do nothing in Mule.  Use the existing approach, or a custom MP implementation that does the same to improve performance.  
Answer: 2041697.0

User story: "As a user, if I've changed my default expression language, enricher should still work."
Answer: 105.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: "As a user, I want to be able to configure the default expression language for my project so that I can use Weave as my expression language."
Answer: 109.0

User story: "Review java heap size and other options in wrapper.conf before 3.7 release"
Answer: 2189113.0

User story: "Go through this doc https://docs.google.com/a/mulesoft.com/document/d/14V8JTyIK6RgD20-FwzVid0lEuWhGCG1ICiFRsUp3S6Y/edit# and fix everything that is missing."
Answer: 123.0

User story: "Item1"
Answer: 359.0

User story: "Fix SE-1019 for new connectors."
Answer: 852381.0

User story: "AS A  user    I WANT  I want to have documentation around the features of this transport    SO THAT  I can learn how to use it and to have a reference  "
Answer: 146757.0

User story: "AS A user  I WANT I want the transport to be tested against a real broker and a real application.  SO THAT I can be sure the transport works on real world usage. "
Answer: 181311.0

User story: "AS A  user    I WANT  I want to be able consume instantly amqp messages    SO THAT  I can consume messages at any point of the flow  "
Answer: 181315.0

User story: "AS A  user    I WANT  I want to be able consume continuously amqp messages    SO THAT  a MuleEvent is created and delivered to a flow when a messages arrives to a queue and is comsumed  "
Answer: 181366.0

User story: "AS A  user    I WANT  I want to be able to configure the transport in a single point    SO THAT  I can configure the common transport attributes in a single reusable place  "
Answer: 181319.0

User story: "AS A  developer    I WANT  I want to have a base project skeleton    SO THAT  there is a basement to build on with agreed placeholders for endpoints, connectors, transactions that should be stable.  "
Answer: 181322.0

User story: "AS A  user    I WANT  I want to be able to rely on a defined schema to write my AMQP integrations     SO THAT  I have exact knowledge of how I’m syntactically supposed to use the transport and to have help from my IDE to autocomplete and detect errors.  "
Answer: 181324.0

User story: "AS A  product owner or community member    I WANT  to be able to review the specs     SO THAT  I can and contribute with my feedback  "
Answer: 10402.0

User story: "When developing an integration in a SOA environment a common scenario is to consume several web services and aggregate its behaviour, possibly adding logging in a database, notifications or any other operations. If any web service operation fails the developer needs to rollback the previous successful web service, database or queue operations. Currently there are some web service transactions specifications. We should research if Mule ESB customers would use this feature, or if it is used in SOA development at all. And analyse cost and benefits for it.    An alternative approach would be to support compensations, but we don't support that either."
Answer: 15924.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: "As a Mule user I would like to:    * Deploy a new application and being able to override the app properties while deploying with the DeploymentService"
Answer: 2527095.0

User story: "As a Mule user I would like to:    * Deploy a domain with mule API  * Undeploy a domain and all its apps  * Redeploy a domain and update all the apps  "
Answer: 113855.0

User story: "There's a functional dependency between the TransientRegistry and the SpringRegistry, due to the fact that:    * The Spring registry contains the SimpleRegistryBootstrap  * The Spring registry contains the MuleContext  * Because the Spring registry starts flows, connectors, batch jobs and other components that depend on objects started through the registry bootstrap, we can't start the spring registry before the TransientRegistry.     These issues prevents us from:    * Have a solid IoC mechanism  * Have a consistent lifecycle across registries    "
Answer: 446042.0

User story: "Before reverting back to DynamicOptimizer we need to:  - Fix MVEL ASMOptimizer bugs  - Expand MEL tests to cover ASM/Reflective/Dynamic optimizers."
Answer: 18075.0

User story: "As a user, I want to have the option to see all queries run in my connected relational database in my Mule logs in DEBUG mode."
Answer: 80173.0

User story: "As a user, I want to connect to popular relational databases using JDBC with little extra configuration.    In order of priority, the databases are:  1. Oracle  2. PostgreSQL  3. Sybase  4. MS SQL Server  5. DB2  6. MySQL (done)    [~<USER> FYI  "
Answer: 1309211.0

User story: "Create micro-benchmarks to test MEL expression evaluation."
Answer: 1284097.0

User story: "As a user of Mule 3.5.0, I would like Mule to depend on the latest version of MVEL (used for DataMapper and MVEL) to stay up-to-date with the latest MVEL bug fixes/enhancements.    The latest version seems to be 2.1.8"
Answer: 32409.0

User story: "In order to run user testing we need to integrate the current component to Mule.  "
Answer: 41733.0

User story: "I want to be able to share connection to external systems between mule applications    I want to be able to communicate mule applications deployed in the same container through VM queues.    I want to be able to define a common security manager for all the applications deployed in the mule container"
Answer: 159534.0

User story: "When I define a message filter (expression filter, payload filter, etc) is because I want not to continue the execution for the current message if some criteria is reached, but I do want to know I've filtered a certain message, or perhaps prepare some answer or response code for the person that has called my flow"
Answer: 36292.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 several enhancements around until successful    1 - It is using the mule common work manager. So the behaviour of it is affected by other threads in mule that are not related to until successful. It also makes hard to customise the threading profile for the until successful. Each until successful should have it own threading profile.  2 - It doesn't provide any reliability when it can. Current implementation, when using a persistent object store, prevents losing messages if a server crash. It can be the case were duplicates are generated but that can be overcome with filters. But, if I need to set up a limit to the maxEntries of the object store, it would evict messages without letting me do anything about it. So I would be losing messages. We need to enhance until-successful with a maximum number of messages to hold. If that number is exceeded then it should thrown an exception and the exception strategy must kick of.   3 - We need to change how the waiting between retries is implemented. Currently is doing Thread.sleep(..) and I don't have to explain why that is a poor implementation."
Answer: 332368.0

User story: "Basic requirements:     http://corp.wiki.mulesource.com/pages/viewpage.action?pageId=27132117  "
Answer: 21089.0

User story: "Right now, when a poll needs to deal with updated objects, we use watermarks as an approach to filter out elements that were already processed. The only way to do that right now is to implement the logic manually which forces the user to deal with object stores, default values, repeated logic, dev time dependencies, etc.    This story is a container of all the features required for watermark  "
Answer: 192019.0

User story: "See here: http://corp.wiki.mulesource.com/pages/viewpage.action?pageId=27132117    This will require some in-iteration investigation."
Answer: 180467.0

User story: "* Move generated DevKit code to ESB and expose an interface that DevKit can use  * Improve user experience when trying to configure an OAuth connector    http://corp.wiki.mulesource.com/display/WP/Making+OAuth+user+experience+smoother"
Answer: 51162.0

User story: "Deprecate Services (and anything else we can)"
Answer: 19984.0

User story: "Create an example application to showcase apikit functionality"
Answer: 24522.0

User story: "Multiple representation support for apikit"
Answer: 24525.0

User story: "As a Mule ESB developer, I want my custom business events and transaction IDs to be printed to my logs when I'm developing an application so that I can ensure my events are set up correctly."
Answer: 1777748.0

User story: "Update the version of Spring we are using to 3.2"
Answer: 38933.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: "* Packaged examples should be modified as per the following plan: https://docs.google.com/a/mulesoft.com/spreadsheet/ccc?key=0ArwrJmCfHowWdDNCdnJYeldHcDI5M0dYaTRsWUwxd2c#gid=2    * This requires the following additional work:      - Creation of the two new identified examples.      - Modification of target examples to use latest 3.4 features. Beyond specifics identified on spreadsheet this includes adding in-studio documentation for all examples.     - Modification of documentation for target examples.     - Removal of examples tagged as Archive from Studio.     - Modification of docs to reflect an Archived examples section.      - Placement of all examples in GIT and tagging as active versus archived.     - From the ESB stand-alone distribution point of view: Remove all examples except the new hello world and existing loan broker."
Answer: 241434.0

User story: "As a Registry user, I would like to be able to apply throttling policies to my Mule ESB flow end-points. "
Answer: 41083.0

User story: "As a Mule user, I would like to use the dynamic lookup component within my flows.  Detailed specs defined here:   http://corp.wiki.mulesource.com/display/WP/Dynamic+Router+%28supports+Registry+Dynamic+Endpoint+Resolution%29"
Answer: 23796.0

User story: "As a Mule user, I would like to configure my Mule instance to be paired with my Registry account through my registry key so that I may be able to manage my ESB instance's endpoints with the registry.   User should be configure the registry key for their registry account for an ESB instance. From there on: The HTTP endpoints of all apps deployed to the ESB instance should be manageable with the paired registry instance.  Detailed specs described here:   http://corp.wiki.mulesource.com/display/PRODMGMT/Registry+Interaction+and+License+Management+Support "
Answer: 43910.0

User story: "As a Mule ESB user, I would like to be able to turn on the use of the NIO stack through a deploy.properties toggle.   As a Mule ESB user, I would like to be able to use the new WebSocket components within my flows. "
Answer: 1011551.0

User story: "The list of enhancements requests that should be fixed are the ones with blocker and critical priority as listed here:    http://www.mulesoft.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+review-by-PM-pending"
Answer: 2087701.0

User story: "Today we show MySQL, Derby, and Oracle. However, MS SQL and DB2 are RDBMS's with very large footprints. As such, we should add these two databases to the set that shows up on the JDBC connector's configuration screen. "
Answer: 40366.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: "* Packaged examples should be modified as per the following plan: https://docs.google.com/a/mulesoft.com/spreadsheet/ccc?key=0ArwrJmCfHowWdDNCdnJYeldHcDI5M0dYaTRsWUwxd2c#gid=2    * This requires the following additional work:      - Creation of the two new identified examples.      - Modification of target examples to use latest 3.4 features. Beyond specifics identified on spreadsheet this includes adding in-studio documentation for all examples.     - Modification of documentation for target examples.     - Removal of examples tagged as Archive from Studio.     - Modification of docs to reflect an Archived examples section.      - Placement of all examples in GIT and tagging as active versus archived.     - From the ESB stand-alone distribution point of view: Remove all examples except the new hello world and existing loan broker."
Answer: 194487.0

User story: "http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation"
Answer: 37324.0

User story: "http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation"
Answer: 37324.0

User story: "http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation"
Answer: 37324.0

User story: "http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation"
Answer: 37324.0

User story: "This version works with 1.8.0 and there are some deprecated methods in 1.9.11, so there is a need for an upgrade."
Answer: 71948.0

User story: "This is currently breaking builds of the Windows Installer. The old timestamp URL/server has been de-commissioned and the new URL I tried doesn't seem to be working either."
Answer: 1255.0

User story: "This is currently breaking builds of the Mac Installer, as the private key/cert pair are now expired."
Answer: 278.0

User story: "h5.Description    API Builder v3 is being retired, and will be removed from Appc CLI 8. We should also remove these CLI-1385"
Answer: 43208.0

User story: "As of SDK 9 we expect to bump the minimum Node.JS supported to 10.x. We'll need to update our installers to provide Node 10/12 and to enforce Node 10+"
Answer: 149505.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: "Following test cases need to be addressed with ES6 changes    com.aptana.js.internal.core.build.JSStyleValidatorTest.testTabsDontMessUpOffset  com.aptana.js.internal.core.build.JSStyleValidatorTest.testBadAssignmentA1  com.aptana.js.internal.core.build.JSStyleValidatorTest.testBadAssignmentA5  com.aptana.js.internal.core.build.JSStyleValidatorTest.testStatementBlock1  com.aptana.js.internal.core.build.JSStyleValidatorTest.testStatementBlock2  com.aptana.js.internal.core.build.JSStyleValidatorTest.testWeirdProgram1  com.aptana.js.internal.core.build.JSStyleValidatorTest.testWeirdProgram2  com.aptana.js.internal.core.build.JSStyleValidatorTest.testWeirdProgram3  com.aptana.js.internal.core.build.JSStyleValidatorTest.testUseArray3  com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock1  com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock2  com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock3  com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock4  com.aptana.js.internal.core.build.JSStyleValidatorTest.testEmptyBlock5  com.aptana.js.internal.core.build.JSStyleValidatorTest.testMoveInvocation2  com.aptana.js.internal.core.build.JSStyleValidatorTest.testUnreachableAB1  com.aptana.js.internal.core.build.JSStyleValidatorTest.testUnreachableAB2  com.aptana.js.internal.core.build.JSStyleValidatorTest.testUnreachableAB3  com.aptana.js.internal.core.build.JSStyleValidatorTest.testStatementBlockOK2  com.aptana.js.internal.core.build.JSStyleValidatorTest.testMissingA1  c"
Answer: 2.0

User story: The "full_uninstall.txt" file in the Appcelerator folder is outdated      {code:java}  Uninstalling/Re-installing Axway Appcelerator Studio  ======================================================================================    If you need to fully uninstall and reinstall Axway Appcelerator Studio,   you can follow the "Uninstalling Studio" steps here:   http://go.appcelerator.com/apupdate and then re-download and   install again as before.  {code}  
Answer: 59153.0

User story: Studio suddenly stop working, every time open it, will stuck at workspace launcher. (Like attached screenshot). Cannot edit or click anything on the dialog. Try the following steps, but did not help    1. Force to quit studio.  2. Restart the system.  3. Remove the studio package from Application, and re-install it from latest installer.   4. Remove the old workspace.    All the changes is I recently updated JDK to version 1.8.0_161. But I tried to revert it back. Still seeing same issue.     Run "appc info" and "appc setup check". All works well. (attached)    Please advice.
Answer: 210.0

User story: "Get Appcelerator Studio 4.9.0 error reporting issues from the Vasil and identify what all can be fixed and create tickets accordingly. "
Answer: 46108.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: "h5.Description    LiveView needs to be updated in Studio to fix the following issues    TIMOB-24693 - LiveView: Incorrect argument checked for custom IP (relates to CLI-1075/TISTUD-7138)  TIMOB-24699 - LiveView: Alloy app errors out when built for Windows"
Answer: 143.0

User story: With V8 5.7.54 and higher, they've disabled the "legacy" debugger protocol (that we just updated to!) and are now using the inspector protocol. Luckily, this seems to be the same underlying protocol iOS/JSCore uses that I had to move to late last year.
Answer: 286448.0

User story: "Studio does not support Android Build-Tools 24.0 as it requires JDK 1.8    Currently Studio works with JDK 1.7.    Also with release 6.0.4 of titanium SDK, an android project can now be build from cli using Build-Tools 24.0 and above.    Hence Studio needs to support using JDK 1.8 and build Android project with newer Android Build-Tools  "
Answer: 38544.0

User story: "Hello,     Unable to install the Appcelerator Studio completely, due to registry editing disabled in Organization laptop. After installing the studio When try to open the Studio got *Screen-01.png* error. Tried to set proxyServer null but got *Screen-02.png* .     *Working Environment:*  Windows 7, R1, 64 bit OS.    Thanks    "
Answer: 1409493.0

User story: "Go through 4.8.0 and 4.8.1 Studio crash reports and create tickets for them to address"
Answer: 166390.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 handle this error gracefully.  {code:java}  com.appcelerator.titanium.android.core 4 0 2016-07-29 12:55:52.772  !MESSAGE (Build 4.8.0.qualifier) [ERROR]  Titanium SDK 6.0.0.v20160717220907 is incompatible with Node.js v0.12.7  You will need to install Node.js v5 in order to use this version of the Titanium SDK.     !STACK 0  Unexpected character (T) at position 0.   at org.json.simple.parser.Yylex.yylex(Yylex.java:611)   at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:270)   at org.json.simple.parser.JSONParser.parse(JSONParser.java:119)   at org.json.simple.parser.JSONParser.parse(JSONParser.java:82)   at org.json.simple.parser.JSONParser.parse(JSONParser.java:76)   at com.appcelerator.titanium.android.core.AndroidSDKLocator.loadTiInfo(AndroidSDKLocator.java:841)   at com.appcelerator.titanium.android.core.AndroidSDKLocator.updateTiInfo(AndroidSDKLocator.java:224)   at com.appcelerator.titanium.android.core.AndroidSDKLocator.access$0(AndroidSDKLocator.java:222)   at com.appcelerator.titanium.android.core.AndroidSDKLocator$1.run(AndroidSDKLocator.java:242)   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)  Unexpected character (T) at position 0.   at org.json.simple.parser.Yylex.yylex(Yylex.java:611)   at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:270)   at org.json.simple.parser.JSONParser.parse(JSONParser.java:119)   at org.json.simple.parser.JSONParser.parse(JSONParser.java:82)   at org.json.simple.parser.JSONParser.parse(JSONParser.java:76)   at com.appcelerator.titanium.android.core.AndroidSDKLocator.loadTiInfo(AndroidSDKLocator.java:841)   at com.appcelerator.titanium.android.core.AndroidSDKLocator.updateTiInfo(AndroidSDKLocator.java:224)   at com.appcelerator.titanium.android.core.AndroidSDKLocator.access$0(AndroidSDKLocator.java:222)   at com.appcelerator.titanium.android.core.AndroidSDKLocator$1.run(AndroidSDKLocator.java:242)   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)  {code}  "
Answer: 1731730.0

User story: As MobileWeb Platform is deprecated with 4.7.0, show a warning message in  # New mobile app project creation wizard, show that "MobileWeb is deprecated".  # Tiapp.xml file deployment targets    This also applicable for creating  MobileWeb modules.  
Answer: 5126.0

User story: "1. Open an alloy view with App designer 'Scratchpad editor'  2. Go to XML section(2nd tab) of the editor  3. Hit 'Ctrl+Space' to see intellisense proposals based on the context  4. Scratchpad XML editor is not showing any intellisense proposals    I believe Scratchpad XML editor should exactly work like standard Alloy View XML editor so that users needn't switch between Alloy view editor and Scratchpad editor    To do this, studio has to expose Alloy view editor functionality and packages to the VisualUI plugin  "
Answer: 46.0

User story: "Create App designer build job in <USER>so that it can be used for building the required jars"
Answer: 4.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 TIMOB-20489 the {{build.py}} scripts in newly generated modules will now give a deprecation warning. Studio [seems to still use build.py|https://github.com/appcelerator/titanium_studio/blob/938ba3b47c1ab33add316308e6593ee99cd329b6/plugins/com.appcelerator.titanium.ui/src/com/appcelerator/titanium/ui/module/BaseModulePackagerLaunchConfigurationDelegate.java#L110] so it needs to switch to {{appc run -p \[platform\] --build-only}}.    See [~<USER> his remarks at:  https://jira.appcelerator.org/browse/TIDOC-2470?focusedCommentId=378605&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-378605    We need to:    # Test if {{appc run -p \[platform\] --build-only}} is fully backwards compatible with {{build.py}}  # Switch Studio to use {{appc run -p \[platform\] --build-only}}  # Add an option to Studio to use {{appc run -p \[platform\]}}, which should run the module example after building the module"
Answer: 43.0

User story: "Watch App XCode Path should be Xcode Path (lowercase C and equal to Tiapp Editor).      "
Answer: 3.0

User story: "Authorised users should be able to create a JIRA ticket from a error report.  "
Answer: 146448.0

User story: "Server should provide a page to view,edit and delete the error reports"
Answer: 146453.0

User story: "Eclipse does this, we should implement this capability in the analytics server.    When studio sends a error report request to the server, server has to analyse the log and identify a pattern to search with in the existing error logs from the server.If finds a similar report, it should identify this as a duplicate and send the existing ticket number/request number to the requested user for a reference.  "
Answer: 146457.0

User story: "Eclipse AERS can only send stack trace and but we should implement a mechanism to send studio log and diagnostic log to the server"
Answer: 50114.0

User story: "TRACE  | titanium exited with exit code 1  ERROR  | Error: ti run exited with error code 1      at ChildProcess.<anonymous> (C:\Users\Don_kiki\.appcelerator\install\5.0.4\package\node_modules\appc-cli-titanium\plugins\run.js:92:23)      at emitTwo (events.js:87:13)      at ChildProcess.emit (events.js:172:7)      at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)  TRACE  | Sending exit signal to titanium process:  6496  [ERROR] Application Installer abnormal process termination. Process exit value was 1"
Answer: 361783.0

User story: "Currently In the studio codebase we are maintaining titaniumUser and Titanium30User, so as part of this ticket will consolidate the functionality of both.    "
Answer: 31965.0

User story: "Placing this in the TISTUD project since it seems this is the place that might require a change or two.    We want to reduce confusion between the two projects. Thus, we will be doing the following:    # Move all open unresolved tickets from AC to TC  # Close TC project  # Redirect any references from TC to AC"
Answer: 30254.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, we're looking to add a flag in adhoc build distribution flows for uploading to Installr App.    Users should be able to flag their build to be uploaded to Installr.  When selected they should be able to add a description to their build.  Additional options available in the CLI plugin such as emailing existing users in the app or adding emails should also be in the form.    CLI plugin located here:  https://github.com/<USER>appc-app-preview-cli-hook"
Answer: 457399.0

User story: "Appc Studio doesn't show an update for Appc Core package @ 4.0.0, if 4.0.0-rc is already installed on the machine."
Answer: 2.0

User story: If we choose to create an arrow with custom location, the project is created with an empty directory.    Steps:  1. New->Arrow project  2.  Project name: "arrowtest" and un-check "Use default location" and provide path to custom location   Example: /Users/<USER>work/eclipse_workspaces/runtime-Titanium-360/arrowtest_diff  Here project name and last segment of the path(project directory name) are different.  3. Click finish  Project will be created with a name "arrowtest" without any content in it.  
Answer: 11482.0

User story: "https://jira.appcelerator.org/browse/CLI-551    Handling the above issue in studio, showing the confirmation dialog to the user to replacing the acs keys based on the user input."
Answer: 3697.0

User story: "Since Titanium docs will not longer be updated, Studio needs to grab the release notes from the Platform docs.    http://docs.appcelerator.com/platform/latest/#!/guide/Studio_Release_Notes    Any links directing to http://docs.appcelerator.com/titanium should now point to http://docs.appcelerator.com/platform"
Answer: 9057.0

User story: "Reproduction: Download and launch the latest Beta installer from the preview site (Beta - 4.0.0.201502181719).    Actual Results: The Installer dialog displays the silent_installer folder and PKG file.  See attached screen shot.    Expected Results: Should only display the PKG file."
Answer: 51785.0

User story: "As access to CHANGELOG.md  will be restricted for the appc-cli project we need a different mechanism(other than github) to read release notes .. probably from a different uri "
Answer: 62818.0

User story: "Dashboard will be changing the Organization document 'org_id' to a String instead of an Integer. This affects APIs such as GET /org, which returns a list of organizations.    This ticket is intended to evaluate any changes needed by Studio to accept an 'org_id' value as a string. To prevent any dependencies, the logic should accept both a string or an integer"
Answer: 21787.0

User story: "Install JDK and Node through one sudo prompt by calling into the AuthorizationExecuteWithPrivileges system level API. Also customize the sudo prompt message and the icon. "
Answer: 2913.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: "Running the Mac native installer in silent mode does not install the pre-requisites such as JDK along with the Appcelerator Studio payload.    A pre-install script has to be added to the installer script to take care of detecting and installing JDK, as part of configuring prerequisites."
Answer: 20218.0

User story: "Running the Mac native installer in silent mode does not install the pre-requisites such as Node along with the Appcelerator Studio payload.    A pre-install script has to be added to the installer script to take care of detecting and installing NodeJS, as part of configuring prerequisites."
Answer: 17413.0

User story: The Windows installer already handles the silent installation of Appcelerator Studio using the below command    {code}  "C:\Users\User\Downloads\Appcelerator_Studio.exe" /qn  {code}    However, it does not install the pre-requisites such as JDK during the silent installation of Studio. We need to handle a special case for installing JDK as part of silent installation.
Answer: 20072.0

User story: The Windows installer already handles the silent installation of Appcelerator Studio using the below command    {code}  "C:\Users\User\Downloads\Appcelerator_Studio.exe" /qn  {code}    However, it does not install the pre-requisites such as Node during the silent installation of Studio. We need to handle a special case for installing Node as part of silent installation.
Answer: 30316.0

User story: "The Mac native installer currently opens up UI to let user go through different stages such as configuring destination/disk, handling pre-requisites, license agreements and finally showing the progress for installing Studio payload.    Add the ability to let to install Studio on mac through command line silently. Customers should have a command with a few options/flags to let Studio and its prerequisites installed silently."
Answer: 29136.0

User story: "The mac native installer (packager) will be build through Jenkins job. Once it is built, we need to sign the installer, similar to the way we are currently signing the Studio application."
Answer: 55138.0

User story: "The packager (mac native installer) has to be included with the resources/images required to display the installer UI.    The <USER>job has to make sure that the required resources are added to the packager before the installer is build."
Answer: 4380.0

User story: "- We already know the location of the Studio payload, but we need to pass in the payload location to the packager build command to include before it is build.  - Find out the command required for building the packer (mac native installer)  - Integrate the command into Jenkins, to build the mac native installer.  "
Answer: 4357.0