CN112783622A - JIRA system-based task management method, system, device and storage medium - Google Patents
JIRA system-based task management method, system, device and storage medium Download PDFInfo
- Publication number
- CN112783622A CN112783622A CN202110042423.XA CN202110042423A CN112783622A CN 112783622 A CN112783622 A CN 112783622A CN 202110042423 A CN202110042423 A CN 202110042423A CN 112783622 A CN112783622 A CN 112783622A
- Authority
- CN
- China
- Prior art keywords
- task
- state
- change information
- timing
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 55
- 230000008859 change Effects 0.000 claims abstract description 87
- 238000000034 method Methods 0.000 claims abstract description 31
- 230000008569 process Effects 0.000 claims abstract description 20
- 238000012545 processing Methods 0.000 claims description 39
- 238000004458 analytical method Methods 0.000 claims description 18
- 238000012544 monitoring process Methods 0.000 claims description 11
- 238000011161 development Methods 0.000 abstract description 12
- 238000004904 shortening Methods 0.000 abstract description 3
- 230000000007 visual effect Effects 0.000 abstract description 3
- 238000012360 testing method Methods 0.000 description 10
- 238000012790 confirmation Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 230000008439 repair process Effects 0.000 description 6
- 230000007547 defect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000012552 review Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000013102 re-test Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
- G06F9/4887—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues involving deadlines, e.g. rate based, periodic
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a task management method, a system, equipment and a storage medium based on a JIRA system, wherein the task management method comprises the following steps: acquiring task change information when a task in the JIRA system is changed in real time; triggering a network hook of the JIRA system based on the task change information, and calling an information receiving interface of the custom server; sending task change information to an information receiving interface of the custom server; the user-defined server analyzes and processes according to a preset task time limit control rule to generate a corresponding control result; and sending the management and control result through a third-party platform. The invention times the task with changed working state in the JIRA system, and sends a prompt to the corresponding user when the time reaches the corresponding working time limit threshold, thus preventing the task from staying too long in the current working state and shortening the development period of the task; and the time consumption of the task can be divided into value-added time and non-value-added time, and the time consumption of the task is refined to obtain a visual display image.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, a system, a device, and a storage medium for task management based on a JIRA system.
Background
The jita is widely applied to the work fields of task tracking, project tracking, agile management and the like as a management and transaction tracking tool.
Generally, a task usually undergoes a plurality of working states such as requirement collection confirmation, design development, testing, acceptance and the like before being completed, and in an actual situation, the task often stagnates in one working state for a long time due to a plurality of reasons, so that the problems that the task development cycle is long and the task cannot be rapidly delivered are caused, and therefore, a technical scheme capable of prompting a worker to timely process the long-standing task is urgently needed.
Disclosure of Invention
In view of the defects of the prior art, the invention provides a task management method, a system, equipment and a storage medium based on a JIRA system, aiming at timely reminding tasks with waiting time exceeding a certain preset time so as to effectively solve the problems of long development period and incapability of quick delivery of the tasks.
To achieve the above and other related objects, the present invention provides a method for task management based on a JIRA system, comprising:
acquiring task change information when a task in the JIRA system is changed in real time;
triggering a network hook of the JIRA system based on the task change information, and calling an information receiving interface of a custom server;
sending the task change information to an information receiving interface of the custom server;
the user-defined server analyzes and processes according to a preset task time limit control rule to generate a corresponding control result;
and sending the control result through a third-party platform.
In an embodiment of the present invention, the method further includes: monitoring a task in the JIRA system.
In an embodiment of the present invention, the preset task time limit management rule includes:
and setting corresponding working time limit thresholds aiming at different task states.
In an embodiment of the present invention, the step of analyzing and processing the custom server according to a preset task time limit management and control rule, and generating a corresponding management and control result includes:
receiving the task change information and judging the hook state;
judging the task state according to the hook state and the task change information, and starting timing;
analyzing and processing according to the timing time, and generating a control result:
when the timing time exceeds the corresponding working time limit threshold value in the task state, generating a task state alarm signal as a control result;
and when the timing time does not exceed the corresponding working time limit threshold value in the task state, taking the timing time and the corresponding task state as a control result.
In an embodiment of the present invention, the step of receiving task change information and determining the task state includes:
when the task change information comprises 'create' information, the hook state is 'created';
when the task change information comprises the update information, the hook state is updated;
when the task change information includes "delete" information, the hook state is "deleted".
In an embodiment of the present invention, the step of determining the task state according to the hook state and the task change information and starting timing includes:
when the hook state is 'created', timing is started;
when the hook state is 'updated', judging whether the task change information contains state update information:
if yes, judging the task state of the task and starting timing; otherwise, timing is not carried out;
when the hook status is "deleted", no timing is performed.
The invention also discloses a JIRA system-based task management system, which comprises:
the information acquisition module is used for acquiring task change information when a task in the JIRA system is changed in real time;
the interface calling module is connected to the information acquisition module and used for triggering the network hook of the JIRA system based on task change information and calling an information receiving interface of the custom server;
the first sending module is connected to the information acquisition module and used for sending the task change information to an information receiving interface of the custom server;
the analysis processing module is connected to the first sending module and used for analyzing and processing the custom server according to a preset task time limit control rule and generating a corresponding control result;
and the second sending module is connected to the analysis processing module and used for sending the control result through a third-party platform.
In an embodiment of the present invention, the task management system further includes:
a task monitoring module to monitor tasks in the JIRA system.
In an embodiment of the present invention, the task management system further includes:
and the threshold setting module is used for setting corresponding working time limit thresholds aiming at different task states.
In an embodiment of the present invention, the analysis processing module includes:
the judging unit is used for judging the hook state when the task change information is received;
the timing unit is connected to the judging unit and used for judging the task state according to the hook state and the task change information and starting timing;
the processing unit is connected to the timing unit and used for analyzing and processing according to timing time and generating a control result;
when the timing time exceeds the working time limit threshold corresponding to the task state, the processing unit generates a task state alarm signal as a control result;
and when the timing time does not exceed the working time limit threshold corresponding to the task state, the processing unit takes the timing time and the corresponding task state as a control result.
In an embodiment of the present invention, when the task change information includes "create" information, the determining unit determines that the hook status is "created";
when the task change information comprises update information, the judging unit judges that the hook state is updated;
when the task change information includes "delete" information, the determination unit determines that the hook state is "deleted".
In an embodiment of the present invention, when the task status is "created", timing is started;
when the hook state is 'created', timing is started;
when the hook state is 'updated', judging whether the task change information contains state update information:
if yes, judging the task state of the task and starting timing; otherwise, timing is not carried out;
when the hook status is "deleted", no timing is performed.
The present invention also discloses a JIRA system-based task management device, comprising a processor coupled to a memory, the memory storing program instructions that, when executed by the processor, implement the JIRA system-based task management method of any of claims 1 to 6.
The present invention also discloses a computer-readable storage medium containing a program which, when run on a computer, causes the computer to execute the jitra-system-based task management method according to any one of claims 1 to 6.
As described above, the present invention provides a method, a system, a device, and a storage medium for task management based on a JIRA system, which can time the time of a task in the latest working state when a new task is created, a task is deleted, or the working state of the task is changed in the JIRA system, and send a reminder to a corresponding user when the time reaches a time threshold corresponding to the working state, thereby preventing the task from staying in the current working state for a long time, and thus shortening the development cycle of the task; and the time consumption of the task can be divided into value-added time and non-value-added time, and the time consumption of the task is refined to obtain a visual display image.
Drawings
The features and advantages of the present invention will be more clearly understood by reference to the accompanying drawings, which are illustrative and not to be construed as limiting the invention in any way, and in which:
FIG. 1 is a system flow diagram illustrating a task management method according to the present invention.
FIG. 2 is a block diagram of the task management system according to the present invention.
FIG. 3 is a block diagram of an analysis module according to the present invention.
FIG. 4 is a diagram illustrating a system configuration for implementing the task management device according to the present invention;
fig. 5 shows an actual display interface of the task management method and the task management system according to the present invention.
Reference numerals:
an information acquisition module 1;
an interface calling module 2;
a first transmission module 3;
an analysis processing module 4;
a second sending module 5;
a task monitoring module 6;
a judgment unit 41;
a timing unit 42;
a processing unit 43.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The present invention may be embodied or applied in various other specific forms, and the terms "upper", "lower", "left", "right", "middle" and "a" used herein are for convenience of description only and are not intended to limit the scope of the present invention, and changes or modifications in relative relationship thereto are deemed to be within the scope of the present invention without substantial change in technical content.
It should be noted that the drawings provided in the present embodiment are only schematic and illustrate the basic idea of the present invention, and although the drawings only show the components related to the present invention and are not drawn according to the number, shape and size of the components in actual implementation, the form, quantity and proportion of the components in actual implementation may be changed arbitrarily, and the layout of the components may be more complicated.
In daily work, the JIRA system is widely applied to the work fields of defect tracking, customer service, demand collection, process approval, task tracking, project tracking, agile management and the like as a project and transaction tracking tool.
As shown in fig. 1, the present embodiment provides a method for task management based on a JIRA system, including:
step S1, acquiring task change information when the task in the JIRA system is changed in real time;
in a JIRA system, a user performs different operations for a task, each of which causes the hook status of the task to change. For example, a user newly creates a task in the JIRA system, and the hook status of the task is "created"; when the task is in the process of processing, the hook state is 'updated'; a user deletes a task in the JIRA system, and the hook status of the task is "deleted".
The task in the JIRA system is monitored in real time, and when the hook status is changed in the above three cases, it is determined that the task is changed, and corresponding task change information, which is the changed hook status, that is, the current hook status, is generated in step S1.
In order to be able to acquire the task change status in the JIRA system in real time, the task in the JIRA system is also monitored in real time.
By monitoring the tasks in the JIRA system, the task change information can be obtained at the first time when the hook state of the task is updated, the task is created and the task is deleted, so that the network hook in the JIRA system can be triggered at the first time when the task is changed, then the custom server carries out monitoring processing to obtain a control result, and a user can also obtain a notification of the corresponding control result in time on a third-party platform.
Step S2, triggering a network hook of the JIRA system based on the task change information, and calling an information receiving interface of the custom server;
web hook (Webhook) in the JIRA system is a method for adding or changing web page representation by customizing a callback function, which is a "user-defined HTTP callback", usually activated by some event, and a callback function, which is a function called by a function pointer, for being called by another party when a specific event or condition occurs, for responding to the event or condition. In this embodiment, when the task change information is obtained in step S1, the network hook in the jitra system is triggered and activated, and then an information receiving interface of a custom server is called through a callback function, where the custom server is used to process the task change information of the jitra system, and the information receiving interface is a Uniform Resource Locator (URL), which is a compact representation of a location and an access method of a Resource that can be obtained from the internet and is an address of a standard Resource on the internet.
In a preferred embodiment of the present invention, the network hook in the JIRA system is pre-created, and the setting of the network hook may be triggered according to the change of the hook status, that is, when the hook status is "created", "updated" and/or "deleted", the network hook is triggered.
Step S3, sending task change information to the information receiving interface of the custom server;
after calling the information receiving interface of the custom server, the network hook in the JIRA system sends the task change information to the information receiving interface of the custom server through the network, so that the task change information is transmitted to the interior of the custom server through the information receiving interface.
Step S4, the user-defined server analyzes and processes according to a preset task time limit control rule to generate a corresponding control result;
and after the user-defined server receives the task change information through the information receiving interface of the user-defined server, analyzing and processing the task change information according to a preset task time limit control rule and generating a corresponding control result.
In this embodiment, before monitoring the task in the JIRA system, the task management method further includes:
and setting corresponding working time limit thresholds aiming at different task states.
In the software lifecycle, in addition to three hook states of "created", "updated" and "deleted" previously set for triggering network hooks, a hook state "updated" in a task in the jitra system includes a plurality of task states representing all development flows in the task development process.
In this embodiment, the hook status "updated" further includes: not started, requiring project validation, pending development, in execution, to be tested, in testing, defect repair, in testing, PO acceptance, completed, and/or closed.
When a user has created a task in the JIRA system, completed the project, but has not performed any development action, then the task state is "not started" at this time;
when the task needs to be evaluated and a task evaluation link is started, the task state is changed into 'requirement scheme confirmation'; preferably, a corresponding 'requirement review' button is set in the JIRA system, and after the button is selected, the task state is changed into 'requirement scheme confirmation';
when the review fails, the task status will be updated from "demand plan validation" to "closed";
when the task state is 'off', the task can be restarted and the redevelopment process is entered, and the task state is recovered to 'not started'.
When the review is not passed, the task state is updated from ' requirement scheme confirmation ' to be developed ';
after the scheme is determined, entering a development state, namely performing software coding, wherein a task state corresponding to a coding process is 'executing';
after the coding is finished, the software needs to be tested, and then the task state is changed into 'to be tested';
in the software test result, the test is passed and the test is not passed, and when the test is passed, the task state is updated to 'PO acceptance'; the test fails, and the task state is updated to 'defect repair';
if the software test fails, the repair is started, and then the task state is changed into 'repair in process'; after the repair is finished, the software test is jumped back again, namely the task state is changed into the state to be tested again, and the retest stage is started;
and when the software passes the test, checking and accepting, wherein the task state corresponding to the checking and accepting is in the checking and accepting process, the task state is changed into the completion state when the checking and accepting process passes, and otherwise, the task state is not to be tested, and the software is tested again.
The time required to complete each task is different and therefore the working time limit threshold is set correspondingly differently for different task states. The task time limit control rule is pre-stored in a custom server, is set according to working time limit thresholds corresponding to different task states, and can be changed according to the actual working conditions. And when the custom server receives the task change information, identifying and obtaining a hook state and a task state contained in the task change information, and obtaining a corresponding working time limit threshold from the stored working time limit thresholds corresponding to different task states, so as to realize the automatic matching function of the custom server. For example, when the task state after the task update is "under test", the corresponding working time limit threshold is 10 days; when the task state is 'check in the middle', the corresponding working time limit threshold value is 3 days.
The process of the analysis processing in step S4 is divided into three steps:
firstly, when the custom server receives the task change information, judging the hook state:
when the user-defined server judges that the hook state of the task is 'created', the user-defined server starts timing; when a task is just created, the custom server times the default initial state of the task when the task is created.
When the custom server judges that the hook state of the task is "updated", the custom server further judges whether the task change information contains state update information, for example, whether the task change information contains changelog and its items.i.field is status: if yes, starting timing; otherwise, timing is not carried out; only when two conditions of changelog and items.i.field as status are simultaneously met in the task change information, self-defining a server to start timing;
further, when the task change information satisfies two conditions including changelog and items.i. field as status, the task state is further determined, that is, the task states "not started", "to be tested", and the like, as described above.
When the custom server judges that the hook state of the task is 'deleted', the custom server does not count time, and the task is deleted from the JIRA system at the moment, so that the task is not necessary to be monitored.
In a preferred embodiment of the present invention, the custom server determines the hook status in the following manner:
when the task change information comprises 'creation' information, for example, when the value of webhookEvent in the task change information is jira: issue _ created, the custom server judges that the hook state of the task is 'created';
when the task change information comprises update information, for example, when the value of webhookEvent in the task change information is jira: issue _ updated, the custom server judges that the hook state of the task is updated;
when the task change information includes "delete" information, for example, when the webhookEvent value in the task change information is jira: issue _ deleted, the custom server determines that the task state of the task is "deleted". And then judging the task state according to the hook state and starting timing. The user-defined Server judges and obtains a task state according to the task change information, obtains a working time limit threshold corresponding to the task state, and starts timing from the time when the task state of the task is updated to obtain real-time timing time when the task stays in the updated task state, for example, when the task state after the task is in the process of checking, the user-defined Server obtains the corresponding working time limit threshold for 3 days, and times the time when the task stays in the task state of checking.
And further, analyzing and processing according to the timing time to generate a control result.
The analysis processing process is that the user-defined server judges whether the timing time of the task staying in the updated task state reaches the working time limit threshold corresponding to the current task state of the task:
when the timing time exceeds the corresponding working time limit threshold value in the task state, the custom server generates an alarm signal of the task state as a control result;
and when the timing time does not exceed the corresponding working time limit threshold value in the task state, the user-defined server takes the timing time and the corresponding task state as a control result.
For example, if the task state after the task update is "checking in the middle", the corresponding working time limit threshold is 3 days, and if the timing time obtained by the custom server is 4 days, the custom server judges that the timing time exceeds the working time limit threshold, at this time, the management and control result obtained in step S4 is an alarm signal of the task state generated by the custom server; if the timing time obtained by the custom server is 2 days, the custom server judges that the timing time does not exceed the working time limit threshold, and at this time, the control result obtained in step S4 consists of the timing time of 2 days and the task state of "check receiving".
Further, after the corresponding management and control result is generated in step S4, the task management method further includes:
and storing the control result.
After the user-defined server stores the control result, subsequent users can conveniently inquire and call the control result, and the users can conveniently export and research the control result.
And step S5, sending the control result through a third-party platform.
After the control result corresponding to the task change information is obtained, the custom server calls an information receiving interface of a third-party platform and sends the control result to a corresponding user through the information receiving interface, and the user can be an individual or a group, for example, the third-party platform is a nailing platform. The third-party platform is not limited, and the third-party platform is within the protection scope of the invention as long as the third-party platform can be used for displaying and displaying the control result.
As shown in fig. 5, the flow, hook state, task state update, and time spent by each hook state and task state of the whole task are shown, so as to facilitate monitoring of the development state of the task and management of the state time limit.
As shown in fig. 5, in some embodiments, the task management method further includes distinguishing a plurality of task states into an added-value state and a non-added-value state, and is configured to count time consumed by all hook states and task states that a certain task has been subjected to, to obtain an added-value time and a non-added-value time, for example, regarding a task state in which the task state is "updated" as an added-value state in "requirement scheme confirmation", "execution", "test", "check", and "acceptance", and regarding a task state in which the task state is "not started", "to be developed", "to be tested", "defect repair", and "PO acceptance" as a non-added-value state; the task management method can further include processing the value-added time and the non-value-added time to obtain a value-added time percentage and a non-value-added time percentage, and displaying the value-added time percentage and the non-value-added time percentage to a user, for example, if a current task state of a certain task is "executing", the task consumes 1min in a task state "requirement scheme confirmation" state, 14min in a task state "to be developed", and 5min in a task state "executing", the value-added time of the task is 6min, the non-value-added time is 14min, the value-added time percentage is 30%, and the non-value-added time percentage is 70%.
In some preferred embodiments, the management and control results generated by the task change information corresponding to the hook states and the task states can be sent to different users through an information receiving interface of the third-party platform.
The present embodiment also provides a JIRA system-based task management system, including:
an information acquisition module 1, configured to acquire, in real time, task change information when a task in a jiara system is changed;
the interface calling module 2 is used for triggering a network hook of the JIRA system based on the task change information and calling an information receiving interface of the custom server;
the first sending module 3 is used for sending the task change information to an information receiving interface of the custom server;
the analysis processing module 4 is used for the user-defined server to perform analysis processing according to a preset task time limit control rule and generate a corresponding control result;
and the second sending module 5 is used for sending the management and control result through a third-party platform.
In the present embodiment, the task management system and the JIRA system may be provided on the same terminal or on two terminals, respectively.
As shown in fig. 2, in this embodiment, a task monitoring module 6 is further included, which is configured to monitor hook status of a task in the JIRA system, and is capable of outputting a prompt signal when the hook status of the task changes, and the information obtaining module 1 obtains task change information after receiving the prompt signal. For example, when the hook status of the task is "updated" and the corresponding task status is changed from "to be developed" to "in execution", the task monitoring module 6 outputs a prompt signal to the information obtaining module 1, and the information obtaining module 1 obtains task change information in which the task status of the task is changed from "to be developed" to "in execution".
As shown in fig. 2, in this embodiment, the analysis processing module 4 may further be configured to set corresponding working time limit thresholds for different task states, and the analysis processing module 4 may include a changing unit (not shown), through which a user can modify the working time limit thresholds for different task states. The analysis processing module 4 adopts a plurality of working time limit thresholds as task implementation control rules to generate corresponding control results, for example, when the task change information received by the information receiving interface of the custom server indicates that the task state of the task changes from "not started" to "required scheme confirmation", the working time limit threshold of the task state of the "required scheme confirmation" is three days, when the time that the task stays in the "required scheme confirmation" task state exceeds three days, the analysis processing module 4 generates corresponding control results, the second sending module 5 sends the control results indicating that the task is overtime to the corresponding user through a third-party platform, and the third-party platform may be a communication platform such as a WeChat, a nail, a mailbox, and the like.
As shown in fig. 3, in this embodiment, the analysis processing module 4 further includes:
a determining unit 41, configured to determine the hook state when the task change information is received;
a timing unit 42 for determining a task state according to the hook state and the task change information, and starting timing;
and the processing unit 43 is configured to perform analysis processing according to the timing time to generate a control result.
In the present embodiment, the processing unit 43 generates the management and control result including:
when the timing time exceeds a working time limit threshold corresponding to the task state, generating a task state alarm signal as a control result;
and when the timing time does not exceed the working time limit threshold corresponding to the task state, taking the timing time and the corresponding task state as a control result.
In this embodiment, the process of the determination unit 41 determining the hook state includes:
when "create" information is included in the task change information, for example, when the value of webhookEvent in the task change information is jira: issue _ created, the determination unit 41 determines that the hook state is "created";
when the task change information includes "update" information, for example, when the value of webhookEvent in the task change information is jira: issue _ updated, the determination unit 41 determines that the hook state is "updated";
when "delete" information is included in the task change information, for example, when the value of webhookEvent in the task change information is JIRA: issue _ deleted, the determination unit 41 determines that the hook state is "deleted", that is, the user deletes the task in the JIRA system.
In this embodiment, the process of starting timing by the timing unit 42 according to the timing state specifically includes:
when the judging unit 41 judges that the hook state is "created", the timing unit 42 starts timing;
when the determination unit 41 determines that the hook state is "updated", the time counting unit 42 determines whether or not the task change information includes state update information, for example, whether or not the value of webhookEvent in the task change information includes change log and its is: if yes, starting timing; otherwise, timing is not carried out;
when the judging unit 41 judges that the hook state is "deleted", the counting unit 42 does not count time.
As shown in fig. 4, the present embodiment also proposes a JIRA system-based task management device 200, where the task management device 200 includes a processor 201 and a memory 202, the processor 201 is coupled to the memory 202, and the memory 202 stores program instructions, and when the program instructions stored in the memory 202 are executed by the processor 201, the task management method is implemented. The Processor 301 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; or a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component; the Memory 202 may include a Random Access Memory (RAM), and may further include a Non-Volatile Memory (Non-Volatile Memory), such as at least one disk Memory. The Memory 202 may also be an internal Memory of a Random Access Memory (RAM) type, and the processor 201 and the Memory 202 may be integrated into one or more independent circuits or hardware, such as: application Specific Integrated Circuit (ASIC). It should be noted that the computer program in the memory 302 can be implemented in the form of software functional units and stored in a computer readable storage medium when the computer program is sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention.
The present embodiment also provides a computer-readable storage medium, which stores computer instructions for causing a computer to execute the above task management method. The storage medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system or a propagation medium. The storage medium may also include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a Random Access Memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Optical disks may include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-RW), and DVD.
In summary, the present invention provides a method, a system, a device, and a storage medium for task management based on a JIRA system, which can time the latest working state time of a task when a new task is created in the JIRA system or the working state of the task changes, and send a reminder to a corresponding user when the time reaches a time threshold corresponding to the working state, so as to prevent the task from staying in the current working state for a long time, thereby shortening the development cycle of the task; and the time consumption of the task can be divided into value-added time and non-value-added time, and the time consumption of the task is refined to obtain a visual display image.
The above description is only a preferred embodiment of the present application and a description of the applied technical principle, and it should be understood by those skilled in the art that the scope of the present invention related to the present application is not limited to the technical solution of the specific combination of the above technical features, and also covers other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept, for example, the technical solutions formed by mutually replacing the above features with (but not limited to) technical features having similar functions disclosed in the present application.
Other technical features than those described in the specification are known to those skilled in the art, and are not described herein in detail in order to highlight the innovative features of the present invention.
Claims (10)
1. A method for task management based on a JIRA system, the method comprising:
acquiring task change information when a task in the JIRA system is changed in real time;
triggering a network hook of the JIRA system based on the task change information, and calling an information receiving interface of a custom server;
sending the task change information to an information receiving interface of the custom server;
the user-defined server analyzes and processes according to a preset task time limit control rule to generate a corresponding control result;
and sending the control result through a third-party platform.
2. The jita system-based task management method according to claim 1, wherein:
the preset task time limit control rule comprises the following steps: and setting corresponding working time limit thresholds aiming at different task states.
3. The jita system-based task management method according to claim 2, wherein: the user-defined server analyzes and processes according to a preset task time limit control rule, and the step of generating a corresponding control result comprises the following steps:
receiving the task change information and judging the hook state;
judging the task state according to the hook state and the task change information, and starting timing;
analyzing and processing according to the timing time, and generating a control result:
when the timing time exceeds the corresponding working time limit threshold value in the task state, generating a task state alarm signal as a control result;
and when the timing time does not exceed the corresponding working time limit threshold value in the task state, taking the timing time and the corresponding task state as a control result.
4. The JIRA system-based task management method according to claim 3, wherein: the step of receiving task change information and judging task state comprises the following steps:
when the task change information comprises 'create' information, the hook state is 'created';
when the task change information comprises the update information, the hook state is updated;
when the task change information includes "delete" information, the hook state is "deleted".
5. The JIRA system-based task management method according to claim 4, wherein: the step of judging the task state according to the hook state and the task change information and starting timing comprises the following steps:
when the hook state is 'created', timing is started;
when the hook state is 'updated', judging whether the task change information contains state update information:
if yes, judging the task state of the task and starting timing; otherwise, timing is not carried out;
when the hook status is "deleted", no timing is performed.
6. A jita system based task management system, the system comprising:
the information acquisition module is used for acquiring task change information when a task in the JIRA system is changed in real time;
the interface calling module is connected to the information acquisition module and used for triggering the network hook of the JIRA system based on task change information and calling an information receiving interface of the custom server;
the first sending module is connected to the information acquisition module and used for sending the task change information to an information receiving interface of the custom server;
the analysis processing module is connected to the first sending module and used for analyzing and processing the custom server according to a preset task time limit control rule and generating a corresponding control result;
and the second sending module is connected to the analysis processing module and used for sending the control result through a third-party platform.
7. The complete task management system of claim 6, further comprising:
a task monitoring module for monitoring tasks in the JIRA system;
and the threshold setting module is used for setting corresponding working time limit thresholds aiming at different task states.
8. The complete task management system of claim 7, wherein the analysis processing module comprises:
the judging unit is used for judging the hook state when the task change information is received;
the timing unit is connected to the judging unit and used for judging the task state according to the hook state and the task change information and starting timing;
the processing unit is connected to the timing unit and used for analyzing and processing according to the timing time and generating a control result:
when the timing time exceeds the working time limit threshold corresponding to the task state, the processing unit generates a task state alarm signal as a control result;
and when the timing time does not exceed the working time limit threshold corresponding to the task state, the processing unit takes the timing time and the corresponding task state as a control result.
9. A jitra system-based task management device comprising a processor coupled to a memory, the memory storing program instructions that, when executed by the processor, implement the jitra system-based task management method of any of claims 1-5.
10. A computer-readable storage medium characterized by comprising a program that, when run on a computer, causes the computer to execute the JIRA-system-based task management method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110042423.XA CN112783622A (en) | 2021-01-13 | 2021-01-13 | JIRA system-based task management method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110042423.XA CN112783622A (en) | 2021-01-13 | 2021-01-13 | JIRA system-based task management method, system, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112783622A true CN112783622A (en) | 2021-05-11 |
Family
ID=75755783
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110042423.XA Pending CN112783622A (en) | 2021-01-13 | 2021-01-13 | JIRA system-based task management method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783622A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485916A (en) * | 2021-06-21 | 2021-10-08 | 上海百胜软件股份有限公司 | Detection method, system, device and storage medium based on JIRA code construction |
| CN113485913A (en) * | 2021-06-10 | 2021-10-08 | 上海百胜软件股份有限公司 | Branch management method, system, equipment and storage medium |
| CN113495755A (en) * | 2021-06-29 | 2021-10-12 | 青岛海尔科技有限公司 | Information multi-dimensional analysis method and device |
| CN113516456A (en) * | 2021-08-06 | 2021-10-19 | 上海中通吉网络技术有限公司 | Task reminding system and method based on JIRA application |
| CN114819923A (en) * | 2022-06-28 | 2022-07-29 | 荣耀终端有限公司 | Work task reminding method and equipment |
| CN116204446A (en) * | 2023-05-06 | 2023-06-02 | 云账户技术(天津)有限公司 | Automatic test flow management method and device based on JIRA platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160134476A1 (en) * | 2014-11-07 | 2016-05-12 | Hannes Kerber | Method for controlling changes in a computer system |
| CN109684036A (en) * | 2018-12-17 | 2019-04-26 | 武汉烽火信息集成技术有限公司 | A kind of container cluster management method, storage medium, electronic equipment and system |
| CN109754145A (en) * | 2018-03-30 | 2019-05-14 | 比亚迪股份有限公司 | Project management method, device, system and the storage medium of task based access control |
| CN109901926A (en) * | 2019-01-25 | 2019-06-18 | 平安科技（深圳）有限公司 | Method, server and storage medium based on big data behavior scheduling application task |
| CN110708232A (en) * | 2019-09-12 | 2020-01-17 | 上海麦克风文化传媒有限公司 | Method and system for realizing JIRA message real-time notification |
| CN110728519A (en) * | 2019-09-27 | 2020-01-24 | 支付宝(杭州)信息技术有限公司 | Processing method and device for refused payment task and server |
-
2021
- 2021-01-13 CN CN202110042423.XA patent/CN112783622A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160134476A1 (en) * | 2014-11-07 | 2016-05-12 | Hannes Kerber | Method for controlling changes in a computer system |
| CN109754145A (en) * | 2018-03-30 | 2019-05-14 | 比亚迪股份有限公司 | Project management method, device, system and the storage medium of task based access control |
| CN109684036A (en) * | 2018-12-17 | 2019-04-26 | 武汉烽火信息集成技术有限公司 | A kind of container cluster management method, storage medium, electronic equipment and system |
| CN109901926A (en) * | 2019-01-25 | 2019-06-18 | 平安科技（深圳）有限公司 | Method, server and storage medium based on big data behavior scheduling application task |
| CN110708232A (en) * | 2019-09-12 | 2020-01-17 | 上海麦克风文化传媒有限公司 | Method and system for realizing JIRA message real-time notification |
| CN110728519A (en) * | 2019-09-27 | 2020-01-24 | 支付宝(杭州)信息技术有限公司 | Processing method and device for refused payment task and server |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485913A (en) * | 2021-06-10 | 2021-10-08 | 上海百胜软件股份有限公司 | Branch management method, system, equipment and storage medium |
| CN113485913B (en) * | 2021-06-10 | 2023-04-07 | 上海百胜软件股份有限公司 | Branch management method, system, equipment and storage medium |
| CN113485916A (en) * | 2021-06-21 | 2021-10-08 | 上海百胜软件股份有限公司 | Detection method, system, device and storage medium based on JIRA code construction |
| CN113495755A (en) * | 2021-06-29 | 2021-10-12 | 青岛海尔科技有限公司 | Information multi-dimensional analysis method and device |
| CN113495755B (en) * | 2021-06-29 | 2023-06-09 | 青岛海尔科技有限公司 | Information multidimensional analysis method and device |
| CN113516456A (en) * | 2021-08-06 | 2021-10-19 | 上海中通吉网络技术有限公司 | Task reminding system and method based on JIRA application |
| CN114819923A (en) * | 2022-06-28 | 2022-07-29 | 荣耀终端有限公司 | Work task reminding method and equipment |
| CN116204446A (en) * | 2023-05-06 | 2023-06-02 | 云账户技术(天津)有限公司 | Automatic test flow management method and device based on JIRA platform |
| CN116204446B (en) * | 2023-05-06 | 2023-08-18 | 云账户技术(天津)有限公司 | Automatic test flow management method and device based on JIRA platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112783622A (en) | JIRA system-based task management method, system, device and storage medium | |
| CN110191094B (en) | Abnormal data monitoring method and device, storage medium and terminal | |
| CN109583758B (en) | Early warning rule correction method and device of monitoring system and computer equipment | |
| CN112817843B (en) | Project management method and system | |
| CN108134708B (en) | Method and device for monitoring third-party interface | |
| CN111522711B (en) | Data monitoring processing system, method, execution end, monitoring end and electronic equipment | |
| CN109767509A (en) | Equipment operation and maintenance management method and device, readable medium and electronic equipment | |
| CN110609780A (en) | Data monitoring method and device, electronic equipment and storage medium | |
| CN110764988A (en) | Alarm method, device and system | |
| CN110674149B (en) | Service data processing method and device, computer equipment and storage medium | |
| CN115964272A (en) | Transaction data automatic testing method, device, equipment and readable storage medium | |
| CN111143325A (en) | Data acquisition monitoring method, monitoring device and readable storage medium | |
| CN111475556A (en) | Data acquisition method, data acquisition equipment, server and readable storage medium | |
| CN113849330A (en) | Method, equipment and storage medium for monitoring and analyzing application fault reasons | |
| CN117670128A (en) | Data processing method and device | |
| CN107357703B (en) | Terminal application power consumption detection method and server | |
| CN112631808B (en) | Data synchronization method, device, electronic equipment and storage medium | |
| CN110633165B (en) | Fault processing method, device, system server and computer readable storage medium | |
| CN114549193A (en) | List screening method, apparatus, device, storage medium and program product | |
| CN110502404B (en) | Early warning processing method based on data management platform and related equipment | |
| CN110413516B (en) | Method and device for identifying slow SQL codes and electronic equipment | |
| CN112532485A (en) | Service monitoring method and device, electronic equipment and readable storage medium | |
| CN108280090B (en) | Intelligent feedback system and method | |
| CN112837517A (en) | Alarm message processing method and device, server, client and alarm system | |
| CN114168440A (en) | Performance test method, device, equipment and medium for metadata acquisition |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |