Why Jira?

Change is always difficult at the beginning. Time permits us to better accept changes. Migrating to JIRA is our first chance to be opened to the world of agility.

Shorter release cycle. Simplication on ticketing tools. Reknown and standards of the market. Standardisation of major platforms like Core CRM and iCARe. Continuous integration tools among developers. Structured way of doing tests. Better visibility of tests performed and the results.

This move is one step ahead for transformation. To better prepare us to take new challenges!

YES WE CAN! (smile)

Table of contents

1.Lost in JIRA as I used to work thay way...tell me more!

Used to be in PMO......Going to be in Jira
RequirementsStory (issue type)
DefectsBug (issue type)
Test scriptsTest (issue type)
SFDC processEpic (issue type). Remember to assign issue to an Epic!
ReleaseFix version (field). In order to assign issue to a release, first needs to create a release record by Change Manager
Urgent change - quick and small hot fixes that are pushed to production quicklyCreate as either Story or Bug. Each move-to-production has to be a release. Urgent change is tied to a minor release
  
  
  

 

A Backlog is a list of issues in the pipeline, waiting to be qualified and assigned to a sprint.

A Sprint can be planned ahead and issues can be assigned to planned sprints.

At any time, you cannot have 2 sprints running at the same time.

You need to complete a sprint before to start another one.

  

 An active sprint is the current running sprint.

 

 

A Test is an issue type. When you create a Test, it has other properties of a Test Case.

It lists down the Test Step, Test Data required to execute that Test Step, Expected result of the Test Step.

You can only include an attachment to a step should it require graphical verification.

 

 

Test cycle contains a list of all the Test issues that need to be executed.

Test cycle can be easily created and then clone, for example, the same test cycle cloned for Devpro and UAT.

For a given Test cycle, we have a good visibility of all tests executed and it's percentage of passes/fails.

 

 

 

 

 

 

 


2.0 Workflow

2.1 Requirements/Story workflow

 

2.2 Defects/Bug workflow


2.3 Detailed activites in the issue lifecycle

3.0 Step-by-step guidelines