Release v1.5.0 · erda-project/erda

Erda v1.5 is officially released with a total of 202 new features and improvements, such as Gantt chart, a powerful tool for task planning in project management, and efficiency measure of requirements and tasks, allowing you to have a clearer picture of the progress and risks of iteration. For microservice governance, Erda supports new topology for services and flame graph for tracing analysis, making it easier for you to understand the overall service architecture of the product with cool visual effects.
For more information, please get the latest version and gain new experiences of Erda.
Thanks again to each of you who contributes to Erda. We will pay attention to and adopt suggestions from the community continuously, to promote the further development of Erda. Look forward to hearing from you!

Exciting New Features 🎉

The following will introduce some key features of the new version in details.

1. R&D efficiency measure - Requirement and task analysis

Based on the efficiency measure of version 1.4, the new version supports requirement and task analysis, to help you analyze progress, risks and issue workflow via burn down chart and cumulative flow diagram.The burn down chart shows the possible problems of your team by iteration filtering. Through the chart exception or deviation from the ideal curve, you can see problems such as progress ahead or behind, task overloaded or unsaturated, requirement granularity too low, task estimated inaccurately, requirement changes and progress updated untimely.

Path: DevOps platform > (Select project) > Projects > Efficiency measure

The cumulative flow diagram helps you view and analyze the cycle time, throughput rate and predicted release date of iterations of requirements and tasks in each workflow status.

2. Project plan management - Gantt chart

In project management, it is essential to make plans, manage task distribution and follow tasks. For this reason, Erda supports Gantt chart in this version, which allows team managers to have a global view on task distribution, allocate and manage tasks reasonably, and view the cost of each issue clearly, and team members to view the distribution and due status of their tasks conveniently. In addition, the chart shows the progress and risks of tasks that may affect others, and tells the reason why some tasks are delayed.

Path: DevOps platform > (Select project) > Projects > Project collaboration

3. Microservice governance - New topology

Erda supports a new topology of services and dependencies on the microservice platform. The platform automatically discovers and analyzes the upstream and downstream dependencies of services, and generates a service topology, making it easier for you to understand the overall service architecture of the product, and query service performance bottlenecks, error hotspots, and abnormal service dependencies.

Path: Microservice platform > (Select project) > Topology

4. Tracing analysis - Flame graph

The flame graph is created by Brendan Gregg, an expert in computing performance. Unlike other profiling methods, the flame graph takes a global view of time distribution, listing all call stacks that can lead to performance bottlenecks.Through the flame graph, you can clearly see where the performance resources are consumed, thus find out the performance bottlenecks of the application for further optimization. Erda also supports flame graph on the microservice platform now, to make tracing analysis visualized and more efficient.

5. System notification - DingTalk notification

Instant messaging apps have become an important way of communication in daily work, and traditional notification methods such as SMS and email cannot meet the demands of system notification. Therefore, Erda supports notification channel management of DingTalk. When an alarm is triggered or followed issue changes such as status updated or remark added, it will push a DingTalk notification to you timely to keep you updated.

Path: Org center > Settings > Notification channel

Full Changelog

New Features

(228759) [Monitoring] Support new visual topology in microservice governance. #2229 #2256
(230877) [Efficiency measure] Support efficiency measure of requirements and tasks. #3313 #3365 #3378
(238380) [Collaboration] Support Gantt chart for project management. #3259
(251153) [Monitoring] Support flame graph in tracing details. #2085
(222543) [Testing] Support management of test space status and basic information. #2758
(222561) [Testing] Support new label, reference, enable/disable, copy and parallel orchestration for test scene set. #266 #2453 #2989
(224168) [Monitoring] Support trace/error and log data storage via ES. #60 #2633
(231090) [Monitoring] Support alarm notification in levels and by SMS. #59 #2378
(261239) [Notification] Support notification channels of phone and email. #2219
(232241) [Notification] Support notification of DingTalk message. #3129
(240364) Support viewing logs of Spark jobs. #3275
(247411) [Cloud management] Add container resource menu. #1983
(251136) [Monitoring] Support new homepage for the microservice platform. #3154
(251135) [Monitoring] Adjust microservice platform menu. #3093
(251137) [Monitoring] Support new service list and topology in service monitoring. #3336 #2388
(252051) [Collaboration] Support new visual design for issues. #134 #2209
(263984) Optimize structure of the project collaboration page. #141 #142 #143 #144 #3394 #3401 #3404 #3405
(264027) Support buildlkitd instead of dockerd for erda packaging and building.
(264280) Optimize progress percentage statistics of requirements. #3360
(267570) Support scalable card component. #2341

Bug Fixes

(204238) The UI release takes too long. #1220
(205361) The dashboard can be saved when the required chart type is not selected. #1952
(209158) The release action in pipeline failed to report metadata. #3043
(209165) [Addon] It is not checked whether there is an addon in the project to be deleted. #1615 #3419 #3450
(210151) [Automated testing] If the interface is configured with a loop, the loop strategy should be expanded and displayed by default. #3020
(222146) Pipeline cache conflicts. #3318
(223455) [Automated testing] After turning the page and editing an execution plan, the page reloads and turns to the first page. #3137
(226938) The time fields are incomplete in the exported Excel file of project collaboration, such as closed time. #2882
(227823) The error message that occurs when relating repeated issues is unclear. #2990
(228378) The timeout configuration is unavailable as there is no timeout input field in the action of test plan. #3125
(231292) The support account only has permissions of audit log in the org center. #2159
(234806) [DOP] When referencing test cases in manual testing, selecting all only works with cases on the current page. #1984
(237839) [Automated testing] The orchestration relationship of parallel orchestrated interfaces or scene sets cannot be viewed in the execution details. #2892
(240758) [Deployments] An extra runtime card appears in the deployments when updating deployment via artifact. #3340
(246603) The pipeline execution details do not match the selected branch. #2051
(246738) Parameter details requires interaction optimization. #2161
(247460) The test plan cannot be filtered by iteration. #1957 #3140
(247463) The plan name column is too narrow to see full information. #3032
(247656) The environment order is inconsistent on different pages. #1968
(248026) [Manual testing] The test cases under test subset loads incorrectly. #3076 #3099
(248120) The scaled out value of the instance is inconsistent with the limit value displayed in monitoring. #2004
(248127) The total number of interfaces, execution rate and pass rate are missed in the automated test case. #3041
(248918) Project issue information displays in the personal dashboard though no project is joined. #3092
(248931) The organization announcement information is not updated as organization changes. #2008
(248966) [Log query] When entering the real-time tail page, the query conditions brought from the log query page should be bracketed. #172
(248985) [Active monitoring] The URL cannot be modified when editing. #1986
(249009) The percentage of used quota is wrong. #1997
(249051) [Log query] On the real-time tail page, the label filter button should be displayed. #172
(249116) Failed to import tasks with a 502 error. #3136
(249137) [Pipeline] The pipeline gets a panic on erda cloud. #3126
(249463) Failed to deploy across cluster. #266
(249480) [Automated testing] The execution pass rate in test plan is not precise to decimals. #3065
(249529) [Alarm] The alarm level in alarm rules and notification objects is incorrect after the old data is upgraded. #2001
(249553) [Alarm] Enter the alarm list page, edit the alarm rule for the first time, and the value field of the filter rule cannot be edited. #2001
(249566) [Notification Channel] When adding a notification channel, the AccessKeyId and AccessKeySecret fields have default values. #2001
(249626) [Test space] Failed to query when data exceeds one page. #3064
(249629) [Test space] There are two scroll bars on the page. #2018
(249666) Unable to view logs on V1.3. #3416
(249684) [Service analysis] After using ES to store trace/error and log data, the charts in the service overview show incorrectly. #2007
(249688) [O&M dashboard] The data of old dashboard cannot show. #2007
(249689) [Deployment log] After using ES to store trace/error and log data, the log of runtime deployment cannot show. #3073 #3077
(249764) [Upgrade test] The audit information is incorrect when the quota is configured as 0 before upgrade. #3349
(249796) [Alarm] Mobile phone is optional in the notification method of notification object in the alarm strategy. #2021
(249887) There is a scroll bar on the project quota page. #2156
(249894) The project name is displayed incompletely. #2154
(249948) The search experience of the backend management requires optimization. #183
(250216) [Alarm] When adding multiple notification groups in an alarm strategy, only the first one is displayed in the list. #2023
(250275) [Alarm] The old custom alarm rules are not compatible. #3088
(250388) [Alarm] It goes wrong when selecting all for comparison method in filter rules. #3102
(250393) [Alarm] It goes wrong when selecting not match for comparison method in filter rules. #78 #86
(250611) [Error analysis] No data on the error analysis page. #77
(250655) [Project collaboration] The view mode of markdown requires adjustment. #2075
(250657) [Notification channel] The creator field is displayed as the account in the notification channel list. #3216
(250658) [Alarm] The page of adding a new alarm strategy shows incorrectly. #2050
(250660) The page of adding a new dashboard shows incorrectly. #2048
(250877) Failed to turn the page of project members. #2052
(250883) [Test space] The dot color should change according to the test status. #3143
(251601) The description and default value of the get parameter in API management are not displayed after release. #2078
(251616) [Pipeline] The cron compensator still creates pipeline. #3119
(252139) The interface execution rate and pass rate exceed 100% in the execution details of test plan. #3126
(252476) After cancelling sorting order, the resources rank in descending. #2107
(252574) Failed to switch to a joined organization as admin. #3182
(252654) In Microservice Platform > Diagnose Analysis > Error Insight, the page of error details crashes. #2079
(252901) Failed to execute the automated test case, but the execution result is empty. #3161
(256203) [Alarm] Alarms are ignored as multiple notification methods are configured. #85
(256222) [Execution plan] The added test plan is not displayed. #3165
(256289) [Notification channel] The switching tab of notification channel switching requires improvement. #2112
(256376) [Execution plan] Test scenes are not parallel. #3166
(256434) [Microservice governance] The page title shows incorrectly on the microservice homepage. #2118
(256435) The resource allocation rate and allocated in the cluster list are wrong. #3173
(256437) Failed to go to the page of token management. #2116
(256535) After switching organization, the cluster list shows the clusters of the previous organization. #3173
(256550) The ascending and descending order of quota usage is reversed. #3173
(256552) Failed to copy scenes to an empty scene set. #3170
(256557) Only K8s clusters are watermarked in the cluster list. #2121
(256579) [Microservice governance] The number of services in msp project is wrong on the microservice homepage. #3181
(256635) [Execution plan] Failed to get the latest execution result when a scene is referenced by multiple scene sets. #3166
(256636) No data in resource monitoring of pod details. #3169
(256648) No data in resource monitoring when clicking node in the pod details to enter the node details page. #3174
(256721) [Alarm] The original notification method of DingTalk should be changed to DingTalk group in custom alarm rules. #3177 #3195
(256805) The name and value in the cluster list do not match. #3179
(256807) The value of memory quota in the cluster list is wrong. #3179
(256994) No data of resource statistics occasionally in the cluster list. #3184
(257036) Failed to view container resources when switching to terminus-dev cluster. #3185
(257042) [Microservice homepage] The number of services in the project shows 0. #3196
(257182) An error occurs when editing scenes of automated testing. #3199
(257257) [Test management] The statistics page requires performance optimization. #3222 #3230
(257960) [Project collaboration] Performance optimization is required. #3208
(257968) [Test report] Performance optimization is required. #3208
(257975) The error message that occurs when deleting a project requires optimization. #3362
(258142) [Application development] Performance optimization is required. #3256
(258272) The statistics page is moved up automatically after filtering. #2167
(258275) The statistics chart of automated testing shows wrong. #3233
(258315) [Automated testing] Each loop result is printed when viewing the execution result of an interface with loop. #3270
(259829) The automated test plan references a scene set. The referenced scene set executes successfully but the referencing scene set is failed. #3244
(260508) An error occurs when saving the edited pipeline. #3262
(260709) [Gantt chart] An error occurs when selecting multiple iterations. #2199
(260722) [Gantt chart] The historical data lacks start time. #3289
(260727) [Gantt chart] The tasks already included should be excluded. #3286
(260744) [Gantt chart] Failed to click to view details of the included tasks. #2200
(260745) [Gantt chart] The default iteration is wrong when there is no iteration in progress. #3284
(260843) [Gantt chart] The page is slow with a lot of requirements. #2205
(260845) [Gantt chart] Manual refresh is required after removing the relation. #2260
(260939) [Gantt chart] An error occurs occasionally when viewing plans. #2202
(260946) [Custom dashboard] The metrics group is unavailable when creating a new dashboard. #2204
(261267) The Gantt chart date is inconsistent with that of issues. #2211
(261274) The old data at 00:00 of Gantt chart needs to be fixed. #2211
(261286) The Gantt chart filtering requires optimization. #3276
(261331) The list of tasks included in the requirement does not show the status. #2231
(261389) The UXD of Gantt chart requires optimization. #2269
(261398) [Automated testing] No secondary confirmation when deleting scenes. #3277
(261505) The iteration oder is not fixes in Gantt chart. #3282
(261837) [Gantt chart] The filled in time is inconsistent with that of timeline. #2220
(261852) The date is not displayed when the mouse hovers on Gantt chart. #2220
(262206) The pod list in the DaemonSet details page shows incorrectly. #3290
(262534) [Deployments] The domain name set for the service does not take effect. #3322 #3323
(262586) [Automated testing] The button on the interface add/edit page is wrong. #2224
(262614) The data of issue due today and tomorrow on the homepage is wrong. #3354
(262679) [Automated test Platforming] Failed to view the configuration sheet log when executing a single test scene. #3304
(263116) [Automated testing] The pagination in execution details is incorrect. #3371
(263172) Failed to deploy API gateway in the testing environment. #3331
(263196) Create a bug with one click in ticket, and the page crashes when clicking the related issues in bug details. #2236
(263214) [Test environment] The admin cannot access the operation management platform. #2243
(263260) [Service list] The error rate of the services in the list always shows 0. #3339
(263281) [Service list] The average delay of service apm-demo-dubbo is inconsistent with that in topology. #2242
(263293) The efficiency measure in test environment requires optimization. #2254
(263359) [Topology] The page crashes after clicking the gateway node and external service node in the topology. #2244
(263409) [Service list] An error occurs when entering the service list of a msp project. #2245
(263474) [Automated testing] The interface execution takes 5 hours and the loop termination condition does not work. #3329
(263572) The status not required in the process should not be displayed. #2255
(263575) Icon is required for issue complexity. #2270
(263634) dice.yml error leads to orchestrator panic. #3351
(263635) [Gantt chart] Manual refresh is required after filtering by assignee. #3335
(263765) [Gantt chart] The dragged date is incorrect. #2269
(263766) The refresh button does not work on the project collaboration page. #2271
(264118) [Service analysis] The data of RPC call is incorrect. #2279
(264469) [Automated testing] The later interface cannot get the output parameters of the previous interface when executing the plan. #3402
(264516) The addon oversold ratio is invalid in test environment. #3383
(265589) [Microservice governance] The HTTP status chart of service node in the topology is incorrect. #3397
(265590) [Gantt chart] An error occurs when dragging the date. #3390
(265633) The environment variables are not injected when running workflow via SPRAK-OPERATOR. #3392
(265656) [Topology] The number of unhealthy services and free services is wrong in topology analysis. #2297
(265684) [Topology] MySQL and Redis nodes are not displayed in the topology. #3414
(265721) [Topology] The HTTP status chart of services node details is not displayed completely with a certain number of status. #2297
(265728) [Topology] The services in topology overview and topology analysis include external nodes. #2297
(265844) The link in DingTalk notifications is incorrect. #3400
(265949) The application cannot be scaled out. #3398
(266007) The scroll bar style in test statistics is wrong. #2304
(266027) The service list is empty when adding service instance for addon. #2305
(266168) The organization member list requires optimization. #2343
(266407) [Service list] The average throughput and average delay in the chart is inconsistent with that in the list. #3414 #3445
(266408) [Service list] The services in the unhealthy service list are not filtered. #3414
(266409) [Service monitoring] The abscissa axis time in the chart is incorrect when the query time is longer than one hour. #3414
(266410) [Service list] The unhealthy services in the unhealthy service ranking is inconsistent with that in topology. #3414
(266411) [Service list] An error occurs on the service list page. #3414
(266412) [Service monitoring] The time unit in the slow response API and slow response SQL is unreasonable. #3414
(266417) [Service monitoring] No unit for the response time. #2316
(266446) [Filter] No profile photo in kanban. #3412
(266447) [Project collaboration] An error occurs when turning page or refreshing list. #3413
(266448) [Project collaboration] Add conditions to the custom filter conditions, the filter status turns to changed, but the added conditions are not displayed after clicking filter. #2320
(266449) [Project collaboration] The filter conditions in the issue list cannot be displayed normally. #2321
(266450) [Project collaboration] Add two filter items after selecting all, click cancel and open again, then the two items are still displayed. #2322
(266452) [Project collaboration] No load more in kanban. #3412
(266454) [Project collaboration] There are two scroll bars in kanban. #2323
(266455) [Project collaboration] The kanban filter in iteration requires modification. #3412
(266456) [Project collaboration] The delete icon (x) style requires adjustment. #2322
(266458) [Project collaboration] The start date and end date cannot be the same in the kanban filter. #2327
(266459) [Project collaboration] Severity should be changed to complexity in requirement filter. #3469
(266460) [Project collaboration] Logic error of filter interval in kanban. #2327
(266461) [Project collaboration] The filter cursor requires optimization. #2326
(266463) [Project collaboration] The labels are not displayed completely. #2328
(266466) [Service monitoring] The overview page shows incorrectly. #2336
(266908) [Artifact management] No artifact displayed when quickly updating from artifacts. #2358
(267323) [Service list] The page number of unhealthy services page and no traffic services page is incorrect. #3488
(267696) [Org center] The project information page of msp projects is wrong. #2351
(267958) [Monitoring] The page of notification channel and access configuration of msp projects does not respond. #3458
(267968) [Microservice governance] An error occurs when returning to the microservice homepage from the service list page. #2363
(267978) [Tracing] No data returned when querying by dubboMethod. #3490 #2405
(267990) Assignee style error. #2362
(268044) Click the related requirement or task but no issue is found. #2365
(268052) The requirement deadline should change as its included task is removed. #3470
(269998) Failed to change the issue status in the issue list. #3515

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v1.5.0