Amrut Software Pvt Ltd CASE-STUDY. Amrut Overview Expertise for over 9 years with Atlassian Range of experience in Customization, Development & Migration

Amrut Software Pvt Ltd

CASE-STUDY

Amrut Overview

Partners

Atlassian Implementations

Customization In Atlassian tools

Level 1

Customization In Atlassian tools

Level 2

Atlassian Training

Atlassian Implementations

Features Basic Enterprice Dedicated Plan

8*5 Web and tracker based support for issues and queries.

Customized Time Zones

Upgrades , Backup/ Restores, Plugins & Applications Suggestions

Module expert for each product:

Hours for Support & Services 500 1000 +Number Of Dedicated

Resources

Training for 2 days

Monitoring services (may require Additional tools)

Onsite within India (5 days per quarter- planned)

Performance Analytics Troubleshooting

Also Available On European Time Zone

Gartner Report

For more info visit:http://www.gartner.com/technology/reprints.do?id=1-1MN598P&ct=131105&st=sb

11

1. Intrinsically developed Issue tracker

2. Struggling with performance issues

3. Obsolete + different features and reports

4. Maintain 3 versions of the application on mission critical projects of Stock exchange software.

5. Different business processes on each instance with no clarity across

6. Had to comply with changing EU laws and security concerns

7. Diverting focus and investing efforts of the development team on Tracker

8. Rising cost of maintaining the system

9. NO Single sign on or LDAP/ AD connection, no password policy implementation.

10. Users had to sign in to different urls and login/ password

11. Eroding KB and resources with Old Tracker expertise.

Client SituationClient Situation

1. Merge all the 3 Instances into one JIRA

2. Create and use the same workflows across all projects

3. Integrate Knowledge management , Code and SSO

4. Integrate with AD.5. Map the users to uniform usernames.6. Single view for management on the

project progress7. Monitoring and alerts for tracking

system health8. DR server incremental sync

Proposed SolutionProposed Solution

1. Standardization and optimization of processes and flow across the org

2. Compliance with Standards

3. Significant decrease of overhead on maintenance and software upgrades

4. Single point Application for all users enhancing the user experience

5. Innovative ides with teams were now across organization.

6. Other operational processes included in JIRA

7. Usage of Agile for few teams

8. Support response and SLA’s better managed.

Client BenefitsClient Benefits

Enterprise issues-level JIRA deployment – 150K

Technology (with sizing details):

Business Process Covered:

1.14 workflows with up to 25 stepped processes for Software devlopemnt, Support and other operational Activities

2.Capturing Vital data mandatory based on conditions and flow

3.Fields hidden and visible based on Group of the user.

1. JIRA , 3rd party Plugins And Groovy / Jelly Scripts

2. 2k users with 150 K issues at starting point

3. 8 months implementation + 3 years ongoing support.

12

1. For one of the leading Engineering CAD product development company

2. Wanted to use JIRA to generate Purchase Requisition request to facilitate generation of Purchase Orders

3. Master and Transactional SAP data to be available in JIRA (through middle layer)

4. Transactional data need to be fetched at runtime to get the latest information

5. Multiple PR’s to be raised in single JIRA issue.

6. While displaying the drop down (which is either a Master or a Transaction SAP data), it should be displayed along with the codes(Codes + description)

7. There are few fields which are auto populate table data based on the information filled in the previous field.


1. Issue type & workflows are created in JIRA for Approval

Issue Types:

1. Material Purchase Requisition : This issue type will be used for creating Material Purchase Requisition

There will be three options to raise material PR:

• Cost Center PR• Project PR• Reimbursable PR

2. Service Purchase Requisition : This issue type will be used for creating Service Purchase Requisition

There will be three options to raise Service PR:

• Cost Center PR• Project PR• Reimbursable PR

3. Add multiple PR line items within the same form to be approved We have developed a new custom-field that can Add the values fetched from SAP Database into JIRA field.

4. Populate dropdown list based on selection from SAP Master Data

Proposed SolutionProposed Solution1. SAP Master & Runtime

transitional Data available in JIRA issues

2. Tracking and maintaining PR data in JIRA

3. Approvals for PR made easier

4. Save SAP license & Customization cost

5. Increase efficiency and save time

6. Better User experience and compliance


SAP to JIRA Data synchronization


1. Java : jdk1.72. Database : PostgreSql3. OS : Windows4. JIRA : JIRA 6.3.4


1. SAP

2. Connection between JIRA & SAP

Upgrade from WIKI to XHTML

1. Client has been using Confluence 3.1.2 for many years with 2k+ users and ~40 GB of data

2. The instance was highly customized with 5 major Home grown plugins which integrated with FTP Servers where the Tools RAW Data in TXT format was generated .

3. The Data in these files was used to publish Runtime Reports in Confluence pages.

4. With Confluence 4.x the mark up language has been changed to XHTML.

5. Challenges in the project was with respect to the interconnection of the plug-in and data in older format

6. No documentation of the 3rd party plugins.


1. Upgrade Confluence to 4.0 and later

to latest stable Version with:

2. Upgrade the stored data to XHTML

3. Upgrade the Connectors to FTP

4. Upgrade The plugins to be

compatible with new format.

5. Upgrade the All the Macros,

templates, Variables, PageSets

6. Change the storage location from

Database to File system

7. Upgrade the report & PDF exporter

plugin custom developed.


Benefits of the program:

1. The New process/ system can

currently handle the older as well

as new format

2. Minimum Alteration of current

formats

3. Macros to translate @ runtime to

Xhtml

4. Lighter database with attachments

on file system.

5. Faster response and performance

6. Better user experience



1.Java, Macros and

2.2k users with 40GB data

3.6 m deployment (18 man month

Project)


1. Project Documentation,

Artifacts and Reports

2. Templates for various type of

projects

3. Formatted Data

Xwiki to Confluence import

1. Check the feasibility for an

importer for migrating data

between Xwiki to Confluence

2. Analyse the data for usual syntax

and migration issues from below

check list

3. Identify clean or and mitigate the

syntax differences in the data

refer link for both Xwiki &

Confluence syntax.

4. Create a Scope of the project

with efforts & timelines


1. The Importer is designed to be

extensible, so that data can be

imported into Confluence from XWIKI

with minimal data loss or formatting

changes.

2. Most of the Importer can be divided

into 2 major

Components: Exporting and Converti

ng.

Modules for the Importer• Creating syntax converters• Macro's re-development • Creating Importer's Frameworks• Underlying Structural handling• Global Non-converter handling



1. Limitations of Xwiki are overcome

2. More Flexible than Xwiki

3. Better look and feel

4. Maximum attachments can be

uploaded and shared



1.Java, Macros and

15

Financial Product devolvement based company supporting multiple client installation across the globe.

Move to Product / Technology layer1. Features & bugs may arise in various projects,

related to a common Product & dependent on underlying Technology layer

2. The need to push this vertically down or push it to various instances (up)

3. Linking and auto updating the progress of the linked issues

4. Granting or restricting access to various user groups if the issue is tracked in core projects.

5. New features like ‘Move to Product / technology layer ’ of issues in different projects to be tracked at Implementation , product & technology layer

Release manger 1. Create and maintain a parent child relation

between releases, 2. Various internal and external releases to be

tracked separately3. Only children can appear in Fixed releases once

final release is decided or vice versa.4. No validation of business rules while creation

Custom reports1. 10 new Custom reports expected from the dats.

reports developed and exported to documents & reports.

Client SituationClient Situation1. Create a plugin for MTP feature in

JIRA

2. Identify implementation , Product , technology Projects

3. Define rules, Access and teams for each level

4. Clone , link, and auto update parent / destination issue based on triggers.

5. Create release manager Feature in JIRA

6. Understand and define the rules for these

7. Migrate and maintain relations of parent child into AO table (not JIRA DB)

8. Develop custom reports and formatting's for reports.



1. This helps the correct tracking by the correct team with out exposing the critical information about the issue

2. Bug fixes and new features developed in differ projects can be pushed to new client installations.

3. Avoid duplication of work/ Feature development fr each client installation

4. Maintaining Testing, Internal, and deliverable Releases separated but linked.


New Features to JIRA

1. JAVA , Groovy, AO tables,

2. 4k releases mapping

1. JAVA , Groovy, AO tables,

2. 4k releases mapping

Technology (with sizing details):Business Process Covered:

1. Version/ Release management

2. A Feature lacking in JIRA to be truly Enterprise project management system for product based companies

1. Data Migration of existing customer cases from other web portal in to Jira for reference

2. Based on company work timing, different type of SLA should be needed with facility to Start, stop, pause & reset i. Automation Escalation needed. ii. Reports Based on SLA remaining time

3. Provision to create Issue/Cases from website. i.e. from the non Jira users can create Jira issue by accessing website's particular page

4. Customized Incoming as well as Outgoing mail handler

5. SMS Alers on issue creation for Leads.

6. Knowledge Base Needed

Miscellaneous a.Permissions based on groups & userb. Issues can be assigned to group & group

member onlyc. Notificationsi. Jira usersii. Non Jira Usersd. Making fields mandatorye. Field dependency on other field. (Scripted

fields) f. various workflows for a single project

a.


1. For data migration JIRA provides a facility to Import data from outside with Importers plug-in

2. For SLA With desired facility "CRM for JIRA" plug-in is used

3. For Escalation Automation, "Automation" plug-in is used

4. To provide facility to create JIRA issues from Website, JIRA Issue Collector is used

5. Customized Incoming & Outgoing mail handler Plug-in

6. Inbuilt Notification and Permissions facility for JIRA Users

7. SMS plug-in is used8. The knowledge base will be captured in

Confluence, and integrated with JIRA9. Script runner Plug-in to accomplish various

apply scripts needed for • Permissions & Notifications• Field Configurations• Field dependencies(Scripted fields)


1. Problem of mail history maintenance is resolved

2. Tracking on Customer complaints/requests is easier

3. Everything is well structured & in well format

4. Different types of reports can be issued on the fly

5. SLA facility helps employee time management, Escalation

6. Non Jira users can also create/report Jira issues though custom mail handler

7. Customer gets current updates on the issues reported by them

8. Agents/Jira users (employees) can directly communicate with customer by writing mail from Jira itself

9. Agents able to add/ search key words or open from the Knowledge base

10. Also Agents can Select/copy the relevant block of text on the confluence page and add it as a comment to the Jira issue


Technology (with sizing details):Business Process Covered:CRM1. SLA management2. Email Integration3. Issus & CR Tracking

1. Java : jdk1.72. Database : MySQL 5.6.14 3. OS : Linux 64 bit machine4. JIRA : JIRA 6.3.45. Confluence : Confluence 5.5.6

JIRA CONFLUENCE CRM Project

• Feature requested by users in https://jira.atlassian.com/browse/CONF-2522 one of the oldest and most voted issue.

1. Created almost a decade ago (Jan 2005) with top 10 votes & watchers for the issue.

2. The feature request is to globally update word or sentences across the instance

3. Highlight and count items4. Ability to maintain audit 5. Roll back all or specific actions6. Wild card searches

• New features in progress

1. Regular expressions

2. User access to other groups ( currently only Confluence admin has the rights)

3. Release in Atlassian Marketplace


Developed a plug-in for the feature

1. The feature request is to globally update word or sentences across the instance with i) Replace one by one, ii)Replace all & iii)Roll Back

2. The plug-in maintains the history of the changes and can be rolled back individually

3. The plug-in excludes the space , macro and table names from such changes, as it may affect the functionality and linkage of these items

4. Search can be based on wild cards and special expressions

5. Search word can be replaced after replace action



1. This feature allows the users to find and replace one by one or globally replace words, phrases and url for changes in the confluence


Global-Find & Replace plugin

1. Revamping the core banking software along with development and testing vendor, needed a dependable and highly flexible issue tracking and project management tool

Client SituationClient Situation 1. We implemented features like auto assignment on custom select and setting up disaster recovery system, equest has helped the Bank set the system within a short turnaround time as the Development project had already commenced

2. As JIRA does not support Clustering or HA, We have setup back up and recovery for JIRA mechanism to support a incremental back up every 10 min in a geographically different location


1. Adapt to vendor development and another vendor’s testing team environment to maintain clear traceability and ownership between the bank and the vendors and managing the SLA’s for vendors activities

ChallengeChallenge

JIRA - ITIL deployment for India’s leading Bank

1. In case of production server goes down the DR server can be made up and running within with a minimal loss of time and data.


Author

1. We have extensively developed Multiple reports for our clients to generate runtime vital statistics to be pulled out within fraction of seconds.

2. We have also created new features to Hide reports from certain groups and roles, so as to provide another level of security to the data and reports.

3. One of the use case is to expose only required reports to the clients


Custom reports

Email-id Location Contact No

[email protected] Pune +91-9922139393

[email protected] Bangalore

+91-9448537401

[email protected] Mumbai +91 9867147661

[email protected] Chennai +91 9986129325

[email protected] NCR +91-8149988339

Documents

Amrut Software Pvt Ltd CASE-STUDY. Amrut Overview Expertise for over 9 years with Atlassian Range of experience in Customization, Development & Migration