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: "h2. Card  DNN currently requires .Net 4.0 and above in order to operate. In 2012, Microsoft released .Net 4.5 which included many new features including support for asynchronous task based development.  New frameworks like Web API 2 and MVC 5 require .Net 4.5 support. Subsequent to .Net 4.5, Microsoft has released two minor in-place updates incorporating performance improvements and bug fixes.    DNN libraries and modules should be updated to compile using .Net 4.5 and should run without issue on .Net 4.5.1 and .Net 4.5.2.    h2. Conversation    h2. Confirmation  "
Answer: 3200.0

User story: "Similar to the DNNExceptionAttribute provided in the Services Framework for the WebAPI methods, we should provide a DnnHandleErrorAttribute, which can handle DNN errors by automatically logging the exception."
Answer: 238969.0

User story: "Similar to the DnnAuthorize and DnnModuleAuthorize attributes in Web API, we should provide authorization attributes that can apply DNN permissions to individual action methods (or to a MVC Controller)"
Answer: 238971.0

User story: "h2. Card As part of our move to more web service based development, we would like to open up the ability to call platform services from external systems in a secure manner.  The simplest approach is to use an HMAC based signature which can be used for both HTTP and HTTPS connections.  A custom authorization attribute should be created which implements the HMAC protocol for authorization.  h2. Conversation We will not consider using the same API for both internal and external access.  h2. Confirmation "
Answer: 71.0

User story: "h2. Card DNN currently uses a customized ASP.Net membership implementation to handle managing users and authentication.  This forms the foundation of our security infrastructure.  ASP.Net membership is a roles based security system and requires extra effort to enable the integration of claims based systems like OAuth  In DNN next we will be using the ASP.Net Identity framework as the foundation of our application security. ASP.Net Identity is a more modern framework and provides improved extensibility and native support for both claims based and role based authorization.  As part of our desire to implement OAuth and HMAC security for web services in DNN 7.5, we would like to determine the level of effort required to implement ASP.Net identity in the current system.  As part of the spike, we would like to determine how invasive the change would be, and how it might impact an OAuth server implementation.  h2. Conversation What is the expected output? Report documenting the findings.  The recommended approach (using identity server etc.) h2. Confirmation "
Answer: 61.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: "h2. Card  SPA Modules should behave the same as any other DNN module when it comes to packaging.  A SPA module should be installable using a standard DNN module manifest. Since SPA modules use an HTML file as the primary method for rendering content, the manifest should allow the module to define an HTML file to render for specific module controls.    The DNN framework should use the defined html file to render the requested module control following the standard DNN convention.  While an HTML module may define a number of module controls, it should also be able to programatically define a html file to use without using a predefined control.    When installed, SPA modules should be installed in the DesktopModules folder using the same conventions as more traditional modules.    h2. Conversation    h2. Confirmation"
Answer: 20169.0

User story: "h2. Card  The HTML module type will allow the user to define JavaScript and CSS to include when rendering the HTML view.  The rendering engine should support some standard conventions which eliminate the need for configuration for common use cases.    An html view should automatically inject any css or js file which uses the same name as the html view file.  For example an html file named myview.html would automatically inject a reference for myview.js and myview.css if defined.  This is in addition to standard DNN conventions of including module.css, portal.css and default.css on every page.    h2. Conversation    h2. Confirmation  "
Answer: 20172.0

User story: "h2. Card  HTML does not have a mechanism for easily executing server side logic.  As part of the SPA module support HTML modules will include support for using DNN tokens. The use of tokens provides the ability to link standard HTML to server side logic.    HTML views need to be able to define the CSS which is needed to properly render the HTML.  One New standard tokens should be created which defines the CSS vneeded for a view.    These tokens will use a new token pattern: [Token: {propertybag}]    Token Type 1:  [CSS: { url: http://mysite.com/blah.css }]  [CSS: { path: /blah.css, priority: 1 }]  [CSS: { path: /blah.css, priority: 1, provider: head }]    These tokens will call the standard DnnCSSInclude methods with the defined parameters.  The propertybag is a standard JSON object and includes parameter names and values which are used to call the appropriate include methods. The order of properties in the propertybag is unimportant and should not impact the ability to bind to the appropriate CSSInclude methods.    h2. Conversation  The CSS token should be implemented as a standard DNN token which is usable by any module using the TokenReplace engine.    h2. Confirmation  "
Answer: 20179.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: h2. Card  HTML does not have a mechanism for easily executing server side logic.  As part of the SPA module support HTML modules will include support for using DNN tokens. The use of tokens provides the ability to link standard HTML to server side logic.    HTML views need to be able to define the JavaScript  which is needed to properly render the HTML.  Two New standard tokens should be created which defines the JavaScript needed for a view.    These tokens will use a new token pattern: [Token: {propertybag}]    Token Type 1:  [JavaScript : { url: http://jquery.com/blah }]  [JavaScript : { url: http://jquery.com/blah, priority: 1 }]  [JavaScript : { path: /jquery.js, priority: 1, provider: head }]    These tokens will call the standard DnnJSInclude methods with the defined parameters.  The propertybag is a standard JSON object and includes parameter names and values which are used to call the appropriate include methods. The order of properties in the propertybag is unimportant and should not impact the ability to bind to the appropriate JSInclude methods.    Token Type 2:  [JavaScript : { jsname: "jquery" }]  [JavaScript : { jsname: "jquery", version: "1.10.0" }]  [JavaScript : { jsname: "jquery", version: "1.10.0", specific: "LatestMajor" }]    This token variation will load predefined JavaScript packages which have been installed as JavaScript extensions. This token should just be a call to the RequestRegistration call on the JavaScript class with the appropriate parameters.    h2. Conversation  The JavaScript token should be implemented as a standard DNN token which is usable by any module using the TokenReplace engine.  This token should be disabled by default and a module must affirmatively indicate that this replacement should be enabled.    h2. Confirmation  
Answer: 20206.0

User story: h2. Card    As part of the MVC support the solution should support the use of Master Razor Layouts.    h2. Conversation    If a developer wants to use a "Shared" layout for their Module Views they should be able to use the following syntax    @{       Layout = "~DesktopModules/MyModule/Views/Shared/Layout.cshtml"  }    There are other ways a Master Layout is defined - and these should optionaly be supported.    * in _ViewStart.cshtml  * when the View object is created in the Controller e.g. "return View("Index", "_Layout", item)    h2. Confirmation
Answer: 181.0

User story: "h2. Card  As part of MVC support the solution should support the use of standard Action Filters.  This is a spike to determine the level of effort needed to implement this feature.  h2. Conversation  DNN must support the following Action Filters * Authorization - used for security filtering * Action - used to provide custom code before and after the execution of the action * Result - used to provide additional filtering of the ActionResult * Exception - used to provide exception handling within an Action  h2. Confirmation"
Answer: 207.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: "h2. Card  The DNN core platform uses modules as the primary mechanism for adding new functionality that includes both business logic and user interface elements.  The current implementation is based on ASP.Net web forms and allows module developers to use web controls or server controls for rendering the UI.    DNN should include the ability to define an html file as the view control and render that view as part of module rendering. HTML rendering should support the use of standard DNN tokens which effectively provides context information to the html.    h2. Conversation    h2. Confirmation  "
Answer: 20275.0

User story: "h2. Card  MVC Modules should behave the same as any other DNN module when it comes to packaging.  An MVC module should be installable using a standard DNN module manifest. Since MVC modules use a controller action as the primary method for rendering content, the manifest should allow the module to define a controller and action to render for specific module controls.    The DNN framework should use the defined controller action to render the requested module control following the standard DNN convention.  While an MVC module may define a number of module controls, it should also be able to programatically define a controller action to use without using a predefined control.    When installed, MVC modules should be installed in the DesktopModules folder using the same conventions as more traditional modules.    h2. Conversation  Need to define the module control naming convention \{controller\}/\{action\}.mvc    h2. Confirmation  Modules should be created in the DesktopModule/MVC subfolder."
Answer: 307.0

User story: "h2. Card The ASP.Net MVC framework uses HTML helpers to simplify rendering of common HTML elements.  Modules written using the MVC framework should be able to utilize all core HTML helpers including:  h3. Form Helpers * BeginForm() * * EndForm() * * TextArea() * TextBox() * CheckBox() * RadioButton() * ListBox() * DropDownList() * Hidden() * Password()  h3. Validation Helpers * ValidationSummary * ValidationMessage * ValidationMessageFor  h3. Misc Helpers * ActionLink  h2. Conversation Should add URL and AJAX helpers  h2. Confirmation"
Answer: 322.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: "h2. Card Currently DNN modules use an IActionable interface to define custom module actions which are rendered in the Module Action Menu.  The purpose of the interface is to define a well known method that can be called by the framework to retrieve a collection of actions defined by the module developer.  Each controller action may be used to render a view and thus should be able to define a collection of actions which the framework can retrieve and render.  h2. Conversation A custom method attribute could be used to identify a method that returns a collection of actions.  The method must implement a predefined signature but could be located in any class which is accessible by the core framework.  It should not be necessary to define the action items in the same controller as the action which relies on the action collection.  h2. Confirmation The two attributes should be: * *ModuleActionAttribute* - This attribute is used to define a single Module Action and only supports the most common features of module actions.  This attribute allows the controlkey, icon, security level, and title to be set for the module action. For greater control over all module action functionality, the ModuleActionItems attribute should be used.  * *ModuleActionItemsAttribute* - This attribute is used to identify a type and a method which can be called by the framework to retrieve a collection of ModuleActions. By convention, if the type is not defined, it will assume the method exists in the controller.  By convention, if the method is not defined, it will assume a method name which corresponds with the action decorated by the Attribute instance (e.g. the Edit action method would have a corresponding GetEditActions method)."
Answer: 361.0

User story: "h2. Card  As part of the MVC module support, the platform should be extended to allow module developers to create MVC controllers.  Each defined controller should support the creation of multiple controller actions.      h2. Conversation  DNN must support the creation of Controllers written in C#. Support for controllers written in VB is optional.    All module controllers should inherit from a DNN specific base controller.  The base controller should include context information including the current module information, current page, and current portalsettings.    h2. Confirmation"
Answer: 821.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: "h2. Card The DNN core platform uses modules as the primary mechanism for adding new functionality that includes both business logic and user interface elements.  The current implementation is based on ASP.Net web forms and allows module developers to use web controls or server controls for rendering the UI.  The platform should be extended to allow module developers to create modules using the ASP.Net MVC framework.  A module should support the use of MVC views using the Razor view engine.    h2. Conversation DNN must support the use of C# razor views. Support for VB based views is optional.  MVC views should have access to intrinsics like the Model and ViewBag objects.  MVC views must be rendered inside the content area of the module container without injecting any additional HTML elements beyond what is defined in the container and the view.  All module views should inherit from a DNN specific base viewpage and should be able to define the model type as part of the view definition. A sample implementation might look like: @inherits DnnViewPage<MyModels.ModuleInfo>  It should also support implicit inheritance and then define a model using the @model helper.  h2. Confirmation"
Answer: 887.0

User story: "h2. Card  The Skin module is used to manage which themes are installed in DNN. The administrator can quickly see all of the theme and container layouts for installed themes.  The SkinDesigner module supplements the Skin module to allow the administrator to override predifined settings for objects defined in the theme.    In this release, these two modules should be refactored into a single module and separated from the core platform.  The core APIs, db schema and stored procedures should remain in the core platform.    h2. Conversation    h2. Confirmation"
Answer: 263600.0

User story: "h2. Card  The Site Wizard is used for creating child portals or applying site templates to the existing portal. The site wizard is just a thin UI over the top of core portal management APIs.  These APIs will remain part of the core platform.    h2. Conversation      h2. Confirmation  "
Answer: 243702.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: "h2. Card  The Site Log is used to log system activity. Since it was first introduced, newer and better logging options have been added to the platform. All site log APIs and associated database schema and SPROCs should be removed from the core platform and included in the SiteLog module.      h2. Conversation  As part of extracting this module, upgrade logic should be added to the platform to remove any scheduled tasks and stored procedures related to this feature. The sitelog module should also be removed from the appropriate extensions tables. The sitelog table will remain *untouched* to avoid any potential data loss.    The Site Log module should be moved to [https://github.com/dnncommunity] and registered in the Forge.    h2. Confirmation  There should be no site or host settings referencing SiteLog settings.  SiteLog related settings should be deprecated in Portal and Host classes but can be completely removed in cases where the class only exists to support SiteLog. New installs and upgrades alike should not have this module (under extensions) or the Admin pages available post upgrade/install. Also, as part of this the extracted module should live in a new github repository here: https://github.com/DNNCommunity/Dnn.SiteLog    NOTE: This will introduce a known breaking change for anyone who might call the SiteLog APIs.  It will also remove a feature that might be in use on some websites."
Answer: 244734.0

User story: "h2. Card  The Sitemap Settings module is used for configuring the sitemap. The sitemap APIs and associated database schema and SPROCs should remain in the core platform.    h2. Conversation      h2. Confirmation  "
Answer: 245237.0

User story: "h2. Card  The Page Manager module is used for managing pages in an individual site. The page/tab APIs and associated database schema and SPROCs should remain in the core platform.  Any APIs which are strictly used for presentation purposes should be removed from the platform and included with the module.    h2. Conversation      h2. Confirmation  "
Answer: 245387.0

User story: "h2. Card  The List module is used for managing system lists by host users. The list APIs and associated database schema and SPROCs should remain in the core platform.     h2. Conversation      h2. Confirmation  "
Answer: 245390.0

User story: "h2. Card  The Google Analytics module is used for integrating Google Analytics into a user's website. The Google Analytics APIs and associated database schema and SPROCs should remain in the core platform.      h2. Conversation      h2. Confirmation  "
Answer: 249617.0

User story: "h2. Card  The Event Viewer module is used for managing the event logs. The eventlog APIs and associated database schema and SPROCs should remain in the core platform.  Any APIs which are strictly used for presentation purposes should be removed from the platform and included with the module.    h2. Conversation      h2. Confirmation  "
Answer: 249556.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 profilepic imagehandler is very restricted in his functionality. An imagehandler with more possibilities to show and manipulate images would be a great  addition to DNN. Please see my pull request. Documentation follows."
Answer: 11420.0

User story: "h2. Card  Each administrative function identified below should be separated into an independent module.  We could choose to install or not install a given module into the final DNN CMS distribution.    h3. Admin Only Features  * Newsletter  * Recycle Bin  * Event Viewer  * Google Analytics  * List Editor  * Page Manager  * Sitemap  * Site Log  * Site Wizard  * Themes  * Roles    h3. Host  * Configuration Manager  * Dashboard  * SQL Module  * Digital Asset Manager (File Manager)  * Extensions  * HTML Editor Manager  * Scheduler  * Users  * Vendors/Banners    h2. Conversation    h2. Confirmation  The following areas are out of scope:  * Site Settings  * Host Settings  * Module Settings  * Page Settings"
Answer: 310194.0

User story: "h2. Card  Create a Captcha Provider to implement the reCaptcha control from Google. The provider must include the ability to register the appropriate reCaptcha API keys.    h2. Conversation    h2. Confirmation  "
Answer: 1014365.0

User story: "h2. Card  The current captcha control used in DNN is delivered as a standard user interface component.  Whenever the core framework or a module wishes to enable captcha support, the captcha control is added to the UI and displayed as appropriate.      The current Captcha control should be refactored into a Captcha provider.  This will simplify the process of integrating third party services like reCaptcha and allow the community to develop a number of different approaches to solving this issue.    The provider must include the ability for a Captcha implementation to include both a main view as well as a settings view.  The main view will be displayed where ever the captcha is used.  The settings view should be displayed as part of the settings for the provider which is accessible from the Admin extensions page.     h2. Conversation    h2. Confirmation    "
Answer: 1014370.0

User story: "This module should be moved to a separate github repo in the github.com/dnncommunity organization.    This will impact both installs and upgrades. It also means that the newsletter module page under admin will be removed in both scenarios.   "
Answer: 311184.0

User story: "ASP.NET MVC has become the development platform of choice in the ASP.NET world.    This enhancement adds core support for MVC modules - modules built using the ASP.NET MVC paradigm."
Answer: 77407.0

User story: "Razor support was added as an external project but that requires reflection to use.    As we move into a Razor, Html5, MVC universe this support should be moved to the core."
Answer: 86.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: "More and more modules are being created using HTML5/Javascript and WebAPI.  Currently this requires the HTML to be created in a UserControl.    This enhancement will add support to the Module Injection logic to directly support Html files (using the extension html or htm).    These fields will then be automatically wrapped in a LiteralControl to be added to the control tree."
Answer: 307114.0

User story: "Page events were missed from the linked story.  We need to ensure there are additional events for the following (will be useful in Content):  - Page Restored  - Page marked as Published"
Answer: 2.0

User story: "A few events were missed from the linked story.    We need to ensure there are additional events for the following (most are for Content):  - Group/Role Created  - Group/Role Deleted  - Group/Role Joined  - Group/Role Left  - UserAuthenticated  "
Answer: 95.0

User story: "h3. Card:  As a user, I want to use the term themes instead of skins    h3. Conversation:    h3. Confirmation:  We need to go through the system and replace the word skins with the themes  The changes involve the platform and content    h3. Note:  This change needs to be released in 7.4.0  "
Answer: 1312.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 an administrator, I want to use an external folder provider for the root folders of my site, but I also want to include a subfolder of a different folder provider type, so I can have all of my user data stored on a mix of external storage.    h2.  Conversation  In Version 7.3, a new feature was added which allows for the external storage of a new site to be created using a folder provider for external storage.  This allows setup of new sites to be started with all 'user' data stored separately from the application files.  This allows for leverage of geo-redundant storage in cloud providers, use of CDNs and simpler and faster backups for the application files themselves.    However, due to the design of folder providers, once an external folder provider is used, no subfolders of another folder provider type can be used.  This prevents someone leveraging external folder providers for the site root further leveraging another folder provider in their site (ie, using a dropbox folder provider for a certain folder, or using a database or secure folder provider).    This change is to relax that restriction to allow folders created in the root of the site to have subfolders of a different folder provider type.    Example:  root : Azure Storage  - images : Azure Storage  - Users : Azure Storage  - Documents : Dropbox  - Videos : AWS Provider  - Secure Documents : Secure Folders    In this example, only subfolders of the same type as the parent folder would be allowed to be created.    h2.  Confirmation  * Change restriction on subfolders so that subfolders of different provider types are allowed to be created at the root level of the site  * 'child' subfolders of root-level subfolders can only be created of the same type as the parent.  * Both external and standard folder providers would be supported for creation of subfolders    "
Answer: 100288.0

User story: "This is about adding events to the Platform so that listeners can know when multiple items occur so we can then hook into mechanics and log activity when this happens (similar to what we do w/ Users today and portals).     We need to ensure there are additional events for the following (most are for Content):  - Relationship Formed (added a friend/followed someone)  - Relationship Dissolved (removed a friend/stopped following)  - Folder Created (DAM Should have this today)  - Folder Deleted (DAM Should have this today)  - Folder Updated (DAM Should have this today)  - File Created (DAM Should have this today)  - File Deleted (DAM Should have this today)  - File Updated (DAM Should have this today)  - Page/Tab Created  - Page/Tab Deleted  - Page/Tab Updated  - Module Created  - Module Deleted  - Module Updated"
Answer: 54640.0

User story: "We want to allow the addtiion of extension points on the Page Settings > Page details sections"
Answer: 74369.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: h2. Card:  Site Settings extension point code references to DigitalAssets Module. This should be something more generic as other module could inject some extensions. The module name used in the extension point metadata should be "SiteSettings".    
Answer: 5518.0

User story: "Existing Platform has two workflow systems – one for the Text/Html module and one for the File Management.  It is important that these two different approaches are merged into a single workflow.       The workflow should use the generic ‘State Management’ concept developed for the Text/Html module, so that it can be expanded out to handle entities of any type, defined by third party developers.    The internal workflows will be tied to Content Items, and each of the workflow-controlled pieces will be a Content Item.    Requirements  * Unified Workflow system for all workflow-controlled entities  * All workflow-controlled entities in Evoq should be be content items  * Workflow to adapt to content items, but is not restricted to content items    h4.Workflow API  One of the key goals of the next release is the unified Workflow.   The single set of tables will be located at the DNN Platform level.   The design of workflow will allow any entity to be tracked through the Workflow states.    Locating the workflow at the DNN Platform level will encourage adoption by 3rd party developers which will strengthen the value of the Workflow system. While the Workflow UI will not be included with DNN platform, the default Workflows will be included.  It will be possible     Requirements  The public API for the Workflow process will be exposed at the DNN Platform level.   This public API will involve the following functions (at a high level)  * Start a workflow Process on an entity  * Move the entity through the process by approval  * Move the entity back through the process by rejection  * Publish the entity    In addition to the API, the following actions will occur during the API calls  * Send workflow notifications to related security groups via the DNN private messages    Out of scope of the Public API is:  * Exposing the File Management workflow UI in DNN Platform  * Exposing the Workflow Management UI in DNN Platform  * Providing the page-level history, versioning and publish/reject control    Essentially, the Workflow API is about exposing a state-tracking subsystem to allow vendors to build modules targeting a standardized platform.  "
Answer: 148280.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: "Environments with large numbers of portals exhibit different performance characteristics than environments with a single portal. We need to test the performance of an installation with 100 portals ( using the default website template for each portal ) by sending random traffic to each of the portals and observing the behavior. "
Answer: 17298.0

User story: " When the permissions grid is expanded beyond the ability to view horizontally, then it should scroll horizontally, leaving the role name and ‘actions’ column visible.  The scroll bar can be watched in the below image:  !https://dnntracker.atlassian.net/secure/attachment/15027/15027_grid-horizontal-scroll.png!    h3. Confirmation  - If the number of permissions columns exceeds the available width of the grid, a horizontal scroll bar will appear, which will scroll the centre of the permissions grid but leave the first and last columns fixed."
Answer: 1426368.0

User story: GetSearchModules is very chatty and requires multiple calls to get the modules which can be indexed (this is not cached so executes every time the indexer runs).      It also makes unnecessary calls to Get Tab Settings and GetTabModuleSettings and forces those collections to effectively be permanently in memory.  The "AllowIndex" setting could be moved to be part of the "ModuleInfo" object and TabInfo object which mean they were already cached.
Answer: 1427365.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 site administrator, I want an easy way to add a new group or user to the permissions grid of a content piece so that I can quickly achieve my task.+  h3. Conversation The current permissions grid design works well for the default installed list of users.  However, it does not scale well when large lists of groups are created.   Current Grid design: !current-grid-design.png!  The existing permissions grid will be replaced with a new design.  The new design lists only those permissions which are already set, and provides a way of adding new groups to have a permission configured.   1. Permissions grid – default view.  Shows Group/ Role drop downs and newly added role highlighted when added (yellow fades back).  Add username uses the drop-down list of users filtered as text is entered (existing implementation - see sending messages from user profile). !7-04-2014 9-06-52 AM.png!   2.  When the permissions grid is expanded beyond the ability to view horizontally, then it should scroll horizontally, leaving the role name and ‘actions’ column visible. !grid-horizontal-scroll (1).png!   h3. Confirmation - When the permissions grid loads, it shows only those permissions which are currently used for the object that the grid refers to - The ‘Add Role’ function is always visible to users who have the authority to change the permissions - When the ‘Add Role’ button is clicked, a row will be added to the top of the grid, and will briefly change color to highlight that it has just been added, as feedback to the user. - The ‘select role group’ and ‘select role’ drop downs will work with each other to filter down the entries, as is done elsewhere in DNN - If the number of permissions columns exceeds the available width of the grid, a horizontal scroll bar will appear, which will scroll the centre of the permissions grid but leave the first and last columns fixed. - All other permissions grid functions will work as normal. - Clicking on the ‘delete’ icon in the ‘Actions’ column will remove all permissions related to the role that was deleted. - Clicking on the ‘delete’ icon should show a confirmation dialog, including the name of the role clicked.   The text must come from the correct resources file, and the English confirmation should be: o Title : Confirm Role Permission Delete o Question : Are you sure you wish to delete the permissions for [role name]? o Buttons : Yes/No or OK/Cancel.  NOTE : Horizontal scrolling is lower priority than all the other changes.  +Testing Notes+ This is for performance reasons.  We need to test that the performance is improved when loading a large table of permissions."
Answer: 62494.0

User story: "{{Globals.NavigateURL}} is called many times per page load, so any hot paths within it need to be optimized."
Answer: 25721.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We need to improve the performance of a basic page with HTML modules, when visited by Administrators and Host users.    This will test the full impact of the Control Bar.    We will follow the overall guidelines for this scenario as described in the Epic."
Answer: 245.0

User story: Relocate Host Settings > Other Settings > Scheduler Mode to a collapsible "Settings" panel at the bottom of the main Scheduler UI view.
Answer: 23945.0

User story: "There should be an API method which can be called within a scheduled task that would append a status message to the job history. Then when the the history is checked through the UI, the administrator could get additional feedback about the progress of the job."
Answer: 40827.0

User story: "A user should have the ability to Stop an already executing scheduled job. We need to do a spike to determine the feasibility of allowing this without requiring developers to write more code in their scheduled tasks."
Answer: 34128.0

User story: "When a scheduled job is specified to run on ALL servers, if the site is configured to use Server Groups then the job should only run on servers that are part of the Group."
Answer: 40825.0

User story: When running a scheduled job, the Next Start is set based on the date/time when the job last completed. As a result, the start time for scheduled jobs will "creep" over time and evantually cause problems if you are relying on jobs to run in a specific order. it should be possible that the Next Start is based on the time of the previous Start. 
Answer: 31227.0

User story: "We will add a Scheduler Settings option where you can specify the Delay After Site Restart option ( in minutes ). The default will be 1 minute but it can be overridden. In both Timer and Request mode the scheduler will not kick off any jobs until the Delay has elapsed."
Answer: 62943.0

User story: "The Schedule Status UI should be enhanced to include the ability to choose a specific server. This will allow you to view what is executing on a specific server, its status and history, and provide the ability to start and stop the scheduler."
Answer: 31021.0

User story: "When managing a scheduled job, it should be possible to specify server names that are not part of the current farm configuration. This is required so that you can configure a single installation and have it work seamlessly in staging and production. From a user interface perspective it would be beneficial to simpy allow for a comma delimited text box for Server data entry - but perhaps also have a dropdown box that contains the list of servers in that environment that the user can select and add to the textbox."
Answer: 40842.0

User story: "When defining a new scheduled task and if running in a web farm, the user should be able to specify the server(s) the task needs to execute on "
Answer: 35062.0

User story: "The Recurring and Retry Frequency should also support the ability to execute every X seconds, every X weeks, every X months, and every X years. "
Answer: 23979.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: "When managing a scheduled job you should be able to optionally specify a Start Date and/or a Start Time. The scheduler logic will need to be modified to set the NextStart for a task based on the Start Date and Start Time defined for the task. NOTE: this does not guarantee that the job will actually run precisely at the specified Start Date / Start Time. If the server is down at the time it is supposed to run or other jobs are already running, then it will run as soon as the server comes back on online.      "
Answer: 29934.0

User story: "After adding/modifying/deleting a scheduled job you should not have to restart the site for the changes to take effect. "
Answer: 24051.0

User story: "Main scheduler view should be sort in alphabetical order. It should also have a filter so that you can view the scheduled jobs for a specific Server or All ( All should be the default )"
Answer: 29391.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 easily upload files so that it doesn’t slow down my workflow+    h3. Conversation  The file picker/uploader has the ability to drop a file directly into the target location.  It also shows an ‘upload’ button.  This, and other upload buttons are used throughout DNN.  They generally launch an operating-system file picker to choose a file and upload it to the site.  These will all be replaced with a new file upload control which allows for multiple drag and drop.  There will be some exceptions to this, which are noted below in the ‘File Uploader – Replacments’ section.  In areas where the upload is to a fixed folder location (by the implementing code), the Folder location will not be visible.     !4-03-2014 3-24-20 PM.png!  Above : File Uploader (Folder picker enabled)     !4-03-2014 3-24-20 PM-2.png!  Above : File Uploader (No Folder picker)    h3. Confirmation  • File uploader will be launched by an ‘upload’ button  • File uploader is a popup  • Folder picker can either be available to choose the upload folder, or it will be hidden when the upload folder should not be changed  • The file uploader will not have the option of decompressing zip files in these use cases  • The file uploader will have the option of importing a file from a web location  • The file uploader will have the option of clicking to browse or using drag and drop    h2. File Upload – Replacement Locations  * Essentially wherever a file upload is to be used  * Not for the XML Merge or Host->Extensions installer  * The URL control will incorporate the File Picker/Uploader control    Source Location    Id or container Comments  Controls\FilePickerUploader.ascx Postfile  Replaced with File Uploader (see other stories about file picker/uploader)  Controls\UrlControl.ascx   txtFile  File uploader  Modules\Groups\Create.ascx  inpFile  File uploader – no folder picker  Modules\Groups\GroupEdit.ascx inpFile  File uploader – no folder picker  Modules\Journal\MyFiles.ascx  fileUp  File uploader – no folder picker  Admin\SQL\sql.ascx    uplSqlScript File uploader – no folder picker  Should also load file immediately after upload.  Admin\XmlMerge\XmlMerge.ascx No Change Leave upload as is  Admin\Extensions\Install.ascx  No Change Leave upload as is    "
Answer: 33064.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 of the site, I want a simple, searchable and usable control to select files so that the page responds quickly and I don’t have to work through a very long drop-down list to find a file+    h2. Conversation  All file selections in DNN use a File Drop down, which is unwieldy and slow when the number of files in a folder increases.  This change will replace the use of drop-downs for file selection with a file picker in the same pattern as the folder and page pickers already developed.     !file-picker.png!  Above : New File Picker control    h2. Confirmation  • File picker includes search box  • File picker lazy loads the data  • File picker uses same presentation and similar logic to the existing page and folder picker controls.    h3. File Picker - Replacement Locations  - The changes will be made in the control ‘FilePickerUploader’  - In the ‘FileRow’ container of urlcontrol.ascx, where the existing file/folder pickers will be replaced with the FilePickerUploader control.  - In the ‘dnnExport’ container of Modules\Export.ascx [with no upload functionality]  - In the ‘importModuleForm container of Modules\import.ascx [with no upload functionality]    Control        Id of container   Type  UrlControl.ascx       FileRow    Folder/File Picker Uploader  Modules\Export.ascx     dnnExport  Folder/File Picker  Modules\Import.ascx     importModuleForm Folder/File Picker  Admin\SkinDesigner\Attributes.ascx   dnnEditSkins  Folder/File Picker  Admin\Modules\ViewSource.ascx   dnnViewSource File picker/uploader  Admin\Extensions\EditModuleDefinition.ascx rowFile1   File picker (no folder)  Admin\SkinDesigner\Attributes.ascx   cboFiles   File picker (no folder)    Any other areas of the application or modules where a file picker is found should be raised – the default will be to replace any file drop down with the new picker control, unless there is a compelling reason not to.  "
Answer: 41610.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 of the site, when I upload a file, I want to have the option of using drag and drop, selecting from a list or searching for a file so that I can choose the fastest way of selecting a file for my needs.+    h2. Conversation    Throughout DNN a combination file picker/uploader is used.  This allows users to either choose an existing file or to upload a new file to the location specified.  The new design will retain the presentation of the old design, but will change the style of the drop-downs to ensure that they do not grow large when the underlying list is large – whether that is folders or files.   This will ensure faster performance of the UI and easier user experience to find a file or folder.  The drag-and-drop uploader makes selection of a file simpler.  This feature will remain as is currently in use.    !file-picker-uploader-closed.png!   Above : File Picker in use, showing current file selected     !file-picker-uploader-folder-open.png!  Above : File Picker in use, showing Folder selection drop down.     !file-picker-upload-file-open.png!  Above: File picker in use, showing list of files in drop down.    h2. Confirmation  • The existing file picker / uploader control will have the folder and file drop-downs replaced  • The folder picker will be re-used as it is elsewhere in the DNN Platform (such as in the file Upload control)  • The file drop-down will be created to use the same style and functionality as the folder-picker, only it will list out the filenames instead of folder names  • If the folder picker changes the selection, the list of files in the file picker will change to match.  • The search for a filename will work by matching all the filenames in the selected folder.  • The file upload will work in the same way, and the file will be uploaded into the currently selected folder.  • The new file drop-down (the file picker) will be used as a stand-alone control, as well as being part of the file picker/uploader.    SEE CONTENT-2323 for linked PRD and implementation locations  "
Answer: 33347.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: "51Degrees V3 includes x100 faster algorithm, more device combinations, response time/bandwidth monitoring in real time, lower memory footprint and faster initialisation.    The data file is structured for performance when stored on the disk and does not need to be loaded into memory. The new algorithm offsets the performance penalty by being so much faster. The other advantage is that the startup time is a lot faster because the data does not need to be loaded into memory. The data file on the disk does however need to be uncompressed. For those needing faster performance and who can accept more memory usage there is an attribute called memoryMode (set to true) in the config file that will load it into memory.    Resources: http://51degrees.com/v3closedtesting    Minor code changes needed to the 51Degrees provider to make the Host -> Device Management screen work with version 3 ( attached )    New features will be available in the final V3 version that allow a host user to enable/disable the device detection logic by setting an Enabled attribute in the 51 Degrees config file. In addition there will be an option to enabled/disable AutoUpdates by setting an Enabled attribute in the 51 Degrees config file. These options should be exposed through the Device Detection Management user interface."
Answer: 65602.0

User story: "Following the process described in the Epic this class needs to be cleaned up so there is only location for RoleController methods."
Answer: 31680.0

User story: "Following the process described in the Epic this class needs to be cleaned up so there is only location for UserController methods."
Answer: 22545.0

User story: "Following the process described in the Epic this class needs to be cleaned up so there is only location for PortalAliasController methods."
Answer: 9630.0

User story: "Following the process described in the Epic this class needs to be cleaned up so there is only location for TabController methods."
Answer: 13963.0

User story: "Following the process described in the Epic this class needs to be cleaned up so there is only location for ModuleController methods."
Answer: 15400.0

User story: "We need to improve the performance of the Edit Module Settings Scenario.    Note this scenario needs to be tested for scalability (large number of pages and folders/files)    We will follow the overall guidelines for this scenario as described in the Epic."
Answer: 73083.0

User story: "We need to improve the performance of the Edit Page Scenario.    Note this scenario needs to be tested for scalability (large number of pages and folders/files)    We will follow the overall guidelines for this scenario as described in the Epic."
Answer: 72987.0

User story: "We need to improve the performance of the Register Scenario.    We will follow the overall guidelines for this scenario as described in the Epic."
Answer: 51825.0