Modern Requirements4TFS 2018 Update 1 Release Notes Modern Requirements 6/22/2018
Table of Contents 1. INTRODUCTION... 3 2. SYSTEM REQUIREMENTS... 3 3. APPLICATION SETUP... 3 GENERAL... 4 1. FEATURES... 4 2. ENHANCEMENT... 4 3. BUG FIXES... 4 ADMIN PANEL... 5 1. FEATURES... 5 2. BUG FIXES... 5 SMART DOCS... 6 1. FEATURES... 6 2. BUG FIXES... 6 ALICE (BOT)... 7 1. FEATURES... 7 2. BUG FIXES... 7 REVIEW MANAGEMENT... 8 1. ENHANCEMENTS... 8 2. BUG FIXES... 8 BASELINE... 9 1. ENHANCEMENTS... 9 2. BUG FIXES... 9 SMART NOTE... 10 1. BUG FIXES... 10 ADVANCED REPORTING... 11 1. BUG FIXES... 11 SMART REPORT... 12 1. BUG FIXES... 12 TRACE ANALYSIS... 13 1. BUG FIXES... 13 USE CASE EDITOR... 14 2. BUG FIXES... 14 EMBEDDED/VSTS VERSION... 15 1. ENHANCEMENTS... 15 2018 Modern Requirements Page 1 of 20
1. BUG FIXES... 15 MR AGENT... 16 CUSTOM ID... 17 1. FEATURES... 17 DIRTY FLAG... 18 1. FEATURES... 18 MR MAIL SERVICE... 19 1. FEATURES... 19 APPENDIX A: HARDWARE REQUIREMENTS FOR REDIS... 20 2018 Modern Requirements Page 2 of 20
1. Introduction This document contains the notes for the release of Modern Requirements4TFS (MR4TFS). It describes the key features of each module of the Modern Requirements4TFS application, such as Smart Docs, Smart Note, Alice (BOT), FAQ, Diagram, Mock-up, Use case, Review management, Trace Analysis, Baseline, Reporting and Impact Analysis. 2. System requirements Software requirements 1. Operating system: Windows 10, 8.1, 8, 7, Windows Server 2016, 2012 and 2008 R2 2. Browser: Internet Explorer 10 or above, Google Chrome and Mozilla Firefox47.0.1 or above 3. Screen resolution: 1280x960 or above 4. IIS 7 or above 5. Microsoft.NET Framework 4.5 or above 6. ASP.NET 4.5 7. Multilingual support Language pack for IE & Save as Word Please note the following: Both the 32-bit and 64-bit versions of the operating systems are supported. Credentials required for installing Modern Requirements4TFS should have administrator rights on the computer. In other words, users installing Modern Requirements4TFS on their machine should use admin credentials (or credentials that include administrator rights) for proper installation. For regular team projects, the user of a machine on which ModernRequirements4TFS is deployed must have administrative rights on TFS Collection (or added in Application Domain in IIS). Also note that to access GIT-enabled team projects, the logged-in domain user of a machine on which Modern Requirements4TFS is deployed must have authenticated rights on TFS Collection (or added in the application domain in IIS). Hardware requirements 1. At least 12 GB of memory is required, but even more memory is required if executing TFS work item queries greater than 100,000. 2. Hard drive space of 500 MB. 3. Application setup Refer to the Modern Requirements4TFS Installation Guide.docx for installing the application. 2018 Modern Requirements Page 3 of 20
General 1. Features 1. Single Sign-on (SSO): Now single sign-on functionality is supported in MR4TFS. By using this functionality users don t need to enter their credentials every time while accessing the application. It is supported by Team foundation server s 2017 Update 3, 2018 Update 1 and above. 2. Enhancement 1. Performance Optimization: Performance is improved in all modules of MR4TFS. 2. Save as Template: On saving a file as a template, users will be notified to override the template if a template with the same title already exists in the module. It is supported by all modules such as Smart Docs, Smart Note, FAQ, Diagram etc. 3. Bug fixes 1. Different modules are not working when users leave the system in idle state for 45 minutes. 2. Work items are not showing on the Add work items window grid when users click Find. 3. After renaming a TFS project, the user is unable to access previous files that already exist in a project. 4. The same files and folders appearing on two different projects (this happens at random). 2018 Modern Requirements Page 4 of 20
1. Features Admin Panel 1. Dual GIT Repository Support: Now a user is able to see the Git and TFVC projects are listed separately when setting up the Git Repository name from admin panel. This allows users to choose GIT Repo for MR4TFS to use in both cases of source control selection (GIT & TFVC). This way the only repo application will access is the GIT repo assigned to MR4TFS for a given project. 2. Bug fixes 1. User-configured fields for Review and Baseline compare popup are not showing in the admin panel. 2018 Modern Requirements Page 5 of 20
Smart Docs 1. Features 1. Discover: Users can view the How-To manual for Smart Docs features under the Discover option provided in the module. 2. Bug Fixes 1. When users close or cancel the Smart Editor popup window without saving the changes, the confirmation message dialog doesn't show up to get the approval on changes from user. 2. Inability to upload an image to Smart Editor when users log in using their admin credentials. 3. Hand icon appearing on Description/Id label. 4. An error message "An error occurred while processing your request" showing when users open any attached document in Smart Editor. 5. When users open an image from Smart Editor after tab switching, the broken icon appears instead of the correct image. 6. [TFS-2013] Inability to create a file through the specific process template in Smart Docs. 7. A confirmation message being delayed after users close the Smart Editor window. 8. The Save button not appearing disabled when users save text. 9. Previous tab changes being reflected on tab switching. 10. The "Work item updated successfully" message showing when users save an empty title from the Smart Editor. 2018 Modern Requirements Page 6 of 20
Alice (BOT) 1. Features 1. Discover: Users can view the How-To manual for Alice (BOT) features under the Discover option provided in the module. 2. Bug Fixes 1. If a user enters bold text, it is being replaced with HTML tags. 2. If a user enters multiple items by pressing the Shift and Enter keys, the system asks Is there another? 3. When a user types something other than No after Thank you, the Backlog window's grid shrinks in. 4. If the user types No after Thank you, a conversation goes into a continuous loading state. 5. The system supports the Resume on published work items but doesn t allow users to rename or delete work items from the Backlog. 6. If users restart a conversation, the published content should not be removed; rather, unpublished content should be removed. 2018 Modern Requirements Page 7 of 20
1. Enhancements Review Management 1. Unique username in Signature & Audit report: The username by which the user is logged into TFS will show up in the electronic signature at work item level as well as in the Review audit report. 2. Ask for password on approval: If a review initiator checks this property while requesting a review, all assigned approvers can view a dialog of username and password authentication when approving/rejecting work item(s). The username authentication process is applicable for approvers only. 3. Save functionality: A reviewer can submit the remarks on each work item(s) in the form of a reviewed comment by using the Submit Review button. This button is the replacement of a Save icon on the toolbar which was previously used to activate this functionality. 2. Bug fixes 1. The unique identity of the approver is not showing beside the approver s name in the review audit report. 2. By applying the rule Ask the user for a password on approval in a review, if an approver while approving/rejecting a work item, enters an invalid username on first time authentication, Incorrect username error is showing repetitively, even after user has entered the correct username. 2018 Modern Requirements Page 8 of 20
1. Enhancements Baseline 1. Special character support: Added support to enter special characters in the title while creating a new file and folder. 2. Bug fixes 1. Tags field of a work item not showing in a compare dialog. 2. As of date showing a repeated list of work items in the grid and appearing as crossed. 3. The revision date column not sorted correctly on As of Date window. 4. Creating "Review Request" from a baseline showing no response if that baseline contains large data. 5. The Difference Report is sometimes generated in HTML format instead of being generated in a Word document. 6. The Difference Report is sometimes not generated and shows error on generation. 7. The Difference Report doesn t generate if any work item in that baseline is deleted from TFS. 8. While copying the baseline, team project drop-down becomes empty if a user changes the server. 9. Copy baseline from one collection to another collection showing area and iteration path of source project. 2018 Modern Requirements Page 9 of 20
Smart Note 1. Bug fixes 1. When copy pasting any high definition image from any other source into the file, the user is unable to check-in that file. 2. On file check-in, all images are saving in work item description except the images whose width is bigger or equal than 187pixels; and whose height is bigger than 193 pixels. Instead of showing the image the embedded image text is displayed. 3. If the Smart Note page is containing an image that s large in size, that file isn t checking in. 2018 Modern Requirements Page 10 of 20
Advanced Reporting 1. Bug fixes 1. Report generation takes a longer than expected time with 5,000 work items. 2. [IE 11] Smart part changes its position when users insert it after any text. 2018 Modern Requirements Page 11 of 20
Smart Report 1. Bug fixes 1. The multi-line field type of a work item doesn t render proper data as in TFS. 2. A report that includes a table of contents in the selected document template is generating in HTML format from Save as word. 2018 Modern Requirements Page 12 of 20
Trace Analysis 1. Bug fixes 1. In Horizontal Matrix query type, test result data and steps are not populating. 2. In Horizontal traceability query type and the selected custom columns are not populating when users select a single row from the editor. 3. Work items don t appear in the hierarchy if the same work item also exists on the root level. 2018 Modern Requirements Page 13 of 20
Use case Editor 2. Bug fixes 1. If a user renames a file in mockup and use case module the Object text appears in file header instead of the file name. 2018 Modern Requirements Page 14 of 20
1. Enhancements Embedded/VSTS version 1. Performance is optimized for tab switching. 1. Bug fixes 1. When the user refreshes the browser window, the Review hub navigates the user to the Licensing hub. 2. Test results not showing in Trace Analysis and Queries tabs when the system generates a Smart Report in VSTS. 3. The inserted file is not downloading on file/tab switching in Smart Note. 4. In VSTS, few issues exist in Smart Note, Impact Analyzer and Smart Report when adding image attachments. 5. In MR4TFS admin tabs the yellow bar pops up sometimes as a result of performance issues on VSTS. 6. When users click, enter or change the format from the drop-down in advanced reports, the Object object text is shown in the drop-down in VSTS. 7. Different modules not working when users leave the system in idle state. 8. Images in work item description not showing in Impact Analyzer or when generating a Smart Report. 9. A user is unable to close the Reuse work item and Smart Editor popup window when clicking the Close icon. 10. The license page is not opening while a user is being activated. 11. Continuous loading starts when users access any module tab if default GIT Repository is set to "MR4TFS" from IIS manager. 2018 Modern Requirements Page 15 of 20
MR Agent MR Agent is a module of Modern Requirements4TFS (MR4TFS) containing three components. It works as a framework that handles its components information centrally; it also handles the registration processes required on the server for the components. You can think of MR Agent as a background service that acts as an intermediary, managing all queries and transactions of these components between TFS server and MR4TS. Custom ID. Dirty Flag. MR Mail Service. 2018 Modern Requirements Page 16 of 20
Custom ID Custom ID is a component that enables users to set or assign a customized ID to a TFS work item. Users can configure a required field along with the required formatting for Custom ID. Usually, corporations and enterprises have their own standard IDs. For different projects, different formats representing their type and project names are considered in assigning IDs. Custom ID can take care of all your needs in the area of ID customization. 1. Features 1. Customize new or existing TFS work item IDs: Simply configure Custom ID on the required collection and apply it to existing work items. The system will assign a customized ID in accordance with the configuration to all existing work items. 2. Auto identification and Apply for new projects: Custom ID can be configured on a Collection with a feature of auto sync, which periodically checks for the creation of a new team project on a configured collection. As soon as it identifies that a new team project is created, it will apply a Custom ID field in accordance with the configuration on it. 2018 Modern Requirements Page 17 of 20
Dirty Flag Dirty Flag guarantees that all stakeholders understand the effect of a change made by any team member. This helps keep intact the context of change on associated items as well. Users can audit changes made throughout the project to warn the group when changes that can affect their associated teams. It also provides a comparison between a work item s previous state (on which the item has been modified) and the current (latest) state in TFS. 1. Features 1. Identify modifications on UI: Dirty Flag adds a tag to the target work item so that users can have an extra step of visibility. Users can search all tagged work items to identify all modified work items. Rules can be applied to identify certain conditions including: Work item type, state, key properties, etc., and only work items fulfilling those rules will be tagged as dirty. Users can get more information through details in the Suspect tab of a work item or its details in the history field. 2. Clear status after review: Users who review a dirty flagged work item can clear its flag so that its indication flag could be removed. On clearing a flag from the work item, its associated tag is also removed automatically. Users can remove all flags at once instead of removing them one by one. 2018 Modern Requirements Page 18 of 20
MR Mail Service MR Mail service helps users to instantiate requirements or discussions in TFS from email. In most cases, requirements or important discussions regarding an existing requirement are carried out on emails. MR Mail manages all replies in the work item discussion field. This enables users to get complete details, reviews and feedback on a particular requirement in the same place 1. Features 1. Register email addresses: Users can create a work item of any type for a discussion started on email. This can include initial requirements or a module description, etc. Alternatively, MR Mail enables users to start a new conversation on TFS through email; similarly, a discussion could be started on an existing work item ID. 2. Email-chain management: When sent, discussion or requirement details usually require a review or feedback, causing an email chain to start. MR Mail maintains this discussion in TFS in the history field of a work item so that replies on any discussion are also available on the TFS server for review and record. 2018 Modern Requirements Page 19 of 20
Appendix A: Hardware Requirements for Redis According to Modern Requirements4TFS, approx. memory usage per user is 477.8495 KB (0.4666 MB). Maximum hard drive space required is 1.5 * (memory size). For instance, in case of an 8 GB RAM, maximum hard drive space occupied by Redis would be 12 GB. 2018 Modern Requirements Page 20 of 20