Described herein is a computer implemented method. The method comprises receiving, by an issue tracking system, a deployment update from a deployment system which includes deployment information in respect of one or more issues maintained by the issue tracking system. The method further comprises associating one or more issues maintained by the issue tracking system with deployment information by identifying the one or more issues to which the deployment information in the deployment update relates, extracting the deployment information from the deployment update, and associating the deployment information with each of the identified issues.

An industrial integrated development environment (IDE) provides a development framework for designing, programming, and configuring multiple aspects of an industrial automation system using a common design environment and data model. Projects creating using embodiments of the IDE system can be built on an object-based model rather than, or in addition to, a tag-based architecture. To this end, the IDE system can support the use of automation objects that serve as building blocks for this object-based development structure. Project data models defining collections of automation objects and their functional relationships can be stored in a model library for selective inclusion in system projects.

Described herein is an issue tracking system (ITS) comprising: one or more processors; one or more non-transitory computer-readable storage media storing sequences of instructions which, when executed by the one or more processors, cause the one or more processors to: render a user interface including a plurality of user interface elements each listing an external service from which the ITS can receive external objects and associate the received external object with one or more issues maintained by the ITS; determine, in response to a user interaction with one of the user interface elements, whether an issue maintained by the ITS is associated with an external object received from the listed external service; and render within the ITS, a user interface for an application marketplace, the application marketplace user interface including a listing of one or more integration applications that, once installed, connect the listed external service to the ITS and associate external objects received from the listed external service with one or more issues maintained by the ITS.

Translations between versions of data object schemas may be performed between data object producers and data object consumers. A request to update a data object may be an update according to an additional version of a schema applicable to the data object from an existing version of a schema. The data object may be provided by one component of a distributed system. A trigger event may be detected to send the data object to a different component of the distributed system. The data object may be translated from the additional version to the existing version and sent to the different component.

A system and method for feature switching in software applications. A feature switching action (FSA) is received and at least one user device is identified based on the received FSA. At least one feature switching instruction (FSI) is generated based on the received FSA and the FSI is sent to at least one of the identified user devices. A feature switching instruction response (FSIR) is received from each user device that received a FSI and a feature switching action response (FSAR) is generated based on the received FSIRs.

Described herein is a computer implemented method. The method comprises receiving, by an issue tracking system, a deployment update from a deployment system which includes deployment information in respect of one or more issues maintained by the issue tracking system. The method further comprises associating one or more issues maintained by the issue tracking system with deployment information by identifying the one or more issues to which the deployment information in the deployment update relates, extracting the deployment information from the deployment update, and associating the deployment information with each of the identified issues.

Provided methods and systems allow dynamic rendering of a reflexive questionnaire based on a modifiable spreadsheet for users with little to no programming experience and knowledge. Some methods comprise receiving a modifiable spreadsheet with multiple rows, each row comprising rendering instructions for a reflexive questionnaire from a first computer, such as a data type cell, statement cell, logic cell, and a field identifier; rendering a graphical user interface, on a second computer, comprising a label and an input element corresponding to the rendering instructions of a first row of the spreadsheet; receiving an input from the second computer; evaluating the input against the logic cell of the spreadsheet; in response to the input complying with the logic cell of the spreadsheet, dynamically rendering a second label and a second input element to be displayed on the graphical user interface based on the logic of the first row.

Described herein is an issue tracking system (ITS) comprising: one or more processors; one or more non-transitory computer-readable storage media storing sequences of instructions which, when executed by the one or more processors, cause the one or more processors to: render a user interface including a plurality of user interface elements each listing an external service from which the ITS can receive external objects and associate the received external object with one or more issues maintained by the ITS; determine, in response to a user interaction with one of the user interface elements, whether an issue maintained by the ITS is associated with an external object received from the listed external service; and render within the ITS, a user interface for an application marketplace, the application marketplace user interface including a listing of one or more integration applications that, once installed, connect the listed external service to the ITS and associate external objects received from the listed external service with one or more issues maintained by the ITS.

A method for managing a business. At least one relationship is determined between N business components (B.sub.1, B.sub.2, . . . , B.sub.N) and respective N costs (C.sub.1, C.sub.2, . . . , C.sub.N) and respective N values (V.sub.1, V.sub.2, . . . , V.sub.N) pertaining to the N business components. The N business components are a subset of M business components (B.sub.1, B.sub.2, . . . , B.sub.M) of a Component Based Model (CBM) of the M business components subject to M≥2 and N≤M. Determining the at least one relationship includes relating business components of the CBM with an Information Technology (IT) model of an IT system. The IT model includes abstract IT structures, virtual IT structures, real IT structures, or combinations thereof.

A virtual object system can orchestrate virtual objects defined as a collection of components and with inheritance in an object hierarchy. Virtual object components can include a container, data, a template, and a controller. A container can define the volume the virtual object is authorized to write into. A virtual object's data can specify features such as visual elements, parameters, links to external data, meta-data, etc. The template can define view states of the virtual object and contextual breakpoints for transitioning between them. Each view state can control when and how the virtual object presents data elements. The controller can define logic for the virtual object to respond to input, context, etc. The definition of each object can specify which other object in an object hierarchy that object extends, where extending an object includes inheriting that object's components, which can be modified or overwritten as part of the extension.