Category Archives: JIRA

Will your Agile Transformation be an Epic Failure?

AgilePicture-2

Image credit: Miranda Kumar (at age 8)

For the last 20 years I have been in the business of helping companies get better at developing software products. I started my career believing that the highly structured processes like CMM Level 5 will magically take care of the software projects woes. After two disappointing years, I moved on to Rational Unified Process (aka RUP). After another 6-7 years of disappointments with RUP the natural progression in my thinking and (coincidently) software development process evolution took me down to the path to Agile. My success with Agile processes has made me a believer in the process.

Unfortunately, many of the teams that start their journey towards the Agile land don’t ever reach there. Across the board I have found some common traits in the teams that failed with their Agile transformation effort. In this article I have shared all of them. Feel free to add more from your experience in the comments below.
Continue reading

Posted in Agile, AGILE Tools, JIRA, JIRA on Demand. Tagged with , , , , .

Programmatically Create Select Type Custom Field In Jira

In order to create a custom field type, you should be aware of basic plugin development.

Please follow the following steps to create an advanced custom field type in Jira.

    1. Create a basic Jira plugin skeleton. For creating Jira Plugin please refer to the given linkhttps://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project/create-a-helloworld-plugin-projectAfter creating a Basic plugin skeleton modify your atlassian-plugin.xml and add the following code in your atlassian-plugin.xml.
    2. After creating a Basic plugin skeleton modify your atlassian-plugin.xml and add the following code in your atlassian-plugin.xml. <customfield-type key=”Jira-Cf-Type-field” name=”Jira-Select CFType” class=”com.atlassian.jira.plugin.customfield.JiraCustomFieldType”><description>Create Your Own Advance Custom Field Type</description>                             <resource type=”velocity” name=”view” location=”templates/plugins/fields/view/view-basictext.vm”/><resource type=”velocity” name=”edit” location=”templates/edit- jiraselectcftype.vm”/><resource type=”velocity” name=”xml” location=”templates/plugins/fields/xml/xml-basictext.vm”/>

      </customfield-type>

                                          

      com.atlassian.jira.plugin.customfield.JiraCustomFieldType – class which extends an available CustomField Class to provide an entry point for the custom field.
      Continue reading

Posted in Agile, AGILE Tools, J2EE, JAVA, Java Script, JIRA, JIRA on Demand. Tagged with , , , .

OAUTH 2.0 AUTHENTICATION FOR THIRD PARTY APPLICATIONS

Most of the APIs now-a-days incorporate oauth 2.0 authentication. It is not as complicated as it may seem at times, provided the right links and documentation are found. Microsoft APIs are extremely helpful and useful, but to access them from a third party application is when its needed, for the entire process of registration and access token retrieval, to be followed; to comply with the oauth authentication in place.

For office365 (2016) APIs the links that would help access these APIs would be of the format https://outlook.office.com/api/{version}/me/

me – represents the logged in user
{version} – v2.0 or v1.0
/… – events (for outlook calendar API)

The first step, as hundreds of websites mentions, is to register the application. To be a little more comprehensive on this point, I would like to mention that it is not required to deploy any kind of code or application into the registration portal.

https://apps.dev.microsoft.com is free if you have access to a Microsoft office account.

The registration process is a way of letting Microsoft know that a particular app is going to access its APIs. It is a good practice to name the app appropriately as it will appear on the screen when the application, that is being developed, navigates to the login page.

mirketa_oAuthAppRegistration

Application id is the client id which is needed to be provided in the headers when requests are made for authorisation code and access token.
Continue reading

Posted in Agile, AGILE Tools, J2EE, JAVA, Java Script, JIRA, UI, WEB SERVICES. Tagged with , , , , .

Introduction to Version Control System

A version control system, to a great extent, is based around the concept of tracking changes that happen within a collection of directories or files.

A version control system (VCS) allows you to track the history of a collection of files. It supports creating different versions of this collection where each version captures a snapshot of the files at a certain point in time and the VCS allows you to switch between these versions as well. These versions are stored in a specific place, typically called a repository.

The process of creating different versions (snapshots) in the repository is depicted in the following infographic. Please note that this picture fits primarily to Git. Other version control systems like Concurrent Versions System (CVS) don’t create snapshots of the files but store file deltas.

mirketa-git-VCS

  Continue reading

Posted in Agile, AGILE Tools, Apache Ant, J2EE, JAVA, Java Script, JIRA, JIRA on Demand, MirketaInc. Tagged with , , , , , , .

How to programmatically move attachments from one JIRA issue to another JIRA issue?

The following piece of code when executed, helps us move attachments between two issues of same project or different projects in Jira.

Here I have two issues, one of them will be the source issue, where user adds an attachment and another issue will be the target issue, where the user want to move the attachment to.

This functionality is working fine in JIRA in its UI, however, I have tried to accomplish the same functionality through Java code. The following code executes the task of moving an attachment between the issues of both same or different projects.
  Continue reading

Posted in J2EE, JAVA, JIRA, JIRA on Demand. Tagged with , , , , .

JIRA GADGET

How to design your first Jira gadget?

Jira provide the ability to display information about project/issues/data on a dashboard, through the use of   ‘gadgets’. Gadgets are a big leap in JIRA’s reporting features.

In this document here I shall give instructions on how to write your first Jira gadget.

Before we start designing the gadget, we should know the key component of Jira gadgets :-

  • GADGET.XML is the most important part of a Jira gadget. It holds the specification of the gadget, and includes the following:- Continue reading
Posted in JIRA, JIRA on Demand, XML. Tagged with , , , .

INTRODUCTION TO NODE JS

Mirketa_Node

INTRODUCTION TO NODE.JS

What is Node?

This blog will introduce you to NODE. I will take you through Node and its environment setup for developing your first application. Node is an open-source, cross-platform runtime environment for executing the JavaScript code. For Node you must be acquainted with JavaScript, HTML and CSS and also have some familiarity with web applications and the MVC concept. Its built on the Google V8 JavaScript engine and V8 compiles JavaScript code to native machine code.

Continue reading

Posted in CSS, HTML/CSS, Java Script, JIRA, JIRA on Demand, Node.JS. Tagged with , , .

Introduction to Atlassian Connect

Mirketa_Introduction_to_Attlasian connect

What is Atlassian Connect Framework?

Atlassian Connect framework is used to develop add-ons for Atlassian applications like Jira and Confluence.

Atlassian Connect add-ons are web applications. They operate remotely over HTTP and can be written in any programming language.
Continue reading

Posted in Agile, CSS, HTML/CSS, J2EE, JAVA, JIRA, JIRA on Demand, Mirketa Atlassian Connect, Mirketa Atlassian Framework, MirketaInc, UI, UX. Tagged with , , .