Modern Requirements4TFS 2018 Release Notes

Transcription

1 Modern Requirements4TFS 2018 Release Notes Modern Requirements 3/7/2018

2 Table of Contents 1. INTRODUCTION SYSTEM REQUIREMENTS APPLICATION SETUP... 3 GENERAL FEATURES ENHANCEMENT BUG FIXES... 4 SMART DOCS FEATURES... 5 ALICE (BOT) FEATURES... 6 SMART NOTE FEATURES BUG FIXES... 7 ADVANCED REPORTING FEATURES BUG FIXES... 8 SMART REPORT FEATURES ENHANCEMENTS BUG FIXES... 9 REVIEW MANAGEMENT FEATURES ENHANCEMENTS BUG FIXES BASELINE FEATURES ENHANCEMENTS BUG FIXES TRACE ANALYSIS FEATURES: ENHANCEMENT: BUG FIXES Modern Requirements Page 1 of 18

3 FAQ BUG FIXES DIAGRAM FEATURES BUG FIXES SIMULATION BUG FIXES USE CASE EDITOR BUG FIXES EMBEDDED VERSION FEATURES BUG FIXES Modern Requirements Page 2 of 18

4 1. Introduction This document contains the notes for the release of Modern Requirements4TFS. It describes the key features of each module of the Modern Requirements4TFS application, such as Impact Analysis, Diagram, Mock-up, Use case, Review management, Baseline, Trace analysis and SmartOffice Library. 2. System requirements Software requirements 1. Operating system: Windows 10, 8.1, 8, 7, Windows Server 2012 and 2008 R2 2. Browser: Internet Explorer 10 or above, Google Chrome and Mozilla Firefox or above 3. Screen resolution: 1280x960 or above 4. IIS 7 or above 5. Microsoft.NET Framework 4.5 or above 6. ASP.NET 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 4 GB of memory is required, but even higher memory is required if executing TFS work item queries greater than 100, Hard drive space of 200 MB. For Redis installation: According to Modern Requirements4TFS, approx. memory usage per user is KB ( 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. 3. Application setup Refer to the Modern Requirements4TFS Installation Guide.docx for installing the application Modern Requirements Page 3 of 18

5 General 1. Dirty flag support: This feature provides users with the capability of receiving alerts on TFS work items when the defined condition is met. The alert appears in the form of a raised red flag whenever a certain condition becomes true in TFS. Users can put a check on the suspected field of any work item type and define pre-state conditions for it. As soon as the system finds a work item in a pre-state condition, it will look for a modification of the suspected field. If any suspected fields get modified, the system will mark associated work items with a flag called Dirty. 2. Multilingual Support: Modern Requirements4TFS now supports several languages, such as Thai, Chinese and Russian on user inputs. 3. Work item as hyperlink on Grid: Users can now open work items in TFS window on doing mouse hover and clicking work item title in the Grid. 2. Enhancement 1. Select Query drop down: Now users can efficiently select a large number of query data under the selected project. 3. Bug fixes 1. Continuous loading appearing on switching among the teams and projects, or on connecting multi projects and teams on the same browser Modern Requirements Page 4 of 18

6 SmartDocs 1. Insert work item: Users can add existing work item(s) using this option. 2. Smart Editor: This feature provides advance editing options for all rich text fields of selected work items. i. Text editing options: Users can use rich text features for text editing including formatting options etc. All these changes done in Smart Editor will be reflected on the Smart Document grid as soon as the user closes it. ii. Table editing options: Users can add tables in accordance with the requirement using advance table operations in Smart Editor; advance table formatting options are also provided. iii. Refresh: Users can view recent changes made on TFS in rich text field of work items by clicking Refresh on the Smart Editor grid. 3. Show ID: Users can set the On or Off ID column option to show or hide the ID column on the SmartDoc grid. 4. Show description: Users can set the On or Off value for the Description option to display or hide work item s description on the SmartDoc grid. 5. Create custom templates: Users can create their own custom templates and save them in a project by selecting the option Save as Template from the grid toolbar. These templates can be used later by any user who s accessing the application from the same service and server. 6. Save as Template: Users can now save any smart document along with its formatting etc. in form of smart doc template and can reuse it from My Templates category. 7. Sample templates: To help users, some pre-defined templates compatible with out ofthe-box process templates are packaged in the application such as Scrum, Agile, CMMI and etc. 8. Update template: To update changes in the rule set of the template from which the current Smart Document is derived from or created. 9. Remove: Remove enables users to remove selected work items from the Smart Document. 10. Indent: It enables users to create the selected work item/row as the child work item of the row above. 11. Out dent: It enables users to create the selected work item/row as parent or sibling of the row above. 1. Create Review Request: Users can easily create a new Review using smart Doc work items. 2. Create Baseline: Users can easily create a new Baseline using smart Doc work items. 12. Smart Report: Users can now generate a detailed customized report of work items along with linked work items using Smart Report. It will have the following features: i. Report parts: Users can generate a specific type of report by defining the report structure in an xml form. ii. Style sheets: Users can provide the desired font and layout for any template by uploading their own cascading style sheets. iii. Generate HTML report: Users can generate a detailed report using Smart Report. It enables users to generate an HTML report consisting of all the work items along with its details. iv. Save as Word: Users can convert HTML into a Word file through the Save as Word button. It enables users to make further changes in the document. v. Save as PDF: Users can convert HTML into a PDF file through the Save as PDF button. It enables users to use the document for sharing purposes Modern Requirements Page 5 of 18

7 Alice (BOT) 1. Create chat or conversation: Users can initiate a chat or conversation with Alice by selecting the template supported with their team project from the New option on the left panel. 2. Auto-save: Users can continue its chat with Alice without having the tension of saving it, Alice auto-saves all the conversations in real time. 3. Check in or Check out: Users can check in or check out their chat file whenever required. 4. Discard changes: Users can use this option to undo all changes made following the last checked-in state. 5. Instant Help: Users can receive instant help if they don t understand the question. The I sign with Alice questions provides a short phrase explaining the question and background. 6. Text to voice: Users can now click the microphone icon in the message bar to activate this feature, and Alice will start narrating questions visible in chat. 7. Voice to text: Users can click the microphone icon to activate this feature. This functionality enables users to ask Alice a question through voice, with the answer appearing in the chat window. 8. Context: Users can get the contextual view from this tab for the ongoing conversation in the chat window. 9. Backlog: Alice extracts the data from conversation and makes a backlog of the conversation according to the defined hierarchy in script. Users can view their response or requirement in a backlog view and make modifications, if required. i. Publish: Users can publish data directly from a backlog view and, after publishing the data, respective work item IDs would be displayed in a backlog grid view. 10. Scenarios: This functionality enables users to view their given data or responses in the form of scenarios. 11. Info: It provides information about chat, users and participants. 12. Help: It provides Alice and conversation command help to users Modern Requirements Page 6 of 18

8 Smart Note 1. Create custom templates: Users can create their own custom templates and save them in a project by using the Save as Template option from the grid toolbar. These templates can be used later by any user accessing the application from the same service and server. 2. Save as template: Users can now save any document along with its formatting etc. in the form of a template and later reuse it if needed. 3. Sample templates: To help users, some pre-defined templates are packaged in the application, such as meeting notes, project overview and to-do list, among others. 4. Full screen: Users can have a full-screen view of the Smart Note page by selecting the Full Screen mode button at the toolbar. 5. Insert image: Users can now insert images in a page and can search for images through Bing search and add images to the media library. 6. Dashboard: Users can now access Smart Note features from the application or dashboard. 7. Search file: Users can search for files that exist in a project within the Smart Note module. 8. Discover: Users can view the How-To manual for Smart Note features under the Discover option provided in the module. 9. Insert file: This feature enables users to insert or attach file in the Smart Note page. i. Attach file: Users can attach Word, PDF, Excel and Power Point files. The entire file will be loaded into the Smart Note page and the user can view it as well. ii. Insert file: Users can insert Excel and Power Point files in the Smart Note page. Users will see a thumbnail for such files and can download and save these files to view them. 10. Smart Report: Users can now generate a detailed customized report of work items along with linked work items using Smart Report. The report will have the following features: i. Report parts: Users can generate a specific type of report by defining the report structure in an xml form. ii. iii. Style sheets: Users can provide the desired font and layout for any template by uploading their own cascading style sheets. Generate HTML report: Users can generate a detailed report using Smart Report. It enables users to generate an HTML report consisting of all the work items along with its details. iv. Save as Word: Users can convert an HTML file into a Word file through the Save as Word button. It enables users to make further changes in the document. v. Save as PDF: Users can convert an HTML file into a PDF file through the Save as PDF button. It enables users to use the document for sharing purposes. 2. Bug fixes 1. Continuous loading appearing on file switching. 2. Continuous loading appearing on selecting a file. 3. The title, New File, in the new page pop-up has been replaced with New Page so the issue has been fixed. 4. The loading icon not appearing when creating a template. 5. Background and font colors not changing on applying a different color from the tool bar. 6. The container not resizing the w.r.t image size properly. 7. On TFS 2015/2013, warning message not appearing on attaching files bigger than 4MB Modern Requirements Page 7 of 18

9 Advanced reporting 1. Insert header or footer: Users can now insert headers or footers on any generated output data while performing save as Word. Users can upload their own templates with the desired header or footer and generate documents accordingly. 2. Insert table of contents: Users can now insert a table of contents on any generated output data while performing save as Word. Users can upload their own templates with the desired table of contents and generate documents accordingly. 3. IntelliSense on select report: Users can now search any report part from the drop down menu through IntelliSense. This feature makes it easy for users to view searched results and select the desired file. 2. Bug fixes 1. A generated report not being properly formatted. 2. The wrong URL being displayed while the selection is on the Reporting tab and root file is selected. Also, the static page not being shown. 3. The screen getting stuck when the user collapses the left panel after creating a new report. 4. A report not being generated after changing the formatting of Smart Part. 5. On [VSO/Team], user is unable to open a report file with a message appearing in a particular scenario. 6. [Firefox] Data still being displayed on the Result tab while the query is deleted from the Editor tab. 7. [IE] The font family of Smart Part in Internet Explorer not appearing the same as in Google Chrome. 8. Continuous loading being displayed when F5 and Ctrl are pressed. 9. Heading formatting not being applied on sample templates headings in the Editor tab. 10. Changes in formatting applied on a single line being applied on the whole paragraph. 11. OK button shown enable without inserting any query in the insert Smart part window. 12. Continuous loading being displayed when applying the paragraph format on the text written above Smart Part. 13. The OK button not being displayed in upper case letters on the Create Table Wizard window. 14. The shared query folder being selected and inserted in Smart Part. 15. The Progress bar not being displayed when switching between two reports containing large amounts of data. 16. [Volume] Not being able to generate a report containing 5,000 work items. 17. ID hyperlink does not navigate to the correct URL when open from save as word document Modern Requirements Page 8 of 18

10 Smart Report 1. Insert header or footer: Users can now insert headers or footers on any generated output data while performing save as Word. Users can upload their own templates with the desired headers or footers and generate documents accordingly. 2. Insert table of contents: Users can now insert a table of contents on any generated output data while performing save as Word. Users can upload their own templates with the desired table of contents and generate documents accordingly. 3. IntelliSense on report part: Users can now search any report part from the drop down through IntelliSense. This functionality makes it easy for users to view searched results and select the desired file. 4. Generate shared steps work item: Users can now generate a Smart Report with the shared steps work item type, including action and expected result. 2. Enhancements 1. Show currently selected report part: Users can now view the file on the Report tab that is simultaneously being used on the Designer tab. This makes it easy for users to generate files while working back and forth without selecting the file again and again. 2. Style sheet on label: Users can now apply the required style sheet on the field and label both. 3. Bug fixes 1. The OK button being disabled on performing Save as in a particular scenario. 2. Empty space being shown on scroll down in the Designer tab. 3. Extra spacing appearing between the report part and the style sheet drop down. 4. The tool tip not being displayed on the icon appearing on the sort by/group by options. 5. The table width not being set only once for the "Form as table" section type. 6. The style sheet with the specific report part not retaining on the switching of tabs. 7. The "Save" toolbar button remaining disabled while creating a new file Modern Requirements Page 9 of 18

11 Review management 1. Review filter: Users can apply a filter to view the relevant reviews while connected to a specific team context. 2. Reapprove or reject on review work item: Now users can change the state (reapprove or reject) of a work item after approving or rejecting it until the review is closed. In case a review is reopened after extending the due date, then users can change the state of a work item. 2. Enhancements 1. Area path: Now users can view all reviews created under the project or in project teams while connected to a project. Also, if users are connected to a specific team, they can view only the reviews created under that team. 2. Review audit report: Now users can view the cumulative status of all work items in a review. The review includes the number of items that have been approved, rejected and how many contain no response as provided by any user. 3. Baseline from review: Now users will be asked to specify the type of work item revision on which they want to create a baseline. These can be existing revisions (a revision on which the review is requested), approved or rejected revisions (revision on which the work item is approved or rejected) or the latest revision at server. 4. Due date: Now the review creator will be able to extend or change the due date of a review, which is in an open state as well as in a closed state from the Details tab. Also, the due date cannot be set to the past date. 5. Rules configuration settings: Now users can approve all or reject all on work items in a review if Approve as packaged value is true in the web configuration. 6. Compare pop-up: Users can now view work item properties and their comparison status through the Compare modeless pop-up. Only those properties stated in the user settings file will be visible on the compare pop-up. In order to view all properties, users can select Show all fields and choose On. 7. Compare work item properties: Users can now view an accumulated result through the Compare tab as well, after comparing two HTML properties other than the description. 8. Add URL hyperlink in work item: Upon creation, URL of a created baseline will be added in each work item as a hyperlink if the user selects that given option. Also users can view the details of a work item, i.e. which revision of the item is part of which baseline in the Comment field of the added hyperlink. 3. Bug fixes 1. Review vanishing from the connected project on browser refresh when review is created on the team s area path. 2. Approve or Reject buttons being enabled when user Create Review from an existing review with Approve as Package in a given scenario. 3. Review not being opened by the link when user create review request from project to team. 4. The response graph displaying wrong results when users choose to approve and reject a work item in Review. 5. Review disappearing when a review is created on the user-defined area path Modern Requirements Page 10 of 18

12 6. The Review completed button appearing disabled following the Create Review request from the new or review from review [Git]. 7. The Response time field appearing empty in the review audit report when users choose to approve all or reject all. 8. The review being shown in the Active Reviews folder when opened by the link after the review was closed manually. 9. The Incorrect password message appearing on clicking approve or Reject on review work items; with the Ask User password checkbox enabled. 10. The audit report displaying reviewers as approvers in a particular scenario. 11. [Git]The review from baseline displaying a wrong message and not showing in the folder explorer until clicking Refresh. 12. On clicking Create Review from review, work items not being visible while the count is displayed. 13. Approver/Reviewer name disappear from details tab when browser window is resized Modern Requirements Page 11 of 18

13 Baseline 3. Create baseline from baseline: Users can initiate a new baseline from an existing baseline on the same work item revisions, or the latest revision. Users can also add more work items or delete items while creating them from an existing baseline. 4. Merge baseline: Users can now perform the merge baseline functionality on copied baselines. Users can make changes in one baseline and merge into the second baseline according to the configuration set in the merge window. 5. Comparison status based on configured fields: On compare baseline, comparison status on the grid will display only the change if any change occurs in those properties stated in the user settings file. 6. Source or target baseline information: Users can view information such as name, created by, created date of both target and source baselines in the Details tab. To navigate to the respective baseline, users can click the Open Baseline link. 2. Enhancements 1. Add URL hyperlink in work item: Upon creation, URL of a created baseline will be added in each work item as a hyperlink if the user selects this given option. Also, users can view the details of a work item, such as which revision of the item is a part of which baseline in the Comment field of the added hyperlink. 2. Compare pop-up: Users can now view work item properties and the field comparison status through the Compare modeless pop-up. Only those properties stated in the user settings file will be visible on the Compare pop-up. In order to view all properties, users can select On under Show all fields. 3. Compare work item properties: Users can now view an accumulated result in the Compare tab as well, after comparing two HTML properties other than the description. 4. Add Parent ID: Users can insert parent work item id under options tab while doing Copy/Reuse baseline. All the work items will be created under the given parent id after copy/reuse. 3. Bug fixes 1. [Random] Work item not coming in grid when creating a baseline from baseline. 2. The following message, "Some error occurred in creating," appearing on the copy baseline to the team of the connected project Modern Requirements Page 12 of 18

14 Trace analysis : 1. Horizontal Matrix i. Query type: Users can now generate a horizontal traceability matrix by selecting the query type option in the Editor tab. The output generated consists of only the work items existing in the selected query. Export to Excel: Users can generate export to Excel on output data. Smart Report: Users can generate a Smart Report on output data. ii. Show merged view: In order to view all directly linked work items in one column, users can select on in a merged view. 2. Intersection Matrix i. Show work items with links: Users can now view work items that link as required by selecting one of the values under the Show drop down. Users can view work items with links or no links in order to track missing requirements. 2. Enhancement: 1. HTML support in export to Excel: Now users can properly view rich text content, such as bulleting and numbering, among others, in export to Excel. 3. Bug fixes 1. Clicking "Any" from link type drop down not selecting all link types in the drop down. 2. Link type not appearing unselected in a particular scenario. 3. "Selected query does not exist on server message appearing on the Editor tab Modern Requirements Page 13 of 18

15 1. Bug fixes FAQ 1. The title in the new topic pop-up not appearing as New Topic but as New File. 2. The question being deleted when deleting an answer work item from TFS. 3. In new question pop-up, ok button not appearing as OK Modern Requirements Page 14 of 18

16 Diagram 1. New stencils: i. Cause and effect diagrams: Users can now create cause and effect diagrams, also known as fishbone diagrams that help users categorize potential causes of a problem in order to identify its root causes. ii. Context diagrams: Users can now create context diagrams, making it easy for them to understand the context of the entity being examined. 2. Bug fixes 1. The Business Object Model size changing when drag and drop is performed on layout. 2. The diagram changes its position on resizing shape once user switch from Analysis to Model tab. 3. The drill down button disappearing from the toolbar on deleting link. 4. The same path and test case steps showing different ratings. 5. The Ok in alert message of the Analysis tab not appearing in capital letters. 6. The space below the OK button of the drill down link window not appearing. 7. Unable to resize vertical swim lane on switching between files. 8. Wrong rating is shown for test case paths and keeps on increasing on tab or file switching Modern Requirements Page 15 of 18

17 Simulation 1. Bug fixes 1. The feedback request window appearing cut off with the cross icon not being displayed. 2. The Send button not being disabled when the stakeholder is not selected in the feedback request window Modern Requirements Page 16 of 18

18 1. Bug fixes Use case editor 1. [IE 11] The tool bar options not working under the Details tab when the focus is not in Editor. 2. [IE 11] The position of the mouse cursor moving above the main success scenario. 3. [Chrome]Text inserted on top when clicking call use case button Modern Requirements Page 17 of 18

19 Embedded version 1. Admin Panel: The Modern Requirements4TFS settings are now embedded into the VSTS server at collection level. Users can find the Modern Requirements4TFS tab under the VSTS settings page by navigating through the settings option from TFS. Under this tab, the following sub hubs are available: i. General: Users can now add the GIT project name along with the Repository name and directly save changes under the General tab. ii. Review: All user-based settings, such as Review Meta information, work item display fields, Review response actions and others for review can be defined and saved under the Review tab. iii. Baseline: All user-based settings, such as work item display fields for view or compare baseline and settings for copy baseline of a baseline can be defined and saved under the Baseline tab. 2. Reuse work item(s): Users can now select single or multiple work items and reuse them within the same or different project. On Reuse, a copy of all selected work items is created along with the properties. 2. Bug fixes 1. Correct formatting not showing when generating a report with multiple smart parts. 2. Audit report not generating in a particular scenario. 3. Date Time not properly appearing according to the current system time zone in the Discussion panel. 4. UI-related issues appearing in different modules for TFS Review from review not displaying select reviewers and the other data fields on selecting multiple reviewers Modern Requirements Page 18 of 18