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: "Agenda - Drillbit - SmokeTest - Blog Posts - Last week's unfinished issues - Planning this week"
Answer: 3053.0

User story: "Stephen and I need to get together and hash out correct behavior for the debugger in 1.7"
Answer: 12844.0

User story: "{html}<div><p>Currently there are some inconsistencies between event names  (camelCase or not). Getting event case parity for the platform  would be nice.</p></div>{html}"
Answer: 3233911.0

User story: *Background*:  After DNN-10583 "Pormpt needs to be allow hosts to script across portals"  we start to see some observations that might be issue in the prompt implementation, not the above ticket - so created this story to log and track the history and investigation notes by development team     # By general cross portal - utilize the current child site implementation and had the same limitation that (roles - users ) are not cross site accessible   # For prompt cross portal please check the above ticket
Answer: 1.0

User story: "In the past, it was possible to search across super users (if you were a super user yourself). In the conversion from 8.x to 9.x, this functionality was lost.     Note: This functionality should be available only to hosts/super users (not administrators or anyone else). "
Answer: 42767.0

User story: "This is about marking all methods in the product as obsolete as of version 9.2 (so they can eventually be removed from the code base in version 11 or similar). "
Answer: 37475.0

User story: Per DNN-10059, we now allow users to upload portal-specific themes to the site, but we still don't differentiate on which themes are portal-specific or global.    This story is to introduce a UI update into Themes which will differentiate global vs. portal themes.    ***********  Design Notes:  1. Add headings for "GLOBAL THEMES" and "SITE THEMES" as shown in the mockup, with a line separator as shown.    2. Add a dropdown filter, visible to both Host and Admin users. By default it should show All Themes, but they can choose to view Global Themes or Site Themes. Site owners (admins) should see all global themes and the portal-specific themes for only their portal. If either Global-only or Portal-only themes are selected to be displayed: the label, themes, and line separator are hidden, and should only see that section header.    3. One other clean up item on this page:  In the implementation, of the Selected Theme Panel at the top, it is the wrong color.  It should be WHITE #FFFFFF, but it is currently showing up as ALABASTER
Answer: 10073.0

User story: "Per Sprint 1 Review feedback, this module needs to have a full width view. This means taking over the area currently used for Notifications.    Please expand the module area to fill the extra pixels once Prompt is opened."
Answer: 13219.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 you type Help in the module, it gives it in English only. The command help information are  stored in html files. We want the command itself to be in English, but the help text should be translatable.  It will need changes to make help dynamically generated from command descriptions."
Answer: 22992.0

User story: "We recently ran into a problem where specific module have to create its own version of cdv concept to force a client side refresh of any css and js after upgrading.    In this proposal we should study how to resolve this issue at platform level with the following possible approaches:  # add a new tag in the module manifest a new flag to force cdv increment after module upgrade  ## pro: we reuse the same cdv mechanism provided in the platform  ## cons: we are refreshing the entire static assets cache of the site just for a specific module  NOTE: we should ensure adding a new tag in the manifest will be backward compatible if module vendor want to allow its module to install in previous platform version. In those the tag will be just ingnored.  # consider the creation of a new mechanism at module level (i.e. mcdv) provided by the platform that will automatically append this new parameter and force specific module assets client cache invalidation  ## pro: we will refresh only the module specific assets (not the entire site)  ## cons: if modules are using the same js/css we are forcing the client to down it twice    We will need to consider the two solutions."
Answer: 23706.0

User story: The in-context menu will be displayed when clicking on the ellipses item in the treeview. It will have 4 actions in Platform and 5 in Evoq.     Actions:  - Add Page(s)  -- This will display an input (textbox) below the current selected menu item (this will allow you to create a child page of the selected page inline)  - View  -- This will navigate the user to the page (and ensure the persona bar is closed); existing behavior  - Edit  -- This will navigate the user to the page and have it in edit mode (and ensure the persona bar is closed); existing behavior  - Duplicate  --   - Analytics  -- This will navigate the user to the analytics section of the persona bar and display the analytics for the specific page    Platform vs. Evoq:  - The "Analytics" option will only be available in Evoq Content & Evoq Engage (not in Platform or Basic)  - There is an icon displayed to the right of the menu item when a page has unpublished changes (this will only be seen in Evoq)
Answer: 11279.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This UI is seen when a user types in at least 3 characters into the search area of pages or when they click the search icon within pages header area. When the search results view (the list of items) is displayed, the "Add Page" button should be disabled and the header area in the persona bar needs to say "Page Search Results" as the header and the breadcrumb will be available (and selected where the user previously was before viewing search results). The back to page will also take the end user back to where they were (prior to searching).     User's can filter their results down further by selecting additional filters. When applied, these will be shown at the top of the results lists in a tag like UI fashion. This will allow users to delete a specific filter and have the results immediately updated (when clearing a filter, always go back to page 1).     When results are displayed, a thumbnail (in Evoq only) will be displayed that shows a larger version seen when user's hover on the smaller thumbnail. If a specific page is clicked, it's page settings will be opened in the page management area of the persona bar (so switch from search results to the page details).     Search Filters:  - Page Type (drop down)  -- URL, File, Page  - Publish Status (drop down)  -- Published, Draft  - Published Range (start/end dates; date picker w/ no time)  - Tags (multi-line textbox that can be comma or semicolon separated)    Evoq vs Platform:  - All search fields will be available in both products but in Platform the published status field would only have 1  - In Platform, the thumbnail (which also exposes a larger view) won't be available and items will 'slide' to the left  - Workflow field (in search results per item) will be hidden in Platform   - In Platform, the last published date will be the last modified date, in Evoq this date will be the last published version's last modified date    Notes:  - Once the search results screen is displayed, a user must click "Back to Page" to get back to where they were  -- Deleting input characters does *NOT* take them back  - On the search results screen, the following actions can be taken (see mockup for hover state on a search result):  -- Clicking on the Name of the Search Result opens that Page's Settings (and the tree and other disabled elements are re-activated)  -- The blue text in fields below (page type, publish status, workflow, tags) are clickable as well, and clicking on one of them ADDS that search filter to the list of filters above. If that filter has already been applied, it does nothing.  -- Notice that on hover, top right there are three other icons, these allow the user to jump to other relevant pages: the eye icon opens that page, the pencil icon opens the page to EDIT MODE, and the chart icon opens to the Page Analytics for that page
Answer: 152535.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: Page details are seen when a user selects a page from the treeview menu or when navigating directly by clicking the gear icon (to get to page settings) from the edit bar. The treeview will have a selected state and the existing tabbed UI (after being updated to use React) will be placed in this area.     Evoq vs Platform:  - There is no thumbnail generated in Platform, so the thumbnail won't be there in Platform (all items to the right of it will move to the left and take up it's space)  - The "Workflow" dropdown will not be available in Platform (this area will just be 'blank')
Answer: 5574.0

User story: When the pages area is selected from the persona bar's menu area, the first view end users should see is the treeview collapsed (treeview covered via a separate Jira) and the area to the right should show an empty state (as shown in the attached mockup) instead of displaying page details (since no page is selected).     Platform vs. Evoq:  - Add Page button will only be displayed when the user has edit permissions  -- In Evoq, this will be displayed if the user has"Add" permissions
Answer: 2591.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This is about getting the base DNN Prompt and it's code under Platform source control and being installed as part of the base Platform (for 9.2 forward). This will only be available to super users (hosts) and will be under the "Settings" menu. 
Answer: 10036.0

User story: "This story is about moving the Azure connector from Basic to Platform. "
Answer: 10085.0

User story: Currently, code is contained exclusively in Evoq for creator connectors (as an extension package type). This code needs to be moved to the Platform and connectors should be available in all packages we ship (in new installs and upgrade scenarios). As part of this story, the naming of EvoqConnectors needs to be changed to simply "Connectors".     Because Evoq shipped with Evoq Connectors, database updates will be required in upgrade scenarios (should only apply to Evoq products that are upgrading from Evoq 8-9.1.x; older versions didn't have EvoqConnectors). 
Answer: 327.0

User story: *Issue:*    The Task history UI is not consistent with the UI pattern the rest of the persona bar tables are headed in, needs to be updated to match.    *General Requirement:*    Revise the UI pattern for Task History to match our typical persona bar pattern "In Line" row details - i.e. a contained table within an "expanded row' (similar to the role membership icon in the Users table).  See attached mockup for a revised Task History UI.     !Screenshot Markup_task history.png|width=700!    !Mockup_task history revised-06.png|width=700! 
Answer: 1.0

User story: "The story is about ensure the Platform is fips compliant.    Action items:  * review code to find usage of no fips complaint algorithm  * PortalSecurity.DecryptString/EncryptString: these methods makes use of MD5 hashing (this is no fips compliant)  ** mark PortalSecurity.DecryptString and EncryptString as obsolete pointing devs to use the other PortalSecurity.Decrypt and Encrypt method  ** Review usage of PortalSecurity.DecryptString and EncryptString and study a possible migration to PortalSecurity.Decrypt/Encrypt ensuring no lost data on upgrade."
Answer: 1328.0

User story: "Develop UI for Page-Picker-Component   * CSS styling (Remove dynamic inline styles)  * Follows functionality discussed with George for partial selections   * Follows same component functionality already on auto.engage458.com"
Answer: 45851.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 old Interface IPortable has two methods:    {code}  <param name="moduleId">The Id of the module to be exported</param>  public string ExportModule(int moduleId)    <param name="moduleId">The Id of the module to be imported</param>  <param name="content">The content to be imported</param>  <param name="version">The version of the module to be imported</param>  <param name="UserId">The Id of the user performing the import</param>  public void ImportModule(int moduleId, string content, string version, int userId)  {code}    The ExportModule does not support changes in content since a given time. It exports the entire content.    We need to create new Interface *IPortable2* with datetime in the Export method.    The export engine must be backwards compatible with the old interface. Module developers should implement the new Interface going forward.    Interface discovery should be done the same way as other interfaces in DNN - using *BusinessController*
Answer: 20149.0

User story: "A given module can be shared on all the pages. We do not want to export it one per page. Instead, it should be exported just once, with enough information to indicate that it's shared across all the pages."
Answer: 20124.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 previously allowed a page to be exported (prior to 9.1) and this wrote the tab settings (most of them), modules and module settings (along with tab module settings) to the export file (in xml). We want to retain everything it previously did (not necessarily how it did things before) and then account for additional concerns. When "Include Content" is chosen as part of the export process, this is when the modules and the module settings (along with TabModuleSettings) should be included (like older versions). When a page exists in the import, the import process needs to replace it (in the end, the page should look identical to the place it was exported from and nothing should be in the recycle bin in the destination related to the page).     *Page Settings to Export*  - Details:   -- Page Type (Based on type, all values surfaced like PermanentRedirect, DisableLink), Name, Title, Description, Keywords, Tags, Display in menu, Link Tracking, Enable Scheduling (start/end dates if applicable), Workflow  - Permissions:  -- Include all role and user permissions that are applied ONLY if permissions are selected as part of export  - Advanced:   -- Appearance: Page Theme, Layout & container along with stylesheet  -- SEO: Sitemap Priority, Page Header Tags, Allow Indexing (moving from More Tab see [DNN-9301]), URLs  -- More: Secure Connection, Disable Page (adding, see [DNN-9301]), Output Cache Provider  - No UI:  -- CultureCode, IconFileLarge, IconFile    Related Jira Notes:  - [DNN-9628]: This is something that is determined as part of the export process.   - [CONTENT-6092]: We are only including published pages in the export and therefore all imported pages should be published upon successful import.   - [DNN-9212]: We will continue to include taburls but it shouldn't be based on any id (on the name, instead)  - [DNN-8219]: Including CSS files  - [DNN-9543]: We need to include the setting "allow indexing"  - [DNN-7700]: Culture Code should be part of page export (and import)  - [DNN-8856]: We need to include page tags (and categories)    Note in Scope:  - Page content items  - Module content items  - TabAliasSkin  - Tab Versions
Answer: 63690.0

User story: "The exported data and files (when any) need to be zipped in one. For security reasons, this will need to be saved as a .resources extension. "
Answer: 58461.0

User story: "- All Portal Settings data (any property from the table should automatically be included)  - Anything related to portal alias data will not be included"
Answer: 8862.0

User story: "This is a sub task for the Permissions part of Site I/E."
Answer: 11433.0

User story: This is a sub task for the Profile Properties part of Site I/E.    User Profile Properties will be an all-or-nothing operation. No option to choose individual propeties. On Export, profile properties should only be exported IF "Users" AND "Profile Properties" is selected. Otherwise, export should not take user profile properties. On Import, the system should not disturb existing users or properties. 
Answer: 21870.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This is a sub task for the Vocabularies part of Site I/E.    Vocabularies Export is an all-or-nothing operation. No option to selected vocab groups or individual terms. The system should take care not to disturb existing vocabulary usage--if replacing existing vocabularies will not disturb a site then that is acceptable. Otherwise, the system needs to check for duplicates and not overwrite those duplicates."
Answer: 21874.0

User story: "This is a sub task for the Roles part of Site I/E.    Roles will be an all-or-nothing operation. No selection to choose which roles to export/import and which ones to leave alone. The import process should also check for duplicates and not replace or disturb existing roles or users of those roles. If, on export, there are users assigned to a new role--on import, those roles should populate with the assigned users as well."
Answer: 21874.0

User story: This is a sub task for the Users part of Site I/E.    Users will be an all-or-nothing operation. No option to choose individuals. On import, the system should check for duplicates and not disturb existing users. Export function will take: membership information, username, password, email. It will also export user profile properties IF "Users" AND "Profile Properties" is selected on Export. Otherwise, export should not take user profile properties. 
Answer: 21873.0

User story: As you export a page, you are given an option to include the "Files". This functionality already exists in the Platform and this task is about ensuring it continues to work (as long as it is selected) with other updates being made to import/export. We should include any portal settings and folder provider settings related to mappings for external providers (like UNC, Box, Dropbox, Amazon S3, etc.).     Items Not In Scope (related to files/folders):  - No version history of files  - No folder subscriptions  - No file subscriptions  - Files within external folder providers (UNC, Box, Dropbox, Amazon S3, etc.)
Answer: 73370.0

User story: "When exporting a site, there is an option to include the content. When selected, content that is on pages (in modules that utilize IPortable currently) will be included as part of the export. This task is about ensuring that continues plus we also include content from Liquid content and Forms. "
Answer: 75042.0

User story: The existing Sites UI in the persona bar today (available to hosts) will need to be modified so that you can get to the import/export persona bar screen for a specific site from the sites UI. This will replace the "export" action available in versions prior to 9.1.     NOTE: This will be available in the Platform too
Answer: 62541.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 Importing, I need visual feedback on the process--including a summary of actions performed and errors, if any.     Upon entering the Import screen, the UI provide a user:  # A list of clickable cards representing the various exports available. Displayed in each card: export name, date, file name, website, export mode, file size  ** The default sort value will be Newest.  # Once selected the user is presented with a summary of what's included in the import package (users, files, roles, etc) and the option to "Overwrite Collisions" or not.    * Constant feedback on the import process while it is executing is important  ** Consider that this process may take some time, so it will need to keep the site alive and communication should persist until the operation is complete (success or failure)    
Answer: 1.0

User story: "When importing or exporting site/page content, the system needs to create two new log types (one for import, another for export). This is especially important for auditing purposes and to see when the last import/export action was taken (please use colors not currently in use).    Module Permissions:  * HOST user will have permission to select any site to Export/Import   * ADMIN user will only see the site(s) they have access to manage    The system will record Imports and Exports as _separate_ logs, each with their own time stamp and summary. The full import/export log will be represented on the Import / Export feature page exposed via a user interface that is similar to admin logs in terms of display and behavior that only displays the imports and exports that were logged.      * There will be 3 filter options: All Imports and Exports, All Imports, All Exports.   * There will be 5 columns: Date, Log type, Username, Site Name and Status (successful, failed, submitted, cancelled)  * Clicking into each will expand the log and display the summary    See mockups for additional information."
Answer: 51216.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 Host or Admin user, I want the ability to select portions of my site or my whole site, and export that as a .zip package for use in any other DNN site--for the purpose of creating new sites or moving from staging to production site. As much as we can, on behalf of the exporting user, we want to include all dependencies they will need for the content they are exporting (extension packages, for example). This functionality will be exposed in a new menu item under the Persona Bar > Settings area. Host users will also be able to get to this area via the Sites area within the persona bar (to export a specific site).     As a user selects options and then progress through the export process, they need to be presented with visual feedback letting them know what is occurring as they progress; including display of any warnings and errors identified as part of the export process.     *PERMISSION*  Admin and Host user have access to this functionality. The Admin user will have the ability to export the contents of only their site; whereas the Host user will be able to export any site.    *WHAT ARE WE EXPORTING*  Existing:  * Content - HTML, Content Types, Content Items and Visualizers  * Files  * Roles  * Profile Properties  * Pages (pick list with option to select/de-select all with a single click)    New:  * Users (each user's membership information: username, password, email, )  * * User profile property values (if users are selected AND profile properties)  * Extension packages (No UI)  ** Modules/Providers/Themes/Language Packs  ** Folder permissions  * HTML Provider Configuration (No UI)  * Vocabularies  * URL's and redirects (No UI)  ** Any AUM settings (site level), any page level redirects  * Evoq page templates (No UI)  * Evoq Connector Data (most of this is probably under portal settings)  * All Portal Settings data (any property from the table should automatically)  ** Anything related to portal alias data will not be included  * All Page Settings not currently included, per page  ** This should include any page header, scripts, etc. seen via the page settings UI    *ACCEPTANCE CRITERIA*  Upon Export, a .zip package should be created that installs into any other like-versioned DNN site (also log the export in the admin logs under a new log type for export). Import will be handled in a separate story.     FEEDBACK FROM SPRINT REVIEW:  * Remove field names (Template Name becomes Name)  * No difference between Platform and Evoq modules - take out the home page thumbnail  * Needs to be a warning in the UI when exporting *encrypted passwords* because they likely won't come with.  *Future Enhancement: restrict export job to one server."
Answer: 101857.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In order to simplify the export/import of a site, extension packages need to be included as part of a site export (if things have been installed since the last export). Most likely, this means we will need to keep copies of the originally installed zip packages after a successful installation (we cannot depend on the built-in packaging because it doesn't necessarily replicate how an extension was packaged).     We need to ensure that when doing so, we are saving them in a new folder with the .resources extension applied to them (to ensure outside users cannot directly download these files). It may be best to make an "Export" folder in the site root and store the packages here (like we do for install).     Note: There will be no UI for this story or anywhere we list the actual saved packages in the UI. Verification by QA for this story may require viewing the file system of the site in the noted folder for the zip files. 
Answer: 27365.0

User story: "As a Persona Bar user, with accessibility requirements, I need to successfully navigate the persona bar and perform actions, make selections and edit fields just as a person without these requirements would.    Acceptance Criteria  Navigate every menu available in the persona bar  * It will include Admin > Edit Profile page.  * This will +not+ include the HTML Editor Manager page. "
Answer: 46581.0

User story: "As an anonymous site user, with accessibility requirements, I need to navigate a website without impediment.     This story will need to test the following anonymous-access components:  * Home Page  * Search Results Page  * Register and Login pages    Acceptance Criteria  The standard Cavalier homepage, with no content present, must fully pass WCAG standards.    ToDo: Gather list of skin objects to be tested."
Answer: 2023.0

User story: "This process has been ongoing, however the following scenario needs to be complete for the next release:    Telerik should not be present on the page  * No Script Manager  * No Telerik Ajax Panel    *DNN Platform*  Telerik should only appear on the page with Asset Manager  * Telerik _will_ be installed by default    *Evoq*  Telerik should _not_ be installed by default  * It may be installed if a customer decides to install legacy digital asset manager"
Answer: 31196.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 Host persona, I want to know when DNN has released an update (standard or critical) so that I may update DNN Platform or Evoq to the newest version. This applies to *all* versions.    BEHAVIOR  This update notification would display just underneath the product name on the persona bar. Clicking the link would take the host user to the Update Service.  The update steps don't change from there and the update can proceed as normal. The update links are identical for Evoq and Platform    LINKS  Clicking the link will pass the necessary parameters for the update service to pull up the version# and display critical updates since that time. Three parameters in the URL: Platform #, Version #, Product Name.  * Platform - "http://update.dotnetnuke.com/redirect.aspx[platform#][version#][productname]"  ** ex. "http://update.dotnetnuke.com/redirect.aspx?core=070402&amp;version=070402&amp;type=Framework&amp;name=DNNCORP.CE"      Additional icon update:   The Update Service passes another image into the Extensions module (see attachment), and needs an update to match the current product. The image displays the most up-to-date version of the module (ex. 04.07.00)
Answer: 1267.0

User story: "The new PersonaBar doesn't appear in mobile devices (iPhone 6, etc). Mobile is critical for the success of DNN."
Answer: 84850.0

User story: "The Platform Person Bar requires several visual enhancements:  * Persona Bar menu items updated from english text to icons. This is a visual enhancement plus ensures that the Persona Bar is universally understood--no matter what language is being used.  * Addition of the hover state for the DNN icon. The hover state will display the following information:   ** DNN Platform + version #   ** .NET framework  ** Server name  ** [Upgrade to Evoq] hyperlink to 'www.dnnsoftware.com/products'  ** [Documentation] hyperlink to 'www.dnnsoftware.com/docs'  ** Logout  * The contrast ratio will be updated from its current iteration to make the menu items more readable and make the whole experience more appealing.  * The header font will be updated from Roboto Slab to Roboto  * The persona bar font will be updated from Source Code Pro to Open Sans semi-bold  * Change the color of inactive text on the menu flyouts, as well as the inactive icons to #868484    See attached mockups.    Also attached here are the SVG icons"
Answer: 6337.0

User story: "In the previous control/admin bar, you can enable/disable 3rd party advanced URL providers from the *Admin > Site Settings* page as well as edit settings for each provider. The new persona bar is missing this setting.     "
Answer: 37816.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 legacy DNN modules need to be removed from all new installs. They are as follows:  * Configuration Manager  * Dashboard  * Device Preview Management  * Extensions  * Host Settings  * Lists  * Pages  * Recycle Bin  * Scheduler  * Security Center  * Site Groups  * Site Management  * Site Wizard  * SQL  * Taxonomy Manager  * Themes  * User Switcher - This is Evoq only  * Users and Roles    Please advise if there are dependency issues with any of these modules and the effort required to successfully break the dependency. That may warrant a separate ticket created for those individual extensions."
Answer: 5838.0

User story: "As a Content Manager, Community Manager or Content Editor: I need the legacy persona bar removed and to use the newly designed persona bar. "
Answer: 50742.0

User story: "A customer has suggested that we add a feature allowing users be added to an existing security role if they meet an administrator assigned condition.    Example: Have all users with email addresses from a specific domain automatically  be added to a specified role."
Answer: 195933.0

User story: "A customer has requested that DNN have an option to enable two factor authentication. The customer added the following commentary:    {quote}Thanks Shawn.    I think part of the mechanism (sproc) is already available in EVOQ/DNN   database...   Sending a password reset sets an expiration time for the link to work.    A similar procedure could be tied into the logon link to send an email   containing   a randomly-generated string that the user types into the next screen for   validation,   and which expires in a defined time period (specified by the site   super-user).    (Would also be nice if the logon page allowed the user to choose whether   to send   the validation code to her registered email or to her registered phone   in a text message.)    Lastly, would be nice to have the feature available by website portal,   rather than tied   completely into the entire EVOQ/DNN instance, as some sites would   require a mixture   of authentication levels.{quote}"
Answer: 211.0

User story: "There are a couple of small changes that the Usage Details report in the extensions module could make to make its user experience smoother."
Answer: 5756.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: "Telerik is used in multiple areas throughout the Platform. With Platform version 8, we started making changes to completely move away from Telerik throughout the products. This story is about the areas worth converting over (some areas, it doesn't make sense because it would basically be a complete rewrite; like the old admin/host modules). We will have drop downs move to normal asp.net dropdown controls (html select inputs preferred), calendars can use pikaday (or some alternative as long as this is client-side focused, localizable for multiple cultures and it is not a server side .NET control) and grids should go to the standard asp.net grid (HTML/JavaScript alternatives preferred).     Non-module UI to Convert:  - URL Control (used in page settings, module settings, file upload from URL).   -- 4 drop downs  - Permissions Grids (used in page settings, module settings, extension deploy permissions)  -- 2 drop downs, 1 grid  - File Picker (used for profile photo)  -- 1 drop down  - Page Settings  -- 4 drop downs, 2 Date/Time Pickers, 1 grid  - Module Settings  -- 5 drop downs, 2 Date/Time Pickers, 1 grid    Areas to *NOT* Touch:  - Digital Asset Manager Module  - Document Viewer Module (Evoq only)  - Ribbon Bar: Control Panel (Ensure removed completely from product packaging)  - Any Admin/Host module removed in 9.0"
Answer: 548850.0

User story: We've made some customizations for a client which we think would be a good fit for inclusion in the core.  There's a "Lock Site" action added to the control bar, which allows a super-user to turn off modifications to the site (probably for entering some sort of maintenance mode).  For our client, the "good enough" way this is implemented is to disable the module actions whenever the site is locked (in addition, custom modules are able to access the locked status via a property on {{PortalSettings}} and do any additional changes, if desired).    Testing Notes:  - Test exposed on/off button in the control panel  - When on, verify that it disables module actions (for any user)
Answer: 17036.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: "Install an authentication handler similar to Basic and Digest Auth-Handlers basen on the  JTW standard ( https://tools.ietf.org/html/rfc7519  )"
Answer: 3931.0

User story: h2. Card  We need to completely remove the "Getting Started" from the template as well as anything special we do to inject this into the platform.     !GettingStarted.png!    h2. Conversation    h2. Confirmation  Note for DEV: please ensure that we remove anything related to that feature and we do not leave any dead code in the source.
Answer: 5785.0

User story: h2. Card  One DNN 7 "feature" that I think needs to be added to items for DNN 8 cleanup is the removal of the Advanced Settings screen.  This page was created to "simplify" settings by aggregating many common settings into one location.  What this ultimately did was complicate things by giving people multiple locations for accomplishing the same task.  It didn't remove options, but instead duplicated options that were already available.    !AdvancedConfigurationSettings.png!    h2. Conversation  Often the way this was implemented was by re-using existing user controls in the new Advanced Settings screen.  This approach is blocking the team's ability to separate out the Skins module since one of the user controls in the skins module is also used in the advanced settings page. See DNN-6637.    h2. Confirmation  The Advanced Configuration Setting page and module should be uninstalled and removed in upgrade and new install of platform 8.0  Note for DEV: please ensure that we remove anything related to that feature and we do not leave any dead code in the source. Keep in mind that probably all the user control used by this module does not belong to him as are from other module. In this case we cannot cleanup these files as part of this story.
Answer: 1.0

User story: "Re-design the DCC Admin's UI to look like the screenshots below."
Answer: 14827.0

User story: "h2. Card  As a DCC Viewer Editor, I want to be able to add content to items of type list and be able to see them.     h2. Conversation  This can be achieved by implementing the appropiate EditorFor methods in the class DotNetNuke.Web.Mvc.Helpers.HtmlEditorExtensions and the DisplayFor methods in the class HtmlDisplayExtensions for supporting fields of types list. This implementation will create html and javascript code to add/edit/delete elements to the list.  It mught be necessary to implement LabelFor methods in the DotNetNuke.Web.Mvc.Helpers.DnnLabelExtensions class"
Answer: 27.0

User story: "h2. Card  As part of DNN Platform modernization effort, we need to remove our platform dependency on Telerik.  The first step in doing this is to ensure that those 3rd party developers who rely on Telerik wrappers can still use those wrappers with minimal disruption.      h2. Conversation  This does not require actual removal of Telerik, but rather just a detangling of the control wrappers so they are in a separate assembly and can be shipped separately.    h2. Confirmation"
Answer: 21803.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  As a developer, I want to be able to define custom token types for my SPA module.  These tokens should be automatically included as part of the TokenReplace process inthe SPA module.    h2. Conversation  The token creation needs to occur in server-side code.  This can be done in the "BusinessController" as that is a defined location for every module.    If we define a new interface, then module developers can return a dictionary<string, IPropertyAccess> that contains the tokens.  We should include the page and modulecontext when calling the interface.      h2. Confirmation  This feature should also include a sample implementation in the Dynamic Content Type Manager so that we can verify the implementation and show users how it can be used in their own modules.
Answer: 21260.0

User story: "I think the Dynamic Content Viewer module needs to implement {{IPortable}}, so that it can be part of page and site templates, maintaining a copy of its content."
Answer: 16013.0

User story: h2. Card  As an user, I want to have display/view templates for all of the default installed content types.       h2. Conversation  We will need a "layout" for the Employee and Product Content Types      h2. Confirmation
Answer: 184.0

User story: "h2. Card As a developer, I want to be able to create a content field which is a list of elements of a specified Content Type ( List<T> ).   h2. Conversation The list should mirror the behavior of a generic list in that all elements of the list must be the same type.  A list can contain either a Content Type or a Data Type (i.e. you don't have to create a 1 field data type to create a List<HTML>).  A list cannot contain a base type.   h2. Confirmation"
Answer: 360.0

User story: "h2. Card As a developer, I want to be able to create field which is a reference to another Content Type.   h2. Conversation There will not be any separate UI stories.  Cascading menu for snippet insertion context menu.  h2. Confirmation "
Answer: 361.0

User story: "The only type of editor available for editing text is a simple text box.  In order to provide a richer experience Markdown and Rich Text Editors will be added."
Answer: 1353.0

User story: "h2. Card DNN 5 introduced a new OPML feed viewer.  This module has not been installed in the platform since DNN 7 however there is still a lot of code related to this feature.  This feature should be removed from the platform.  There is no requirement to extract this into a separate module.   h2. Conversation The following code/folders should be removed: * \Website\desktopmodules\admin\solutions\ * \DNN Platform\Library\WebControls\FeedBrowser.cs * \Website\Resources\FeedBrowser\  h2. Confirmation All related Jira items should be marked as won't fix.  NOTE: This is technically a BREAKING CHANGE  "
Answer: 7270.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 What's New module is used to display the change log for DNN releases. The core platform no longer maintains the change long in the What's New module and uses the Getting Started feature instead. The What's New module should be deleted.  This module does not have it's own API or database structures so there is no backend to consider.        h2. Confirmation  In installed site (on the file system), there should be no more "DesktopModules/Admin/WhatsNew" folder (this is for both new installs and upgrades)  
Answer: 7275.0

User story: "h2. Card  The Content List module is used to display content related to a particular tag. This module was originally created as part of the old search solution. The Content List module should be deleted. No forge project is needed for this module.    h2. Conversation      h2. Confirmation  All related Jira items should be marked as won't fix."
Answer: 7278.0

User story: "h2. Card As a super-user, when I create a new portal, I want the system to use a portal template, the admin template and the list of module defined Admin/Host pages to create the new portal.  h2. Conversation If a developer has defined an Admin/Host page in their module manifest, then this information should be used to generate the appropriate pages in any portals that are created after the module is installed.  h2. Confirmation  "
Answer: 44.0

User story: "h2. Card As an super-user, I would like to be able to set upload permissions on file-types.  I should be able to delegate management of individual file types to administrators and lock other file types to only be manageable by super-users.  As an administrator, I want to be able to assign upload permissions to users or roles for file-types which have been delegated by a super-user.   h2. Conversation The system should come with a set of pre-defined file extensions as defined by our current Host Extensions list.  All file types will initially be manageable by super-users with the exception of the following types: jpg, jpeg, mpg, mpeg, mp4, wmv, mov, gif, png, svg, doc, docx, ppt, pptx, xls, xlsx, pdf, txt, xml.  The image and movie file types (jpg, jpeg, mpg, mpeg, mp4, wmv, mov, gif, png) will have an initial permission which includes the registered user role.  h2. Confirmation This should be built as a SPA module."
Answer: 36085.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 As a module developer, I want to be able to automatically create an admin or host tab during module installation and have the module automatically added to that page.  h2. Conversation The developer should be able to use the DNN manifest to automatically create the appropriate page.  Page permissions should be automatically set based on the menu and should not require configuration in the manifest. The module should be able to set a flag to determine if the page is displayed in the common or advanced settings sections of the Admin/Host menu.  IF an admin page is defined, then it should be created for all portals in the current implementation.  The manifest logic should detect if the page already exists and if the module already exists on the page.  h2. Confirmation Uninstall of the module should delete the associated page if this is the only module on the page.  This will require modifying all of the existing Admin Modules which have already been packaged."
Answer: 125.0

User story: "h2. Card  The Configuration Manager is used for managing configuration files for a DNN installation. The Configuration Manager is just a UI that exists over the top of the core platform APIs.  The UI components should be extracted into a separate module, however the underlying public API and data components should remain part of the platform.    h2. Conversation  This initial conversion effort is only focused on conversion to a module and shall not include conversion to a MVC or SPA module.    h2. Confirmation  "
Answer: 771.0

User story: "h2. Card  The SQL Module is used for executing SQL queries against the DNN database. The SQL Module is just a UI that exists over the top of the core platform APIs.  The UI components should be extracted into a separate module, however the underlying public API and data components should remain part of the platform. All functionality for saving or loading queries should be included as part of the module and is not considered part of the public API.    h2. Conversation  This initial conversion effort is only focused on conversion to a module and shall not include conversion to a MVC or SPA module.    h2. Confirmation  "
Answer: 771.0

User story: "The Professional Preview module is no longer used in the DNN platform.  This module should be removed from the platform."
Answer: 770.0

User story: "h2. Card The Module Creator is used for building simple modules for DNN. The Module Creator was originally a standalone module.  The UI components should be extracted into a separate module, including the underlying APIs and database components.  h2. Conversation This initial conversion effort is only focused on conversion to a module and shall not include conversion to a MVC or SPA module.  h2. Confirmation "
Answer: 769.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 Dashboard is an extensible module that is used for displaying important information a site. All Dashboard related APIs and database objects should be included as part of the module and should not remain in the DNN platform.    h2. Conversation  This initial conversion effort is only focused on conversion to a module and shall not include conversion to a MVC or SPA module.    The API namespaces should be updated to match the module API.    h2. Confirmation    Note: This a BREAKING CHANGE."
Answer: 769.0

User story: "h2. Card The Console module is used for displaying multiple page icons on a single page.  It is intended as a navigation aid for the host and admin menus. The UI components and all API and database artifacts should be extracted into a separate module.  h2. Conversation This initial conversion effort is only focused on conversion to a module and shall not include conversion to a MVC or SPA module.  This should be marked as a system module.  h2. Confirmation  "
Answer: 768.0

User story: "h2. Card  The Vendors Module is used for managing vendors and banners within DNN. The vendors and banners modules, APIs and database structures should be removed from the core platform and extracted into a standalone solution consisting of the Vendors module and a Banners module.  The Banners module will have a dependency on the Vendors module.  The vendors module should create a page on the Admin menu when installed.      h2. Conversation  This initial conversion effort is only focused on conversion to a module and shall not include conversion to a MVC or SPA module.    This module will move to a separate GitHub project in the github.com/dnncommunity organization.  We can drop stored procedures, but should not remove the tables in the core platform.  Install of this module should check to ensure the table is not dropped.    h2. Confirmation    This module will no longer be installed in new installs and this will also be removed from the Admin and Host menus in upgrade scenarios. This means completion of this task should remove the extension and any pages it automatically created.   As part of this, the resulting module should also live in a new github repository here: https://github.com/DNNCommunity/DNN.Vendors    Note: This is a BREAKING CHANGE"
Answer: 763.0