CN110543325A

CN110543325A - data processing method and device

Info

Publication number: CN110543325A
Application number: CN201910753682.6A
Authority: CN
Inventors: 李鹏飞; 李严桵; 李宁馨; 刘宪伟
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2019-08-15
Filing date: 2019-08-15
Publication date: 2019-12-06

Abstract

The embodiment of the invention provides a data processing method and device, and relates to the field of software development. The embodiment of the invention can complete corresponding processing by selecting the target interface from the four preset interfaces when the preset data in the JIRA system needs to be subjected to preset processing. And further, the automatic processing of the data is realized, and the working efficiency is improved. The method comprises the following steps: a processing request is obtained. And selecting a target interface from the four preset interfaces according to the type of preset processing. And performing preset processing on preset data in the JIRA system by using the target interface. The invention is applied to data processing.

Description

Data processing method and device

Technical Field

The present invention relates to the field of software development, and in particular, to a data processing method and apparatus.

Background

JIRA is a project and practice tracking tool produced by atlas company, and is widely applied to the working fields of defect tracking, customer service, demand collection, process approval, task tracking, project tracking, agile management and the like. In the JIRA system, various types of data can be collated and stored.

Currently, when data in the JIRA system is maintained, the corresponding maintenance work is mainly done manually by a user. For example, when data in the JIRA system needs to be updated, a user needs to perform a corresponding operation on a client interface of the JIRA system to complete the task of updating the data.

When data in another system needs to be imported into the jia system or data in the jia system needs to be imported into another data system, if the amount of data involved is large, the manual data importing method is very troublesome, and the user experience is seriously affected.

disclosure of Invention

Embodiments of the present invention provide a data processing method and apparatus, where when preset data in a jiar system needs to be subjected to preset processing, a target interface is selected from four preset interfaces to complete corresponding processing. And further, the automatic processing of the data is realized, and the working efficiency is improved.

In a first aspect, the present invention provides a data processing method, including: acquiring a processing request; the processing request is used for performing preset processing on preset data in the JIRA system; after the processing request is obtained, selecting a target interface from four preset interfaces according to the type of the preset processing; the four preset interfaces respectively include interfaces for performing query processing, update processing, addition processing, and deletion processing on the preset data in the JIRA system; and after the target interface is selected from the four interfaces, performing the preset processing on the preset data in the JIRA system by using the target interface.

in a second aspect, an embodiment of the present invention provides a data processing apparatus, including: an acquisition unit configured to acquire a processing request; the processing request is used for performing preset processing on preset data in the JIRA system; the processing unit is used for selecting a target interface from the four preset interfaces according to the type of the preset processing after the acquisition unit acquires the processing request; the four preset interfaces respectively include interfaces for performing query processing, update processing, addition processing, and deletion processing on the preset data in the JIRA system; the processing unit is further configured to perform the preset processing on the preset data in the JIRA system by using the target interface after the processing unit selects the target interface from the four interfaces.

In a third aspect, an embodiment of the present invention provides another data processing apparatus, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the data processing device runs, the processor executes the computer execution instructions stored in the memory so as to enable the data processing device to execute the data processing method provided by the first aspect.

in a fourth aspect, an embodiment of the present invention provides a computer storage medium, which includes instructions that, when executed on a data processing apparatus, cause the data processing apparatus to execute a data processing method provided in the first aspect.

In a fifth aspect, an embodiment of the present invention provides a computer program product including instructions, which, when run on a computer, causes the computer to execute the data processing method according to the first aspect and any one of the implementation manners of the first aspect.

the data processing method and the data processing device provided by the embodiment of the invention can complete corresponding processing by selecting the target interface from the four preset interfaces when preset processing is required to be performed on preset data in the JIRA system. And further, the automatic processing of the data is realized, and the working efficiency is improved.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.

fig. 1 is a flowchart illustrating a data processing method according to an embodiment of the present invention;

fig. 2 is a second schematic flowchart of a data processing method according to an embodiment of the present invention;

fig. 3 is a third schematic flowchart of a data processing method according to an embodiment of the present invention;

fig. 4 is a fourth schematic flowchart of a data processing method according to an embodiment of the present invention;

Fig. 5 is a fifth flowchart illustrating a data processing method according to an embodiment of the present invention;

fig. 6 is a sixth schematic flowchart of a data processing method according to an embodiment of the present invention;

Fig. 7 is a seventh schematic flowchart of a data processing method according to an embodiment of the present invention;

Fig. 8 is an eighth schematic flowchart of a data processing method according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present invention;

Fig. 10 is a second schematic structural diagram of a data processing apparatus according to an embodiment of the present invention;

fig. 11 is a third schematic structural diagram of a data processing apparatus according to an embodiment of the present invention.

Detailed Description

The data processing method and apparatus provided in the present application will be described in detail below with reference to the accompanying drawings.

The terms "first" and "second", etc. in the description and drawings of the present application are used for distinguishing between different objects and not for describing a particular order of the objects.

furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The term "and/or" as used herein includes the use of either or both of the two methods.

in the description of the present application, the meaning of "a plurality" means two or more unless otherwise specified.

First, technical terms involved in the embodiments of the present application are explained:

JIRA, which is a project and practice tracking tool produced by atlas company, is widely applied to the working fields of defect tracking, customer service, demand collection, process approval, task tracking, project tracking, agile management and the like. The invention selects the target interface from the four preset interfaces to be matched and connected with the JIRA system, thereby realizing the automatic processing of data.

the user story is a function desired by the user from the perspective of the user. A good user story consists of three elements: 1. role: who wants to use this function. 2. Moving: what function or objective needs to be accomplished. 3. Commercial value: why this function is needed, what value this function brings. I.e., a concise and complete presentation of the requirements. Specifically, in the method and the application scenario provided by the embodiment of the present invention, the user story may be specifically a segment of preset data recorded with a "role", an "activity", and a "commercial value".

the steward story, epic, typically takes multiple sprints to develop and test to complete the final delivery. It is usually larger in scope and less in detail description, and epic is larger in granularity, and usually needs to be split into a plurality of smaller data before team development. It can be understood as a space, which can be summarized as a requirement of a sentence. Specifically, in the method and the application scenario provided by the embodiment of the present invention, the story of the historical poem may be specifically a piece of preset data recorded with "demand".

the invention principle of the invention is as follows: in order to achieve reasonable division of labor and efficient communication among teams, data interaction among different systems is increasingly important. Particularly, in the data transmission between the self-owned system such as the project management system and the JIRA system, it is urgently required to find a method capable of automatically processing and solving the data in the JIRA system and improving the work efficiency.

the first embodiment is as follows:

based on the inventive principle, the embodiment of the invention provides a data processing method. As shown in fig. 1, the method specifically includes:

S101, acquiring a processing request.

A processing request for performing preset processing on preset data in the JIRA system.

Specifically, the preset data includes a user story, a stressful story, a bug, an improvement, a new feature, a task, a sub-task, a technical task, a testcase, and a testsuite, and for different preset data, the method provided by the embodiment of the present invention may be used to operate the jiara system, which is not specifically limited herein.

the type of the preset treatment specifically comprises the following steps: and performing query processing, updating processing, adding processing and deleting processing on preset data in the JIRA system.

and S105, after the processing request is obtained, selecting a target interface from the four preset interfaces according to the type of preset processing.

The four kinds of preset interfaces respectively include interfaces for performing query processing, update processing, addition processing, and deletion processing on preset data in the JIRA system.

Specifically, after the processing request is obtained, in the embodiment of the present invention, according to the type of the preset process corresponding to the processing request, a target interface is selected from four interfaces for performing query processing, update processing, addition processing, and deletion processing on preset data in the JIRA system, so as to perform subsequent operations. The target interface includes an interface for performing query processing, update processing, addition processing, and deletion processing on preset data in the JIRA system.

For example, if the processing request is a request indicating to delete a certain piece of data, the deletion interface is selected from four preset interfaces.

In an implementation manner of the present invention, S105 specifically includes: and inquiring a target interface from the JIRA official website according to the type of the preset processing.

Specifically, in the embodiment of the present invention, after the preset request is received, the target interface is acquired from the official document in the JIRA official website, so as to perform the subsequent steps.

for example, when the processing request is a request indicating that a certain piece of data is to be subjected to deletion processing, a deletion interface may be acquired from an official document in the JIRA official website and called to perform a deletion operation on preset data in the JIRA system.

according to the embodiment of the invention, the target interface can be obtained by accessing the official website, so that developers are not required to independently develop the interface, and the called interface version can be ensured to be the latest version.

And S110, after selecting the target interface from the four interfaces, performing preset processing on preset data in the JIRA system by using the target interface.

Specifically, different interfaces are used to perform different processing on preset data in the JIRA system. The target interface can realize the automatic processing of the processing request, and meanwhile, the interaction between the system where the processing request is located and the JIRA system can be realized, thereby improving the working efficiency.

Illustratively, when the embodiment of the present invention is applied to a preset data processing apparatus, an interaction process between the data processing apparatus and the JIRA system is as shown in fig. 2, and specifically includes: s201, selecting a query interface according to a processing request for performing query processing on preset data in the JIRA system. S202, query processing is carried out on preset data in the JIRA system.

in one implementation of the invention, a JIRA system includes a JIRA client and a JIRA server. The JIRA client is used to log into the JIRA server. The JIRA server is used to store preset data in the JIRA system. S110 performs preset processing on preset data in the JIRA system by using the target interface, specifically including step S110 a:

S110a, connecting the jitra client using the target interface, so as to perform the preset processing on the preset data in the jitra system after the jitra client logs in the jitra server.

Specifically, the jitra system includes a jitra client and a jitra server. The embodiment of the invention logs in the JIRA server through the JIRA client. The JIRA server stores therein a plurality of pieces of data, and various types of data in the JIRA server can be accessed by the JIRA client.

in an implementation manner of the present invention, the logging in of the JIRA client to the JIRA server specifically includes:

The JIRA client logs in the JIRA server by adopting a timeout retransmission mechanism and a singleton mode.

By logging in the JIRA server through a timeout retransmission mechanism and a singleton mode, the problem of limitation of logging times of the JIRA server can be solved, and meanwhile, the server overhead caused by logging in the JIRA server for multiple times is reduced.

In an implementation manner of the present invention, the performing preset processing on preset data in the jiara system by using the target interface specifically includes: and performing preset processing on a preset Shih story in the JIRA system by using the target interface.

After the preset story of the preset historical poetry in the JIRA system is preset by using the target interface, the method provided by the embodiment of the invention further comprises the following steps: and correspondingly processing the user story included in the preset steward story.

in particular, a steward story may have multiple user stories. When accessing the JIRA system through the target interface, the embodiment of the invention can process the preset steward in the JIRA system first and then correspondingly process the user story in the JIRA system. Meanwhile, when a new user story is added each time, a new steward corresponding to the user story is added at first. And after the new user is added, associating the new story of the historical poems with the new story of the user.

In one implementation manner of the present invention, after performing the preset processing on the preset data in the JIRA system by using the target interface, the method further includes:

The JIRA client logs out from the JIRA server.

Specifically, after the preset data processing in the JIRA system is completed, it needs to be checked out from the JIRA server. Different users need different user names and passwords when logging in, and the operable types and contents of different users are different. The log-out is for the security of the client to prevent illegal users or users with non-authorized rights from processing the preset data.

Illustratively, as shown in FIG. 3. The JIRA system includes a JIRA client and a JIRA server. S301, a processing request for performing addition processing on preset data in the JIRA system is connected to the JIRA client through an addition interface. S302, the JIRA client logs in the JIRA server. And S303, finishing login. S304, add processing is performed on the preset data in the JIRA server. S305, the addition processing is completed. S306, the JIRA client logs out from the JIRA server.

Example two:

Based on the first embodiment, an embodiment of the present invention provides a data processing method. As shown in fig. 4, the method specifically includes:

S101, acquiring a processing request.

s102, after the processing request is acquired, the type of the processing request is judged.

the types of the processing requests comprise inquiry requests, updating requests, adding requests and deleting requests.

specifically, the query request is used to perform query processing on preset data in the JIRA system. The update request is used for update processing of preset data in the JIRA system. The addition request is used for addition processing of preset data in the JIRA system. The deletion request is used to perform deletion processing of preset data in the JIRA system.

s103, after the type of the processing request is judged, whether preset data in the JIRA system exists in the local database or not is judged.

a local database for storing a backup of preset data in the JIRA system.

Specifically, since the local database stores preset data that is consistent with the preset data in the JIRA system, it is possible to determine whether preset data exists in the JIRA system by determining whether preset data exists in the local database.

On the basis of the first embodiment, in an implementation manner provided by the embodiment of the present invention, the step S105 of selecting the target interface from the four preset interfaces according to the type of the preset processing includes the step S105 a:

S105a, if the type of the processing request is one of an update request and a delete request, and preset data in the JIRA system exists in the local database, selecting a target interface from the four preset interfaces.

Specifically, if the preset data in the JIRA system exists in the local database, it is indicated that the preset data exists in the JIRA system. When preset data exists in the JIRA system, the update request and deletion processing can be performed on the preset data in the JIRA system, and then the corresponding target interface is selected for processing.

On the basis of the first embodiment, in an implementation manner provided by the embodiment of the present invention, the step S105 selects a target interface from four preset interfaces according to a type of preset processing, and specifically includes the step S105 b:

And S105, 105b, if the type of the processing request is the adding request and preset data in the JIRA system does not exist in the local database, selecting a target interface from the four preset interfaces.

specifically, if the preset data in the JIRA system does not exist in the local database, it is indicated that the preset data does not exist in the JIRA system. When preset data does not exist in the JIRA system, the preset data in the JIRA system may be subjected to addition processing, and then a corresponding target interface may be selected for processing.

After determining whether preset data in the JIRA system exists in the local database, the method provided in the embodiment of the present invention further includes step S104:

and S104, if the type of the processing request is one of an updating request and a deleting request and preset data in the JIRA system does not exist in the local database, returning a first preset processing result.

a first preset processing result for indicating that preset data does not exist in the JIRA system.

Specifically, if the preset data in the JIRA system does not exist in the local database, it means that the preset data does not exist in the JIRA system. When preset data does not exist in the JIRA system, the update processing and the deletion processing cannot be performed, and a first preset processing result, that is, a result that the preset data does not exist in the JIRA system, is returned from the local database.

For example, as shown in fig. 5, in S401, after the update request or the delete request is obtained, it is determined whether preset data exists in the local database. S402, if preset data exist in the local database, selecting a target interface from the four preset interfaces. And S403, if the preset data do not exist in the local database, returning a first preset processing result.

After determining whether preset data in the JIRA system exists in the local database, the method provided in the embodiment of the present invention further includes step S106:

S106: and if the type of the processing request is an adding request and preset data in the JIRA system exists in the local database, returning a second preset processing result.

A second preset processing request for indicating that preset data already exists in the JIRA system.

Specifically, if preset data in the JIRA system exists in the local database, it is indicated that preset data also exists in the JIRA system. When the preset data exists in the JIRA system, the second preset processing result, that is, the result of the preset data existing in the JIRA system, is returned from the local database without performing the addition processing.

For example, as shown in fig. 6, in step S501, after the adding request is obtained, it is determined whether preset data exists in the local database. And S502, if the local database does not have preset data, selecting a target interface from the four preset interfaces. And S503, if the preset data exist in the local database, returning a second preset processing result.

Example three:

Based on the first embodiment, an embodiment of the present invention provides a data processing method. As shown in fig. 7, the method specifically includes:

S101, acquiring a processing request.

On the basis of the first embodiment, in an implementation manner provided by the embodiment of the present invention, the step S105 of selecting a target interface from four preset interfaces according to a type of preset processing further includes the step S105 c:

S105, 105c, if the type of the processing request is one of an updating request, an adding request and a deleting request, selecting a target interface from the four preset interfaces according to the type of preset processing.

Illustratively, if the type of the processing request is an update request, an update interface is selected from four preset interfaces according to the type of the preset processing.

In one implementation manner of the embodiment of the present invention, after determining the type of the processing request, the method further includes steps S107 to S108:

S107, if the type of the processing request is the query request, whether preset data in the JIRA system exists in the local database is judged.

Specifically, since the local database stores preset data that is consistent with the preset data in the JIRA system, when the preset data exists in the JIRA system, the preset data also exists in the local database. When the type of the processing request is a query request, query processing may be directly performed on the local database without performing query processing on the JIRA system. The number of unnecessary access to the JIRA system is reduced, and the working efficiency is improved.

and S108, if the preset data in the JIRA system exists in the local database, returning a query result from the local database.

Specifically, if preset data in the JIRA system exists in the local database, it is indicated that the preset data exists in the JIRA system, and the preset data obtained by directly returning the query from the local database is only required to be equivalent to the preset data obtained by returning the query from the JIRA system. Unnecessary access to the JIRA system is reduced, meanwhile, the result corresponding to the query request can be directly obtained from the local database, and the working efficiency is improved. If the preset data in the JIRA system does not exist in the local database, the fact that the preset data does not exist in the JIRA system is indicated, and a result that the preset data corresponding to the query request does not exist is directly returned from the local database, which is equivalent to a result that the preset data corresponding to the query request does not exist from the JIRA system.

For example, as shown in fig. 8, S601 queries the local database according to the obtained query request. And S602, if the preset data exist in the local database, returning a query result. And S603, if the preset data does not exist in the local database, returning a result that the preset data does not exist.

In one implementation manner of the present invention, after performing the preset processing on the preset data in the JIRA system by using the target interface, the method further includes step S111:

And S111, synchronizing the preset data in the JIRA system to a local database by using an interface which is used for inquiring the preset data in the JIRA system and is selected from the four preset interfaces.

Specifically, after each time of performing the preset processing on the preset data in the JIRA system, the query interface is used to query whether the preset data in the JIRA system has changed. If the processing request is a query request, the preset data in the JIRA system is not changed, and the query processing does not update the local database because the preset data in the JIRA system has been synchronized to the local database after the last preset processing. And when the processing request is an update, deletion or addition request, updating, deleting and adding the preset data in the JIRA system, inquiring that the preset data in the JIRA system is changed by using the inquiry interface, and synchronizing the preset data in the JIRA system into the local database after processing the preset user of the JIRA system each time in order to ensure the consistency of the local database and the data in the JIRA system.

In one implementation of the present invention, the local database may not be updated each time the preset data in the JIRA system is processed, and when the local database is not updated each time the preset data in the JIRA system is processed, the method further includes:

and synchronizing the preset story in the JIRA system into a local database by utilizing an interface for inquiring data in the JIRA system in the four preset interfaces at intervals of preset time.

Specifically, the query interface is used to update the local database at intervals, so as to ensure that the data in the local database is consistent with the data in the JIRA system.

Illustratively, the predetermined time includes 30 minutes, 2 hours. The local database is updated every 2 hours, the data in the JIRA system is synchronized to the local database, the data in the local database is not required to be updated every time the data of the JIRA system is updated, and the working efficiency is improved.

Example four:

An embodiment of the present invention provides a data processing apparatus, configured to execute the foregoing data processing method. Fig. 9 is a schematic diagram of a possible structure of a data processing apparatus 70 according to an embodiment of the present invention. Specifically, the data processing device 70 includes: an acquisition unit 701 and a processing unit 702. Wherein,

an obtaining unit 701 is configured to obtain a processing request. A processing request for performing preset processing on preset data in the JIRA system.

The processing unit 702 is configured to select a target interface from the four preset interfaces according to a type of preset processing after the obtaining unit 701 obtains the processing request. The four kinds of preset interfaces respectively include interfaces for performing query processing, update processing, addition processing, and deletion processing on preset data in the JIRA system.

The processing unit 702 is further configured to perform preset processing on preset data in the JIRA system by using the target interface after the processing unit 702 selects the target interface from the four interfaces.

optionally, the apparatus further comprises an output unit 703.

The processing unit 702 also determines the type of the processing request after the acquisition unit 701 acquires the processing request. The types of the processing requests comprise inquiry requests, updating requests, adding requests and deleting requests.

the processing unit 702 is specifically configured to select a target interface from the four preset interfaces according to a type of preset processing if the type of the processing request is one of an update request, an addition request, and a deletion request.

The processing unit 702 is further configured to, after the processing unit 702 determines the type of the processing request, determine whether preset data in the JIRA system exists in the local database if the type of the processing request is an inquiry request. A local database for storing a backup of preset data in the JIRA system.

an output unit 703 is configured to, after the processing unit 702 determines whether the preset data in the JIRA system exists in the local database, return a query result from the local database if the preset data in the JIRA system exists in the local database.

optionally, the processing unit 702 is further configured to determine whether preset data in the JIRA system exists in the local database after the processing unit 702 determines the type of the processing request.

the processing unit 702 is further configured to, if the type of the processing request is one of an update request and a delete request, and preset data in the JIRA system exists in the local database, select a target interface from the four preset interfaces.

The output unit 703 is further configured to, after the processing unit 702 determines whether the preset data in the JIRA system exists in the local database, return a first preset processing result if the type of the processing request is one of an update request and a delete request, and the preset data in the JIRA system does not exist in the local database. A first preset processing result for indicating that preset data does not exist in the JIRA system.

The processing unit 702 is further configured to select a target interface from the four preset interfaces if the type of the processing request is an addition request and preset data in the jiar system does not exist in the local database.

The output unit 703 is further configured to, after the processing unit 702 determines whether the preset data in the JIRA system exists in the local database, return a second preset processing result if the type of the processing request is an addition request and the preset data in the JIRA system exists in the local database. A second preset processing result for indicating that preset data already exists in the JIRA system.

optionally, the processing unit 702 is further configured to synchronize the preset data in the JIRA system into the local database by using an interface, which is used for querying the preset data in the JIRA system, of the four preset interfaces after the processing unit 702 processes the preset data in the JIRA system by using the target interface.

Optionally, the JIRA system includes a JIRA client and a JIRA server. The JIRA client is used to log into the JIRA server. The JIRA server is used to store preset data in the JIRA system.

The processing unit 702 is further specifically configured to connect the jitra client with the target interface, so as to perform preset processing on preset data in the jitra system after the jitra client logs in the jitra server.

In the embodiment of the present application, the data processing apparatus may be divided into the functional modules or the functional units according to the above method examples, for example, each functional module or functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module or a functional unit. The division of the modules or units in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

fig. 10 shows a schematic diagram of a possible configuration of the data processing device according to the above-described exemplary embodiment, in the case of an integrated unit. The data processing device 80 includes: a processing module 801, a communication module 802 and a storage module 803. The processing module 801 is used for controlling and managing the actions of the data processing apparatus 80, for example, the processing module 801 is used for supporting the data processing apparatus 80 to execute the processes S101 to S110 in fig. 1. The communication module 802 is used to support communication of the data processing apparatus 80 with other entities. The storage module 803 is used to store program codes and data of the data processing apparatus.

The processing module 801 may be a processor or a controller, such as a Central Processing Unit (CPU), a general purpose processor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module 802 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 803 may be a memory.

when the processing module 801 is a processor as shown in fig. 11, the communication module 802 is a transceiver as shown in fig. 11, and the storage module 803 is a memory as shown in fig. 11, the data processing apparatus according to the embodiment of the present invention may be the following data processing apparatus 90.

Referring to fig. 11, the data processing apparatus 90 includes: a processor 901, a transceiver 902, a memory 903, and a bus 904.

The processor 901, the transceiver 902 and the memory 903 are connected to each other through a bus 904; the bus 904 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

processor 901 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application-Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to control the execution of programs in accordance with the present invention.

The Memory 903 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 903 is used for storing application program codes for implementing the present invention, and the processor 901 controls the execution. The transceiver 902 is configured to receive content input by an external device, and the processor 901 is configured to execute application program codes stored in the memory 903, thereby implementing a data processing method provided in an embodiment of the present invention.

it should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the invention are all or partially effected when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A data processing method, comprising:

Acquiring a processing request; the processing request is used for performing preset processing on preset data in the JIRA system;

After the processing request is obtained, selecting a target interface from four preset interfaces according to the type of the preset processing; the four preset interfaces respectively include interfaces for performing query processing, update processing, addition processing, and deletion processing on the preset data in the JIRA system;

And after the target interface is selected from the four interfaces, performing the preset processing on the preset data in the JIRA system by using the target interface.

2. The data processing method of claim 1, wherein the method further comprises:

After the processing request is obtained, judging the type of the processing request; the types of the processing requests comprise inquiry requests, updating requests, adding requests and deleting requests;

Selecting a target interface from four preset interfaces according to the type of the preset processing, specifically comprising:

If the type of the processing request is one of an updating request, an adding request and a deleting request, selecting the target interface from the four preset interfaces according to the type of the preset processing;

After the determining the type of the processing request, the method further comprises:

if the type of the processing request is a query request, judging whether the preset data in the JIRA system exists in a local database; the local database is used for storing the backup of the preset data in the JIRA system;

And if the preset data in the JIRA system exists in the local database, returning a query result from the local database.

3. The data processing method of claim 2, wherein after said determining the type of the processing request, the method further comprises:

Judging whether the preset data in the JIRA system exists in the local database;

selecting a target interface from the four preset interfaces according to the type of the preset processing, which specifically comprises:

If the type of the processing request is one of an update request and a delete request, and the preset data in the JIRA system exists in the local database, selecting the target interface from the four preset interfaces;

After the determining whether the preset data in the JIRA system exists in the local database, the method further includes:

If the type of the processing request is one of an updating request and a deleting request, and the preset data in the JIRA system does not exist in the local database, returning a first preset processing result; the first preset processing result is used for indicating that the preset data does not exist in the JIRA system.

4. The data processing method of claim 2, wherein after said determining the type of the processing request, the method further comprises:

if the type of the processing request is an addition request and the preset data in the JIRA system does not exist in the local database, selecting the target interface from the four preset interfaces;

If the type of the processing request is an adding request and the preset data in the JIRA system exists in the local database, returning a second preset processing result; the second preset processing result is used for indicating that the preset data already exists in the JIRA system.

5. The data processing method according to claim 3 or 4, wherein after said pre-setting processing of the pre-set data in the JIRA system using the target interface, the method further comprises:

Synchronizing the preset data in the JIRA system to the local database by using an interface for querying the preset data in the JIRA system from among the four preset interfaces.

6. the data processing method of any of claims 1-4, wherein the JIRA system comprises a JIRA client and a JIRA server; the JIRA client is used for logging in the JIRA server; the JIRA server is used for storing the preset data in the JIRA system;

the performing, by using the target interface, preset processing on preset data in the jiara system specifically includes:

and connecting the JIRA client by using the target interface so as to perform preset processing on preset data in the JIRA system after the JIRA client logs in the JIRA server.

7. A data processing apparatus, comprising:

An acquisition unit configured to acquire a processing request; the processing request is used for performing preset processing on preset data in the JIRA system;

The processing unit is used for selecting a target interface from the four preset interfaces according to the type of the preset processing after the acquisition unit acquires the processing request; the four preset interfaces respectively include interfaces for performing query processing, update processing, addition processing, and deletion processing on the preset data in the JIRA system;

The processing unit is configured to perform the preset processing on the preset data in the JIRA system by using the target interface after the processing unit selects the target interface from the four interfaces.

8. the data processing apparatus of claim 7, wherein the apparatus further comprises an output unit;

The processing unit is further configured to determine the type of the processing request after the obtaining unit obtains the processing request; the types of the processing requests comprise inquiry requests, updating requests, adding requests and deleting requests;

The processing unit is specifically configured to select the target interface from the four preset interfaces according to the type of the preset processing if the type of the processing request is one of an update request, an addition request, and a deletion request;

The processing unit is further configured to, after the processing unit determines the type of the processing request, determine whether the preset data in the JIRA system exists in a local database if the type of the processing request is an inquiry request; the local database is used for storing the backup of the preset data in the JIRA system;

the output unit is configured to, after the processing unit determines whether the preset data in the JIRA system exists in the local database, return a query result from the local database if the preset data in the JIRA system exists in the local database.

9. The data processing apparatus of claim 8,

The processing unit is further configured to determine whether the preset data in the JIRA system exists in the local database after the processing unit determines the type of the processing request;

The processing unit is specifically configured to select the target interface from the four preset interfaces if the type of the processing request is one of an update request and a delete request, and the preset data in the JIRA system exists in the local database;

The output unit is further configured to, after the processing unit determines whether the preset data in the JIRA system exists in the local database, return a first preset processing result if the type of the processing request is one of an update request and a delete request and the preset data in the JIRA system does not exist in the local database; the first preset processing result is used for indicating that the preset data does not exist in the JIRA system.

10. The data processing apparatus of claim 8,

the processing unit is specifically configured to select the target interface from the four preset interfaces if the type of the processing request is an addition request and the preset data in the JIRA system does not exist in the local database;

the output unit is further configured to, after the processing unit determines whether the preset data in the JIRA system exists in the local database, return a second preset processing result if the type of the processing request is an addition request and the preset data in the JIRA system exists in the local database; the second preset processing result is used for indicating that the preset data already exists in the JIRA system.

11. the data processing apparatus of claim 9 or 10,

The processing unit is further configured to synchronize the preset data in the JIRA system to the local database by using an interface, which is used for querying the preset data in the JIRA system, of the four preset interfaces after the preset processing is performed on the preset data in the JIRA system by the processing unit using the target interface.

12. The data processing apparatus of any of claims 7-10, wherein the jita system comprises a jita client and a jita server; the JIRA client is used for logging in the JIRA server; the JIRA server is used for storing the preset data in the JIRA system;

the processing unit is specifically further configured to connect the JIRA client with the target interface, so as to perform preset processing on preset data in the JIRA system after the JIRA client logs in the JIRA server.

13. a data processing apparatus, characterized in that the data processing apparatus comprises: a processor, a communication interface, and a memory; wherein the memory is used for storing one or more programs, the one or more programs comprising computer executable instructions, which when run by the data processing apparatus, are executed by the processor, the computer executable instructions stored by the memory, so as to cause the data processing apparatus to perform the data processing method of any one of claims 1 to 6.

14. a computer-readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform the data processing method of any one of claims 1 to 6.