In the process of software development, companies often encounter the following process management problems, which lead to a decrease in research and development efficiency:
- Many repetitive processes, high manual operation cost, easy to cause human error
- Untimely assignment of work leads to accumulation of tasks and even task delays
- Information maintenance and synchronization are not timely, and manual checking of task fields is costly
ONES Automation process automation solutions help R&D teams automate tedious and repetitive tasks, improve R&D management efficiency, and enable the team to focus on more creative work.
ONES Automation Process Automation
"Configuration-Execution-Analysis-Improvement", ONES Automation helps project managers easily build automation rules, achieve process standardization, process operation visualization , and scientifically analyze R&D process issues to help the team improve R&D efficiency.
ONES Automation process automation
easy to use, easy to build automation rules
ONES Automation provides a graphical configuration interface, you can complete the construction of custom automation rules in a few simple steps, and execute the process efficiently.
The automation rule is composed of three elements: "Trigger Event", "Trigger Condition" and "Process"
"Trigger event" is the beginning of the automation rule. The system will determine whether the user's operation meets the "trigger event", such as creating a new work item, status flow, field update, etc. If it is satisfied, it will start the execution of subsequent processes.
"Trigger Condition" is used to narrow the scope of the rule. Users can choose to always trigger or set "Meet the following conditions" to execute the process.
"Process" refers to the specific execution of the rules. The system executes each process linearly from top to bottom according to the configuration used.
Automated rule configuration
According to the general demand scenarios in the R&D management practice, ONES Automation also presets a variety of commonly used automation rule templates, which the administrator can activate with one click:
- Automatically assign the person in charge of the ticket
- The demand status is synchronized to the processing result of the source work order
- After the tasks are completed, the source requirements are automatically completed
- After all subtasks are completed, the parent work item is automatically completed
- After the iteration of the requirement is updated, the task of requirement disassembly is also moved to the same iteration
ONES Automation provides a variety of automation rule templates
automates execution and supports the processing of complex processes
According to the built automation rules, the system will determine the "trigger event" and "trigger condition", and automatically execute the specified process action.
Take "When the priority is the highest, automatically assign tasks to the designated person in charge" rule as an example: when the user updates the task priority (trigger event), and the priority is the "highest" (trigger condition), the system will automatically Assign the task to the "designated person in charge".
When the priority is the highest, the person in charge is automatically assigned
In actual work, many requirements and tasks do not exist independently. They may have a parent-child relationship or an association relationship, which makes the process more complicated. To this end, ONES Automation also provides the "linkage data object" and "conditional branch" capabilities to meet the judgment and execution of special processes.
The "Linkage Data Object" will add a branch process to the automation rule. The conditional check and action of this division will all use the linkage data object as the target of judgment or operation. For example, in the rule of "Automatically complete source requirements after tasks are completed", it is judged whether all subtasks (linkage data objects) under a certain requirement have been completed.
"Linkage data objects" meet complex process execution
When encountering "conditional branch", the system will continue to return to the main process after executing the branch process until all processes in the automation rules are executed. For example, in the "New Work Order Automatic Assignment of Responsible Persons" rule, the project is determined by setting the "conditional branch", and different responsible persons are assigned.
"Branch conditions" satisfy complex process execution
Analyze the operation of rules and improve the research and development process
In ONES Automation, project managers can manage all automation rules in a unified manner, preview the configuration of the rules, and control the running status of the automation rules with one click through the "switch". It also supports viewing the running logs of the rules, helping the team to accurately control the process efficiency and conduct timely investigations. Problem, continuous improvement of business process.
ONES Automation View rule operation log
ONES Automation classifies and defines the execution results of the rules, which is convenient for managers to quickly find the reasons for the failure of the operation.
ONES Automation execution result analysis
In addition, ONES Automation also supports "Custom Script", "Timed Check", "Add Follower" and other bright functions, to meet the needs of the company's personalized automation process, timely tracking and finding problems.
The ONES Automation process automation solution greatly saves the team's time and labor costs by constructing and managing automation rules, effectively improving the efficiency of the software R&D team, creating a more intelligent R&D management practical experience, and helping companies complete automation transformation.
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。