JP2000123071A - Task management system for to/do list - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize a method for the unitary management of an individual task registered in a ToDo list and a group task registered in problem management system without individually managing those tasks. SOLUTION: This is a means for registering a problem registered by a problem management system 103 in an individual ToDo list 109 of a worker who actually works on the problem as his/her own task. Also, this is a means for registering the progress situation of the task on the ToDo list 109, and for reflecting it on a problem management system 103. Thus, a means for mutually exchanging data between the ToDo list and the problem management system can be realized.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data exchange function between a ToDo list for managing individual tasks and a pending management system for managing tasks (pending) of a group.

[0002]

2. Description of the Related Art Conventionally, a ToDo list is a system attached to a schedule management system, and has been developed as a system for managing personal tasks as a personal memo. The pending management system has been developed as a system for managing tasks (pending) that have occurred in a group, and has a form in which both individual tasks and group tasks are mixed. A related system of this type is disclosed in Japanese Patent Application Laid-Open No. 10-097569.

[0003]

The above-mentioned prior art is characterized in that tasks generated as a group are automatically allocated as individual tasks.
There is no connection with the Do list (memorandum). Therefore, there is no function for personally registering and managing a task (pending) of an individual worker generated in working on the assigned task. In other words, tasks from the viewpoint of the worker are basically not necessary for the concept of an individual or a group, and the progress can be simply managed as one's own task. However, in the related art, it is necessary to separately manage the tasks, and work efficiency is poor.

An object of the present invention is to provide a method for centrally managing individual tasks and group tasks.

[0005]

SUMMARY OF THE INVENTION In order to achieve the above object, a personal ToDo list of a worker who actually works on a task (pending) registered in the pending management system as his / her own task. Register with. This allows
Tasks generated in personal work and tasks (pending) generated through group work can be managed in a personal ToDo list. In addition, by registering the progress of the task on the ToDo list and reflecting it in the pending management system, it is easy to grasp the progress as a group task.

[0006]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to FIG. The ToDo list 109 includes an input / output device 114 for referencing and registering a task, a task input / output unit 113 for managing an input task, task data 108 for storing input task data, and a user of the user using the ToDo list. The user management unit 112 manages user information such as a user ID and a name, the user information 111 stores registered user information, and the transfer unit 110 exchanges registered tasks and user information with the issue management system. You. Although the input / output device 114 and the ToDo list 109 take a C / S type connection form via a network, they may exist on the same machine.

The issue management system 103 includes an input / output device 101 for referring to and registering an issue, an issue input / output unit 104 for managing an input issue, an issue data 102 storing input issue data, and an issue management system. User management unit 106 that manages user information such as the user ID and name of a user who uses, user information 105 that stores registered user information, and transfer that exchanges registered issues and user information with the issue management system. It comprises a unit 107.
Although the input / output device 101 and the issue management system 103 take a C / S type connection form via a network, they may exist on the same machine.

Next, the processing operation of FIG. 1 will be described with reference to the flowchart of FIG. When an issue occurs in the group work, first, the input / output device 1 of the issue management system
From 01, the user logs in to the issue management system. For login, the user is authenticated by inputting a personal user ID and a password.
After logging in, the issue is input from the input / output device 101 of the issue management system. The input contents include the pending contents 401, the worker 404, and the deadline 405 shown in FIG.
1). The pending input / output unit 104 allocates the ID 402 as a unique key for identifying the pending, and sets the name of the log-in user to the registrant 403. This can be done by setting the user ID at the time of login as it is, or by using the user ID stored in the user information 105 as a key and using the name of the row matching the ID 501 shown in FIG. Good.

Further, the data is registered in the pending data 102 and transferred to the transfer unit 107 at the same time (202). The transfer unit 107 inquires of the ToDo list transfer unit 110 whether the worker 404 of the delivered pending data exists as a user of the ToDo list. Here, if means for preliminarily synchronizing the user information of the pending management system and the user information of the ToDo list is adopted, it is possible to confirm the presence of the user only by the transfer unit 107 of the pending management system without inquiring. is there. If the user does not exist, the process ends (203).

If the user exists, the pending data is transferred to the ToDo list transfer unit 110 (20).
4). The transfer unit 110 transfers the pending data to the task input / output unit 11.
The task input / output unit 113 transfers the pending data to the task data 108 as task data of the worker 304 of the pending data (205). If the format of the pending data of the pending management system is different from the format of the task data of the ToDo list, the difference can be absorbed by performing the structure conversion here.

When each worker inputs the progress of a task, the procedure is reversed. FIG.
The operation will be described with reference to the flowchart of FIG. First, T
The user logs in to the ToDo list from the input / output device 114 of the oDo list. For login, an individual user ID and a password are input. After login, T
Input from the input / output device 114 of the oDo list. The input content is the progress status 406 shown in FIG.
1). The task input / output unit 113 registers the progress data in the task data 108 and transfers the progress data to the transfer unit 110 (302). The transfer unit 110 inquires of the transfer unit 107 of the concern management system whether or not the task data exists as the concern data of the concern management system based on the delivered task data ID 302.

Here, a procedure for inquiring the transfer unit 107 by having a flag or the like for identifying a task registered from the ToDo list or a task registered from the issue management system in the data item shown in FIG. May be omitted. If there is no pending data, the process ends (303). If the data is present as pending data, the task data is transferred to the transfer unit 107 of the pending management system (304). The transfer unit 107 transfers the task data to the pending input / output unit 113,
Is the ID of the pending data registered in the pending data 102
402 is compared with the ID 402 of the received task data, and the matching data is updated (305).

[0013]

According to the present invention, a task managed by an individual and a task managed by a group can be handled in a unified manner, and the efficiency of management work by a worker can be improved.

[Brief description of the drawings]

FIG. 1 is a configuration diagram illustrating the principle of a task management system according to an embodiment of the present invention.

FIG. 2 is a flowchart of task management according to the present invention.

FIG. 3 is a flowchart of task management according to the present invention.

FIG. 4 is a data format diagram of task management according to the present invention.

FIG. 5 is a data format diagram of user information according to the present invention.

[Explanation of symbols]

101: input / output device of the pending management system, 102: pending data, 103: pending management system,
104: pending input / output unit, 105: user information of the pending management system, 106: user management unit of the pending management system,
107: transfer section of the issue management system, 108: task data, 109: ToDo list, 1
10: ToDo list transfer unit, 111: ToDo list user information, 112: ToDo list user management unit, 113: Task input / output unit, 114: ToDo list input / output device.

Claims (2)

[Claims] 1. A means for registering and authenticating a user ID for identifying an individual, a means for storing a task input by an individual in a storage area of each individual using the user ID as a key, and referring to a task input by each individual. In the ToDo list, which has means for executing the task, storing means for storing the progress of each task, and means for referring to the progress of each task, an input is made between the task management system for managing the tasks (pending) of the group. A task management system for a ToDo list, wherein tasks are exchanged for each user ID. 2. A means for registering and authenticating a user ID for identifying an individual, a means for storing a task input by an individual in a storage area of each individual using the user ID as a key, and referring to a task input by each individual. A task management system that manages group tasks (pending) in a ToDo list having means for storing task statuses, storing task statuses, and referencing task statuses. A task management system for a ToDo list, wherein information on the progress is exchanged for each task ID.