As a certified Atlassian Silver Solution partner and authorized software reseller, OMNEEMO is uniquely positioned to help organizations adopt and leverage any or all parts of the Atlassian suite of products. Specifically OMNEEMO has on staff expertise in and can help with Jira Software, Jira Service Management (formerly Service Desk), Jira Core, Confluence, Trello, Bitbucket, Bamboo & Crowd.
OMNEEMO can help with strategy, development, integrations, migrations, upgrades, support, maintenance and of course with product selection and sale. From the leveraging of the Atlassian toolset, OMNEEMO can help advise and guide enterprise entities on ITSM, collaboration, project management, code management, customer service, service management, chat, file sharing, issue tracking and so much more.
Collaborate at high-velocity, respond to business changes and deliver great customer and employee service experiences fast.
Plan, track, and release world-class software with the #1 software development tool used by agile teams.
Spend less time hunting things down and more time getting things done. Organize your work, create documents, and discuss everything in one place.
Collaborate and get more done. Trello boards enable your team to organize projects in a fun, flexible, and visual way.
Collaborate on code with inline comments and pull requests. Manage and share your Git repositories to build and ship software, as a team.
Continuous integration, deployment, and release management.
The single sign-on and identity management tool that's easy to use, administer, and integrate.
Collaborate at high-velocity, respond to business changes and deliver great customer and employee service experiences fast.
Plan, track, and release world-class software with the #1 software development tool used by agile teams.
Spend less time hunting things down and more time getting things done. Organize your work, create documents, and discuss everything in one place.
Collaborate and get more done. Trello boards enable your team to organize projects in a fun, flexible, and visual way.
Collaborate on code with inline comments and pull requests. Manage and share your Git repositories to build and ship software, as a team.
Continuous integration, deployment, and release management.
Continuous integration, deployment, and release management.
Extend the basic functionality of Jira by creating a plugin with a new type of custom field.
Implement a project based on a new type of custom field.
Using the plugin, we have implemented our own three-level cascading field that synchronizes the list of current departments with the data on the customer's server.
Tested the functions of the plugin and checked the relevance of the list of departments provided by it.
Initiated a project with a business process that separates the collection of timesheet for streams and for teams, which made it possible to balance the load on the system.
Tested automatic timesheet collection and its impact on system load.
Checked the ease of use of the project for account managers.
Create a data source for a BI application based on data from Jira to download the history of field value changes.
Provide for the possibility of changing the type and content of the downloaded data.
Analyzed the customer's requirements and proposed several implementation options, also considering the features of the BI application.
Using the Jira API, we developed and implemented a data source in the form of a Rest endpoint.
Conducted comprehensive testing and refinement of the data source, receiving updated requirements for it.
Synchronize the customer's Jira with their partner company's internal system while maintaining the order of actions performed in Jira.
Added an intermediate stage in the transfer of information about changes in the form of a database that stores data (transactions) for each change.
Set up the transfer of information from the database in order of priority (first in - first out) within each issue in Jira.
Added a snippet in Jira issues to track the status of update submissions, last successful attempts, and possible errors.
Set up a customer notification system in case of errors in synchronization.
Support existing processes and develop new processes (Electronic bypass sheet, e-program "refer a friend").
Implement the integration of all processes with 1C and HR Link.
Integration of both new and existing business processes with 1C and HR Link was completed.
The necessary projects for the development of new business processes have been implemented, while the most complex mechanics have been applied (using the ScriptRunner plugin).
Appropriate documentation for new projects has been drawn up, a version control system has been applied.
Audit of the current technical support project.
Setting up synchronization with the contractor's system.
Collection of information on all current settings: task types, screens and fields, workflows, configured automations, plugins and their settings.
Data analysis.
Preparation of technical documentation for the project in two versions: one reflected the "as is" state, the second included all our recommendations based on best practices from Atlassian, the ITSM community and our experience.
Reducing customer costs by eliminating some process automations and reworking the rest using the Scriptrunner For Jira plugin.
Reworking SLA settings by generating concise JQL queries (there was a 10-fold reduction in levels compared to the original, from 80 levels for each counter to 8).
Development of a new status model, taking into account all stages of equipment delivery.
Setting up custom notifications for the passage of a certain percentage of SLA to various recipients using our own development - the plugin "Escalation Service".
(https://marketplace.atlassian.com/search?query=Escalation%20Service)
The possibility of independent support of the system without our participation.
Match of statuses and main attributes of objects in both systems.
Flexibility and ease of use.
Materials on setting up the project, and specifically Service Desk (SLA, Customer notifications, Request Types, Automation, etc.).
Full description of scripts and their purpose.
Instructions for all levels (for users and agents).
Manual with Atlassian best practices.
Recommendations for changes.
To match the statuses and attributes of objects, we cloned the structure of the MicroFocus system into the Jira system, including the data structure, the status change process, and the user interface.
Synchronization between systems is performed on the event of an object change in any of the systems, with guaranteed delivery, including a resending mechanism in case of failures and errors.
The class structure included a base synchronization class that stored all the synchronization settings required for configuration, classes for sending messages, and separate classes for listeners and post-functions that were installed in specific places in the business process and transferred to instances of the base classes required parameters.
Solving the issue of data exchange between systems in closed circuits without Internet access: we have developed an intermediate server "Bus", which is an interface for communication between two servers and preprocesses messages.
In close cooperation with our specialists from the MicroFocus department, REST communication points for data transfer we’ve developed. To synchronize data in Jira, standard REST requests were used.
Due to the architecture of the MicroFocus system (you cannot update task attribute values while it is in edit mode by some user), we have developed a guaranteed update delivery feature with resubmissions until the message is delivered. In case of prolonged unsuccessful attempts, notifications are sent to responsible people with detailed instructions to fix the problem.