By the recent epidemic affecting the company cafeteria is not open, in order to solve the problem of feeding colleagues, departments need statistics ordering that next week every Friday; employees are set next week for lunch and dinner from the individual company's option, once determined stand for one week constant.
To complete ordering information is usually collected within a sector employees need to go through the following steps:
1. inform the head of the interface group members who collect order information;
2. Each group members feedback interfaces notify people ordering information, each group collected information on different forms, such as a message through QQ, micro-letters, etc. Solitaire feedback;
3. The members of the group interfaces summarized person ordering information back to the department heads;
4. The head of the summary data for each group to form an overall table and the table total shots feedback to the working group and asked the staff to further confirm;
5. Employee information check the summary table, if found themselves re-ordering information is incorrect department heads modify individual feedback.
6. The head of the table after the check issued to the staff responsible for ordering.
Because when people had a rotating group interfaces, we found some less efficient place:
1. feedback yet determined the person; all members need to find out who is no comparison according to feedback information in the feedback people and groups;
2. The need for an interface group of people (people) and department heads in two stages excel tables summarize;
3. labor statistics is difficult to ensure no mistakes, we need to cross-check;
We created for this project for two more convenient ordering information collection staff, shown in Figure 1:
FIG 1 two items for collecting information ordering
The step of using the system to collect the order information as follows:
1. The department heads to create a problem in the "team task tracking" project and fill in the account list for all employees to "assigned to" field corresponds to the form, click on the "bulk distribution" button to list each a sub-accounts assigned tasks and subtasks appear below the issue;
Figure 2 issue tracking team tasks and subtasks list
2. department heads in "tracking team tasks" and "sub-tasks Item 1," two projects management interface, click "Bulk Register" button to create a team-volume account (default password account created for batch 123456) was, and click "adding to the user group" to add bulk to the "user group" has a problem execute permissions (ExecAuth) in the account;
Figure 3 Rights Management Interface
3.组员获得账号以及操作权限后，登录系统通过父任务下的子任务列表或者进入“子任务项目1”查看分配给自己的问题，填写相应信息并按流程操作。
如图4所示，当前问题状态为“未提交”，根据流程可以进行"更新信息"和“提交”两种操作，对应下方的两个按钮。
图4 子任务的详细信息
用户superadmin点击"提交"按钮后，子任务列表中对应的状态会同步进行更改；部门负责人可以通过子任务列表清楚地看到各个同事的提交情况。
图5 superadmin提交后的子任务列表
4.部门负责人点击图2中的"导出子任务"按钮，可将各组员的反馈情况导出到excel，如图6所示：
图6 导出到excel的子任务数据
从订餐信息收集推而广之，很多上级分派下级执行的任务都可以用类似方法进行跟踪，只需要修改子任务的流程和字段即可。
该系统具有的特点：
1.部门负责人只要保留一份团队成员列表就可以很方便地一键分派任务；
2.每个员工单独处理自己的问题，无法修改分配给他人的问题，避免误操作；
3.每个子任务按制定的流程进行处理；
4.子任务当前状态直观显示，便于任务分派人了解所有团队成员执行子任务情况；
5.一键导出表格；
很可能有人会问为什么不用超级表格？首先疫情期间可能因远程办公的人数太多，用户数超过负载导致超级表格极不稳定甚至很多时候无法访问；其次是某些同事未反馈时很难找到未及时反馈的人员；最重要的一点是超级表格无法按特定流程进行事务跟踪。