Develop module

navigate the view of your develop environments, to ascertain issues and defects for applications, technical services, and cloud services for supported providers enables observable performance of the devops lifecycle to enable continual finetuning of each devops phase the developer module reports critical developer activity as it relates to the performance of your team developer module composition in this dashboard, data can be filtered by two criteria dashboards select a dashboard to view development data specific to that dashboard applications comprehend cloud services' issues and health, such as cost $asset management or enterprise marketplace note depending on your selections from these filters, the data displayed in the widgets varies some widgets may show a "no data available" the message, which means no recent data is available for your selection the develop dashboard displays data in multiple graphs and a table view table that allows a view of critical components of the development phase development activity a graph shows all activities per calendar month, issues (brown), and defects (aqua green) applications a horizontal bar graph displays the top five applications with the highest updated defects/issues technical services a table views data for each supported technical service and includes a drill down feature that enables a detailed view of each instance download reports the develop dashboard supports a reporting feature to download an open issues report this enables users to download data in excel format so that users can download and sent reports to those who do not have access to di or want to perform additional analysis on the consolidated dataset to download a report click the download button, located in the upper right corner of the dashboard in accordance with the following procedure click download to display the download dialog enter a name in the your file name field all other fields are pre populated click download to download the report or cancel to cancel the download widgets the develop dashboard displays two widgets that visually represent development activities and applications development activity the development activity widget allows you to view defects or issues based on the following criteria the displayed data is governed by the date range selected from the timeframe in the header, select duration , default 7 days dashboard filter applications filter defect or issues category, dropdown menu located on the right above the displayed widget for each category there are three status option to display data in the widget new updated closed the development activity widget presents two axes that indicate the activities within a specified timeframe in which the defects and issues occurred the x axis (number of activities) the x axis corresponds to the dates within the activity's timeframe the y axis (timeline) the y axis corresponds to the number of new, updated or closed defects or issues for the selected timeframe applications the top five applications in terms of defects or issues are represented in this graph the top 5 applications with the most updated defects are displayed by default, but the category and type switches can be altered only the top 5 non zero applications are shown in this graph when a user selects one of the applications on the graph, the data for that application is automatically filtered and displayed in the technical service table defects and issues status the development activity widget presents six permutations depending on whether you select the defects or issues category, and which of the three status condition you select new , updated or closed the consult the following list for details new defects provides a view of bugs discovery rate this trend helps the development manager to understand the growth of new bugs, which is critical for new features a spike might indicate a problematic release or a specific area of the application that needs attention if the trend shows a consistent number of new bugs, it might indicate that the team is not addressing the root causes of these bugs updated defects displays a visibility of bugs that are being processed these are the bugs that are in different categories like active or test etc comparing different applications will help development managers to identify which team is focusing on working on bugs closed defects displays bugs that have been closed during the selected duration the development manager can relate the trend of closed bugs with each release if the number of closed defects increases after a release, it might indicate an initial instability that is being addressed conversely, a steady decline in closed defects over time can suggest that the application is becoming more stable by comparing the trend of closed defects with the trend of new defects, you can manage your defect backlog more effectively a higher rate of closure compared to new defects indicates a reducing backlog new issues the trend in the bottom right captures the information of the newly created epics and user stories an ideal way to visualize this is monthly depending on the sprint planning activities, usually this should be higher at the sprint planning phase this can be correlated with the sprint schedule updated issues displays those issues that have changed its status these issues can be user epics and user stories that the engineering team is currently processing this should again follow the sprint cycle as it should reduce the time sprint ends the right graph (applications) gives an application level breakup, which should also account to the similar split in the team structure the development manager can improve the team allocation based on the updated issues of the applications closed issues displays the rate of closing epics and user stories consistent closure of features indicates a well functioning team, while fluctuations might highlight areas that need attention or improvement technical services table the technical service table view is located at the bottom of the develop dashboard, which provides technical service development data in a tabular form and enables a detailed view of each technical service the table shows different projects which are configured in in this case the data is configured at fpl com project and all the information with respect to defects and issues are captured information about the source code management tool is captured in the table currently, it is configured at the different project repos being configured as a technical service and mapped to different applications the active pull request (pr) is an important matrix, which gives the development manager a view on the code approval policy a high number of active prs should be alarming for the development manager and then he/she shall go into the details to identify why there are these many pr which are pending to be merged note technical services are a micro service that is analogous this is the most granular degree of granularity repos in git and bitbucket and projects in jira are mapped only technical services with developments in the recent 6 months will be displayed each row in the table displays information for a specific technical service, separated by columns of information type technical service the name of the micro technical service within the larger application application the application's name typically comprises multiple micro technical services new defects the number of new defects opened against the technical service during the selected time updated defects the number of open defects against the technical service that have been updated during the selected time new issues the number of new issues opened against the technical service during the selected time updated issues the number of open issues against the technical service was updated during the selected time active pr active pull requests tool engine the name of the technical service that produced the issue or defect ticket, such as git attention the development details table displays all data regarding the timeframe selected all the columns in this table can be sorted above this table, you will find a search box that allows searching technical services by name and a settings an icon allows changing the table settings to show or hide pre selected columns at the far right of each table, is an overflow menu icon that enables a detailed view of the issue described in that row click view details to review the following defect and issue summary this comparison displays the trend of new vs updated vs closed bugs during a specific period of time by comparing the trend of closed defects with the trend of new defects, you can manage your defect backlog more effectively a higher rate of closure compared to new defects indicates a reducing backlog similarly, it also compares the trend of issues together for new vs updated vs closed detailed view of issues and defects above the defects and issues graph, is a defects summary and an issues summary containing the number of anomalies (new, updated and closed defects and issues) each number is a clickable hyperlink that displays a drill down view of that item tag searches also available pull request and commit these two charts capture the information on the trend of how commits and pull requests are progressing this data is captured from github for the repo you have selected in the technical services page the metrics illustrate the development activity within the specified repository the closed trend indicates how many pull requests have been approved and merged into the main branch ideally, there should be a balanced flow between the number of new pull requests and the number of closed pull requests the commit trend reflects the level of development activity in the repository regular commits contribute to effective branch management, keeping the codebase up to date and reducing integration conflicts details of pull request and contributors the details page of a pull request provides an overview of the number of open prs for the selected repository the updated date indicates the age of each pr, allowing managers to see which parts of the codebase are pending review and for how long this capability offers insight into the review efficiency of the application the pr link directs to the github page, where development managers can monitor and review progress and identify any delays if the number of open prs is high for a specific repository, appropriate intervention might be necessary to prevent delays contributor details are specific to the selected repository and time frame this information shows how much a developer has contributed in terms of lines of code changed and the number of commits it also indicates the size of prs, which should be managed to ensure an effective review process the table view also supports detailed views for each technical service to access details for a specific technical service, select the overflow menu to the far right of the table and select view details for more information, see develop dashboard table view docid\ ya g3jglshk6qutimkxbz develop dashboard table view docid\ ya g3jglshk6qutimkxbz view a tabular presentation of develop details