STANDARD JIRA-CLIENT ESTNDAR - Indra · On one side, this allows Indra technicians to work...

Standard JIRA Client Use Guide

STANDARD JIRA-CLIENT ESTNDAR

Use Guide

Version 3.0

Madrid, December, 2017

Standard JIRA Client Use Guide

1 INTRODUCTION 3

2 JIRA CLIENT SOLUTIONS 4

3 INSTALLATION AND REQUIREMENTS 5

4 ACCESS 5

4.1 Request for registration of external users 6

5 JIRA CLIENT INTERFACE 8

5.1 Top navigation menu of JIRA CLIENT 9

5.1.1 Logos – Access to Clients 11

5.1.2 Dashboard 11

5.1.3 Projects 19

5.1.4 Tasks 21

5.1.5 Boards 24

5.1.6 User Guides 31

5.1.7 Create 32

5.1.8 Search 32

5.1.9 Help 32

5.1.10 Manage 34

5.1.11 User Profile 42

5.2 JIRA CLIENT Side Navigation Menu 44

5.2.1 Project and selection of Boards 45

5.2.2 Backlog 45

5.2.3 Active Sprints 46

5.2.4 Deliveries 46

5.2.5 Reports 46

5.2.6 Issues 47

5.2.7 Components 47

5.2.8 KPI Reports 47

5.2.9 Automatic closing of Issues 47

5.2.10 Disable Reject Issues 50

5.2.11 Dates management 52

5.2.12 Example of automatic calculation of dates 56

5.2.13 Add-ons 58

5.2.14 Shortcuts 58

6 JIRA CLIENT REPORTS 59

6.1 Average Age report 60

6.2 Created vs resolved issues graph 62

Standard JIRA Client Use Guide 2

6.3 Pie Chart 64

6.4 Recently created issues 65

6.5 Resolution time 68

6.6 Service-Level Agreement 70

6.7 Grouped by one level 74

6.8 Time Since Issues 75

6.9 Time tracking 78

6.10 User Workload 82

6.11 Version workload 83


1 Introduction

This user manual aims to give an overview of the functionality and operations of Jira, and to make known the basic

standard solution. This solution consists in a standard parameterization, accessible for any operation which

requests it in the platform Standard JIRA-Client (hereafter, JIRA Client). It is linked to the Internal JIRA of the

MInd Suite (hereafter, JIRA-MInd). On one side, this allows Indra technicians to work homogeneously and in a

standard way by using the development technical cycle of MInd. Furthermore, the clients benefit from the possibility

to monitor the progress of their requests in the JIRA-Client environment. Both systems are integrated in real time

through web services. (Image Nr. 1 – Integration between Standard JIRA Client – JIRA MInd).

The JIRA-Client offers the users appointed by the client the possibility to create issues for representing a work

request to be achieved within a service. The types of requests are associated to four types of products: Functional

Support, Corrective, Feature Request and Big Feature Request.

When client users create a request in JIRA-Client, it will automatically create an associated request in JIRA-MInd

(of the equivalent type: Functional Support, Corrective, Feature Request or Big Feature Request).

Image nº1 –Integration between Standard JIRA Client – JIRA MInd


2 JIRA CLIENT solutions

JIRA has different parametrizable solutions, accessible for any operation that requests it:

Standard JIRA Client: This solution allows Indra technicians to work homogeneously and in a standard

way by using the development technical cycle of MInd. Furthermore, the clients benefit from the possibility

to monitor the progress of their requests in the JIRA-Client environment. In JIRA-Client, the users

appointed by the client benefit from the possibility to create issues for representing a work request to be

achieved within a service. The types of requests are associated to four types of products: Functional

Support, Corrective, Feature Request and Big Feature Request.

Standard JIRA Client with Approvals: This version is based on the previous solution, although it has

differences in workflows and properties that allow the client to perform additional approvals of the different

phases of the requests when required. Thus, two new types of issues are added to the previous ones. This

allows the client to approve the issue planning: Planned Functional Support and Planned Corrective.

JIRA Client Guarantee: This solution is indicated for the clients to use it during the guarantee period. The

JIRA-Guarantee offers the client the possibility to create Issues and later, thanks to the integration with the

corporate JIRA of Indra, to monitor the progress of the resolution of these issues.

JIRA Client for TM/UM Services: This solution is indicated for TM (Technology Management) Service

operations, UM (User Management) Service and issues of Technical Support: Request and Issue. JIRA-

TM/UM offers the client the possibility to register jobs of technology management, users and technical

support and later, thanks to the integration with the corporate JIRA of Indra, to monitor the progress of the

resolution of these issues, requests or service management tasks.

In case the standard solution is not suitable for a particular operation, a customized configuration of JIRA

Client can be requested.

In the following documents:

Practical cases of Standard JIRA Client.

Practical cases of Standard JIRA Client with Approvals.

The types of issues covered by these solutions will be explained in depth, as well as the creation and monitoring by

the client based on several examples that will help to understand the functionality of the fields that make up the

issues.


3 Installation and requirements

It is installed centrally on the server and it does not need to be installed on the client side.

Web Browsers: if the JavaScript execution has been disabled in the browser, or if you are using a script-blocking

tool, it must be reactivated to run the JavaScript code. The table Nr. 1 shows the compatibility with the most commonly used browsers.

Supported browsers (tested by Atlassian for JIRA Core 7.1)

Web Browsers

Chrome Latest supported version Minimum screen resolution 1024x768 (when the browser is maximized).

Mozilla Firefox Latest supported version Minimum screen resolution 1024x768 (when the browser is maximized).

Safari Latest stable version compatible with Mac OS X

Minimum screen resolution 1024x768 (when the browser is maximized).

Microsoft Internet Explorer

Versions:10.0 y 11.0 Support for edges added from JIRA 7.1.4

Minimum screen resolution 1024x768 (when the browser is maximized). Compatibility view: not compatible.

Table Nr.1

4 Access The access to JIRA-CLIENT takes place through the URL:

https://jira4client.indra.es

A log in with credentials (user name and password) will be required to the user.

Image Nr. 2 - JIRA-CLIENT System Dashboard

https://jira4client.indra.es/


4.1 Request for registration of external users

The request for registration of external users is performed through the project:

JIRA "MIND Support" (SDH)

A “Technical Support” request and as Component/s “MIND external users” should be created, in which the

following information should be included in the description:

We request the registration of an external user with the following data:

Name

Surname

E-mail: [email protected]

Image Nr. 3 – Creation of a request for external user.

Once the username and password has been assigned, it can be changed in the following URL:

https://jira4client.indra.es/secure/PasswordChangeAction!default.jspa

Image Nr. 4 –Window to change Password MInd.

https://jira.indra.es/browse/SDH

mailto:[email protected]



4.2 Password Reset

To reset the password, access https://jira4client.indra.es/secure/PasswordResetAction!default.jspa and fill in the data of our user and captcha.

Once this is finished, the user will receive an email with a link that will allow him/her to change the password. This link will only be valid for the user and for a certain period of time:

4.3 Password Policy

The password can be changed at any time using the following link: https://jira4client.indra.es/secure/PasswordChangeAction!default.jspa

".cli" users will also have access to the link next to their user profile:

The new passwords will have to meet a number of mandatory security requirements:

It must contain at least eight characters (preferably 10).

It must contain characters from the following groups:

Upercase letters (A, B, C, D...)

Lowercase letters (a, b, c, d...)

Digits (0, 1, 2, 3...)

Recommended special characters (! @ # $ % & * + = [ ] . )

The system remembers the last four passwords used

In accordance with the defined security regulations, the passwords are valid for 90 days and must therefore be modified periodically. In case of reaching the last 10 days of validity of the password without having changed it, the user will receive a daily email advising him/her to renew it and the instructions to do so. If this is not the case, the user will be disabled

https://jira4client.indra.es/secure/PasswordResetAction!default.jspa



5 JIRA CLIENT Interface

The JIRA-CLIENT interface (Image Nr. 5) provides an overview of the Project through the combination of the upper

menu (nº 1 of image Nr. 5) and the left-hand side menu (nº 2 of image Nr. 5), allowing a total accessibility for an

entire project management.

Image Nr. 5 – Interface JIRA Client.

The JIRA-CLIENT interface includes the following main areas:

1. Top Navigation Menu: Allows access to general items of the JIRA tool.

2. Side Navigation Menu: Allows the interaction with items related to the Project.

3. Central Information Area: Shows information about the selected contents and allows the interaction with that

information.

Some navigation items in the top menu will be able to load other side menus and support submenus that will be

necessary to operate on that selection. (Image Nr. 6).


Image Nr. 6 – Example. Selection of the Agile option from the JIRA Client menu.

5.1 Top navigation menu of JIRA CLIENT

This section offers detailed information and the actions that can be performed with each option making up the Top

Navigation Menu of JIRA-CLIENT. (Image Nr. 7).

Press on any link included in the following image to enlarge the information.

User Guides

Image Nr. 7 – View of the Navigation Menu section of JIRA Client.

Upload home page

See and manage dashboards

Project Browser

Search of issues and

administration of filters

Project Management with JIRA Agile

Create issues

Search

Help

Manage Projects

User Profile

Note: The JIRA Client navigation menu will be totally displayed, i. e., with all the options visible in the browser (as shown in

the previous image nr. 5) on screens with a resolution of 1024x768 pixels or more.

If the resolution is lower, or the browser window is minimized, the options: Projects, Issues and Agile will be placed

creating a submenu within a new option called: More (Image nr. 8).

Image nr. 8 – Pop-up menu More.


5.1.1 Logos – Access to Clients

Once the tool has been accessed by clicking on the Indra - Mind - Access Clients logo, the Dashboard or the last

one selected will be loaded by default in the central part of the interface, which can be matched to a dashboard

customized by the client. See the following section: 5.1.2 Dashboard.

5.1.2 Dashboard

When the tool is accessed for the first time, the dashboard drop-down menu will show by default the System

Dashboard and the access to Manage Dashboards. (Image Nr. 9). As the user adds new dashboards, these will

appear in the Dashboard menu.

Image Nr. 9 – Dashboard.


5.1.2.1 System Dashboard

The default dashboard of the system has several information items. A welcome introduction and three gadgets

that provide relevant information.

Introduction: It welcomes and includes several accesses to documentation related to Standard JIRA

Client and Guarantee solutions.

Image Nr. 10– Introduction.

Assigned to me: It provides an overview of the Issues the user has assigned.

Image Nr. 11 – Assigned to me Gadget.

Activity Flow: As its name suggests, it shows the recent activity of the users of the application. For

example, when a new request is created.


Image Nr. 12 – Activity Flow Gadget.

Filters saved: This gadget contains filters added as favourite by the user, or customised in such a way that

it shows relevant information. Both links are located at the bottom of the gadget: ‘Create filters’ and

‘Manage filters’ give access to the creation of new filters and their administration.

Image Nr. 13 – Filters saved.

The gadgets, either the system own gadgets or those customized by the user, add a small menu with two options

located to the right of the top bar of the gadget. (Image Nr. 14).

Image Nr. 14 - Gadget upper bar.

These options allow the following actions:

Maximize: It increases the gadget to the Dashboard total space. It can be retrieved pressing the button

Restore.

Minimize - Update: It minimizes or expands the gadget information and refresh the information.

5.1.2.2 Manage dashboards.

This option will open the window with the same name: Manage Dashboard. (Image Nr. 15).


Image Nr. 15 – Manage Dashboard.

From the menu located in the upper right margin of this section, new dashboards can be created, option: Create a

new dashboard, and Restore values by default. (Image Nr. 16).

Image Nr. 16 – Manage Dashboard Menu.

5.1.2.3 Create a new dashboard

This option will open a window with the same name to set a new dashboard. (Image Nr. 17).

A Dashboard consists of Gadgets. Small applications that provide different services and information to the user.

These gadgets are perfectly configurable by the user.

Image Nr. 17 - Create a new dashboard.

The following fields must be completed to set a new dashboard:

Name: Name assigned to the dashboard.

Description: Short description about which function will provide the dashboard.

From: It allows selecting whether the dashboard is to be created as a copy of an existing custom

dashboard, as a copy of the System Dashboard, or it will be created blank, from scratch.


Favourite: It allows marking the dashboard as favourite. (Favourite) (Not favourite)

Sharing: It shows information about the Add sharing field, indicating with whom the dashboard is shared.

Add sharing: Drop-down menu that allows selecting with whom a dashboard is to be shared: with All

(public), with a Specific group or with a Project.

Add: After completing the fields, press this button to create the new Dashboard.


The table below shows and describe some of these gadgets.

Name Description

Requests assigned to the user List of the issues whose Assignee is the user that is currently logged in in JIRA.

Unresolved requests List of the requests, which are not yet finished (Issues not yet delivered).

Delivered requests pending of close.

List of all the Issues already delivered by the Indra supporting team but which are still pending to be accepted by the client (Close the request).

Evolution of the number of Issues created vs resolved

Graphical display of the evolution during the last 60 days of the newly created requests vs the amount of Issues that have already been solved.

Request distribution by product It presents a pie chart with the amount of requests of each type of product.

Request distribution by status It shows a pie chart with the distribution of requests by their current status.

Issue calendar It shows a calendar where the Issues distributed are shown depending on the selected field (for example, Due Date).

Table Nr. 2

5.1.2.4 Restore values by default

By pressing this option, the Dashboards bookmarked in Favorites will be reset. It deletes the Dashboards

customized by the user in Mine. Therefore, this option must be taken into account before pressing it.

5.1.2.5 Left-hand side menu to manage dashboards

The left-hand side menu is located to the left of the Manage Dashboards window that allows navigating through

the options listed below (Image Nr. 18).

Image Nr. 18- Left-hand side menu of the Manage Dashboards panel.

Please, note that if you share a dashboard with (the group) All, it will be a public document that

can be viewed by users who have not logged in to Jira client.


Favourite: It allows displaying dashboards added by the user as favourites. These boards can be

positioned using the arrows on the right margin: From left to right: it places the dashboard in

the first position, it moves it one position up, one position down, and it places the dashboard in the last

position. The option located below, allows Copying other dashboards (e.g. those that have been

shared with All) and Editing or Deleting the dashboards created by the user.

Mine: It allows displaying the dashboards created by the user.

Popular: It allows displaying the dashboards created by other users, and adding them as favourites.

Search: It allows searching a Dashboard using the filters: Name or Description of the Dashboard, Name of

the Dashboard’s Owner, and Shared with all, a group or a Project.

Thus, when the user adds public dashboards set by other users, these will appear in a list in the Dashboards main

menu. (Image Nr. 19).

Image Nr. 19 - Dashboard.

Tools menu

Within the System Dashboard, the Tools utility (upper right margin) facilitates the Copy, Search and Creation of

the dashboards and the possibility to visualize the Dashboard as a Wallboard. This consists of a dynamic

presentation of the data displayed on the dashboard. It is recommended, for example, for projections in operating

rooms. To deactivate a Wallboard, press the escape key (Esc).

Image Nr. 20 – Tools utility.

The Configure Wallboard presentation option allows you to Select panels (different Dashboards, and also the

system and custom dashboards), to select a Random order of exposure, a Transition effect between the

Dashboards, and the Cycle period that determines the duration between transitions. (Image Nr. 21 - Wallboard

configuration).


Image Nr. 21 – Wallboard Configuration


5.1.3 Projects

The projects option allows you to select the CURRENT PROJECT (Image Nr. 22) in which you are working, the last

RECENT PROJECTS with which you have been operating, and the options: View all projects or Project

Browser.

Image Nr. 22 - Projects

The View All Projects option will list all the projects that can be filtered by: All Project Types or All Categories

from the shortcuts that appear in the left side menu.

Selecting a project from any of the above options will open the Project Browser.

5.1.3.1 Project Browser

Image Nr. 23 – Project Browser.

It allows navigating through Projects, and selecting two exchangeable search ways (Nr. 2 in image 23 - Project

Browser).

The Basic search mode allows you to filter the search of a Project by selecting fields (Nr. 1 - Image Nr. 23 - Project

Browser), while the Advanced search allows the use of JQL (Jira Query Language) query procedures that enable

to refine the search, getting more accurate results.


Any search made can be saved by pressing the Save as option (Nr. 3 - Image Nr. 23 - Project Browser). All

previously saved searches can be viewed later from the left-hand side menu: Project Browser Filters (Nr. 4 of

Image Nr. 23 - Project Browser) where they will be added.

The results of the query are displayed in the central part (Nr. 6 - Image Nr. 23 - Project Browser) in a table whose

columns can be customized by using the dropdown menu: Columns located in the right margin of the table.

After the query, the results can be Exported to Excel format (Nr. 5 - Image Nr. 23 - Project Browser) allowing to

work with offline data or their subsequent consultation.

The selection of a project displays the Project Fields and Change History screen with the data set by the tool

administrators, which are not modifiable. These fields correspond to the Add-ons section of the popup left-hand

side menu in the Interface besides the Metadata. (Image Nr. 24).

Image Nr. 24 - General Information & Administration.


5.1.4 Tasks

It allows the search and visualization of issues similarly to the Project Browser, since the interface is practically the

same with slight variations that are explained below. (Image Nr. 25).

Image Nr. 25 - Tasks.

When clicking on any of the first two options (previous image): Current Search and Issue Search, they will open

the Search window (Image Nr. 26).

Image Nr. 26 – Issue Search Panel.

The Search window is divided into three sections:

1. An upper section (Nr. 1 - image Nr. 26 - Issue Search Panel), where you can parameterize the searches of

issues, and save them pressing the ‘Save as’ button. This search can be Basic or Advanced (option on

the right, in the same section Nr. 1 - image Nr. 26 - Issue Search Panel).


In the same way as in the Project Browser, the Advanced search will allow performing JQL (Jira Query

Language) queries inserted in the text field on the left.

To the right of the Search option, the icon: allows selecting Detail View or List View. The basic

difference between both is that the Detail View (Nr. 3 - image Nr. 26 - Issue Search Panel) shows the issue

data in detail allowing interaction with it.

Above the view mode, there are three options, as shown in image Nr. 27.

Image Nr. 27 –Search window options.

They allow the following options:

Share: It shares a search with all users.

Export: Exporting the search result to formats: XML, Excel, Word, graphs of issues solved or

pending in the last 30 days, printing or adding an RSS link among others.

Tools: Through this option, the project managers can Change issues in Block (up to a maximum

of 1000 issues) by means of a four-step wizard that will allow changing: the value of the issue

fields, moving issues, observing issues (to receive notifications) or stop observing them.

2. Section: Filters (Nr. 2 – image Nr. 26 – Issue Search Panel). The search can be reset by pressing the

button: New filter.

The user can select any filters by default:

My open issues.

Reported by me.

Recently viewed.

All the issues.

Apart from selecting the Favourite Filters added by the user.

The option Search filters located under the New Filter button (Nr. 2 – image Nr. 26 – Issue Search Panel)

will open the Manage Filters window (Image Nr. 28) that allows you to Search a filter by name, Owner or

Shared with All or with those groups the user belongs to. Therefore, you can access them and add them

as favourites to the list: Favourite.


Image Nr. 28 – Manage filters.

Apart from the Search option, the Manage Filters window can list filters based on the selected category from

the left-hand side menu, for example:

Favourite: It shows all the filters added by the user as favourites, clicking on the icon: located on

the left of the filter. After clicking on the icon, it will change its colour: This will mean that it is a

favourite filter.

Mine: It shows all the filters owned by the user.

Popular: It consists of filters created by other users, which have been shared with the rest.

Search: When there is a large number of filters, the Search of filters will help to locate them.

The icon: located on the right of each filter, allows accessing the filter edit or delete options. (Image Nr.

29).

Image Nr. 29 – Edit and Delete Issues

3. Depending on the type of view selected (List or Detail), the central section (Nr. 3 - image Nr. 26 - Issue

Search Panel) will show the list of Issues resulting from the search.


5.1.5 Boards

JIRA-CLIENT contemplates the project management with Agile methodology.

From the Boards menu you can access the management, administration and creation of Agile Boards. (Image Nr.

30).

Image Nr. 30 – Agile.

The first section of the menu: Recent Boards (upper image) saves a list of the last boards queried by the user. If

no board has been created or queried, this section will not show any board. It will be possible to click: View all the

boards (Image Nr. 31) to see the existing ones and to select some related to the project in the client.

Image Nr. 31 – All the boards.


Once we start to operate with Agile methodology, the Boards that have been queried will appear, and the more...

option will be added. When pressing it, the Boards window will open (Image Nr. 32) giving the option to view

between:

Boards recently viewed

And All Boards.

Image Nr. 32 – Boards.

When selecting a board, it will be displayed. (Image Nr. 33).

Image Nr. 33 – Example of selected Scrum dashboard.

The option: View all boards will allow expanding the information by opening all the boards. This option, like

Manage Boards, will open the All Boards window (Image Nr. 31 - All Boards).

The Visibility or access to a (Kanban or Scrum) board may be restricted. This restriction can be configured when

creating or editing it later from the option *** that allows the options: Configure and Copy, in addition to the option

Delete for dashboards created by the user. (Image Nr. 34).

Image Nr. 34 - Example of options. Board created by the user.


5.1.5.1 Create an Agile board

To create a new Board, start by clicking on the main button at the top right hand side: Create Board (Image Nr. 32

- Boards) that will activate the wizard to select the type of Agile Board most appropriate to the project being

managed.

Image Nr. 35 – Creation of Agile Board

It will be possible to select (Image Nr. 35) an Agile board of methodology:

Scrum. It is a method recommended for development teams, as it is more prescriptive than Kanban,

where time is organized into short iterations and the job into small and specific deliverables.

Kanban. This method is more adaptable and oriented to change or maintenance jobs that do not need

iterations of Scrum type. It allows displaying the workflow, limits the number of items in each status and

optimizes the time of each item.

The Configuration options accessible via the configuration option: located on the right-hand side of the Board

(Image Nr. 32 - Boards) are detailed below. (Image Nr. 36).

Image Nr. 36 – Board configuration window

Note that in each configuration option a legend is added to guide the user on what can be done in

each of them.


General: It allows editing fields on the Board such as: the Board Name, the board Administrators, the

type of Filter Saved. Shared resources, an editable field that allows assigning filter sharing permissions

with All users (public), with a Group or a specific Project. See the following image. (Image Nr. 37).

Image Nr. 37 - Sharing.

Columns: It allows adding, removing, resorting and renaming columns from the Column Administration.

Columns are based on Global Statuses that can be moved between these columns. The maximum and

minimum restrictions can be defined for each column. (Image Nr. 38).

Image Nr. 38 - Columns.

Lanes: A lane is a row on the board that can be used to group issues. (Image Nr. 39).

The type of lane can be modified by selecting from the following options:

Queries: It groups issues by custom queries.

Histories: It groups subtasks under the parent issue.

Assigned users: It groups issues by assigned user.


Epics: It groups issues under the corresponding epic.

Swimlanes: No swimlane will be displayed.

Image Nr. 39 – Base lanes.

Quick Filters: their use is recommended to further filter the issues on the board, based on the additional

JQL query. (Image Nr. 40).

Image Nr. 40 – Quick filters.


Card colours: It allows assigning a colour based on the types of issue, Priorities, Assigned Users,

Queries, None. (Image Nr. 41).

Image Nr. 41 – Card colours

Card design: The cards can be configured so that they show up to three additional fields. (Image Nr. 42).

Image Nr. 42 – Card design


Estimation: It is possible to estimate the issues when they are in the backlog, in order to have an idea of

how much work is being committed in a sprint. (Image Nr. 43).

Image Nr. 43 - Estimation

Working days: It allows highlighting or excluding non-working days from reports and gadgets. (Image Nr.

44).

Image Nr. 44 – Working days


Issue data view: It allows adding, deleting or resorting fields on the issue data view. (Image Nr. 45).

Image Nr. 45 – Issue data view

5.1.6 User Guides

It allows access to all the available Guides about Jira Client solutions.

Image Nr. 45 – User guides


5.1.7 Create

Pressing the Create ( ) button, the Create Issue will open to set the task.

The new issue creation options are explained in the following documents: Practical case of Standard JIRA Client

and Practical case of Standard JIRA Client with Approvals by the client.

5.1.8 Search

The following text box Search (next illustration) will allow finding Issues using the key or, for example, inserting a

text included in the issue. It is appropriate for quick searches.

Image Nr. 46 – Search window.

Otherwise, it is recommended to use Issue search from the issues menu.

5.1.9 Help

This option provides online help links for Jira and Jira Agile to the Atlassian documentation page, and it also

displays the revision and credits of the tool. See next image.

Image Nr. 47 – Help Menu.


An interesting option in the help menu is the Keyboard shortcuts page. (Image 48).

Image Nr. 48 – Keyboard shortcuts.


5.1.10 Manage

The icon allows access from the Projects option to the Manage section of the selected project. (Image Nr. 49).

Image 49 – Access to Projects

From the Administration window, you can select which project you want to manage from among all the available

ones and for which the user must have assigned editing permissions. (Image Nr. 50)

Image Nr. 50 - List of projects


By accessing one way or another, the Administration window will allow setting up the project, managing

permissions or issues, or assigning specific calendars to issues, among others. (Image Nr. 51).

Image Nr. 52 - Administration

Some of them are:

Components.

Users and Roles.

SLA KPI Management.

Notifications.

Calendar configuration.

Calendar administration.

Given the complexity of some of the most frequent Jira-Client administration issues

discussed below, it is recommended to manage them through a request to MInd Support.


5.1.10.1 Components

A JIRA-CLIENT project can be segmented into as many components as applications or modules integrating the

operation in the client. In this way, the classification of the issues will be performed against the components that

make up the operation. (Image Nr. 53).

Image Nr. 53 - Components

The following fields should be completed to add a new component:

Name: Name of the component.

Description: Short description of the component.

Component leader: Person responsible for the component.

Assigned by default: Assigning the assignee by default. It can be: configured by default (in the Project

fields), the component coordinator, the project coordinator or leave it unassigned.

The Add button on the right will add the new component to the list of components.


5.1.10.2 Users and Roles

The Users and Roles section will allow the project administrators to assign users to specific roles in the project. The

roles created will allow defining other adjustments as permissions or notifications (Image Nr. 54).

Image Nr. 54 – Users and Roles


Using both links placed at the top right corner, it will be possible:

To add users to a role: pressing the link, a user/s or group can be selected and then, a role where it will

be added.

Image Nr. 55 – Add Users to Roles.

Edit the default values: Editing the default values will allow modifying the data of the Leader and the

Responsible by default for the assignment of the project issues.

Image Nr. 56 – Define leader and person responsible by default in the project.

The Permission administration is only accessible by the platform administrator.


5.1.10.3 SLA KPI Management

The Key Performance Indicators are metrics that help us to measure and quantify the Service performance

defined in the SLA Model agreed with the Client.

In order to have a notion about the SLA KPI Management, the following is a summarized explanation of which

sections will be included by the administration of the SLA KPIs. (Image Nr. 57).

Image Nr. 57 - SLA KPI Management Options

KPI Administration: From this section, a new customized KPI can be defined or created from an existing one.

KPI Selection: From this section, it will be possible to select standard indicators and to enable or disable an

indicator, either standard or customized.

KPI Execution: From this section, it will be possible to specify for each KPI displayed the way it will be

executed. There are three execution ways:

ONLINE Executed at a periodic interval of 1 minute to 24 hours.

BATCH Executed at a periodic interval from 1 day to 12 months.

TRIGGERED Executed in a modification of an issue or when it changes status.

KPI Planning: It should be requested to MInd Support.



5.1.10.4 Notifications

When it is necessary to send a notification, once certain conditions have been met in an issue, it can be configured

manually from this section by using Templates.

Image Nr. 58 - Notifications

5.1.10.5 Templates

E-mail notifications use templates to define the structure and contents of the e-mails. (Image Nr. 59).

Image Nr. 59- Templates

Given the complexity of their configuration, it is recommended to create a request to MInd Support to

manage the creation of Notifications from there.



The templates can be set from this window to be used when one or several notifications are sent.

5.1.10.6 Calendar configuration

When an issue is created, a service calendar can be assigned based on its properties. This relationship between

the issue and the service calendar cannot be changed once it has been created.

The assigned service calendar will be used in several time calculations (Indicators and some reports).

5.1.10.7 Calendar administration

For the roles of managers and project managers, they can access from here to the administration of those

calendars configured for the managed project/s.

Given the complexity of their configuration, it is recommended to create a request to MInd Support to manage the

Calendar Configuration from there.

Given the complexity of their configuration, it is recommended to create a request to MInd Support to manage the

Calendar Configuration from there.




5.1.11 User Profile

The User Profile option consists of the Profile of the logged user where the details and modifiable preferences are

collected. (Image Nr. 60).

It also includes the section My Home Page that contains shortcuts to utilities (already commented in previous

sections), such as:

Dashboard: It opens the last dashboard seen by the user.

Agile: It opens the last Agile board opened by the user, either Scrum or Kamban.

Issue Browser: it opens the Issue Browser.

Image Nr. 60 – User Profile

5.1.11.1 User Profile

In summary, the user's profile shows the Details or data of the user, the Preferences and the user's Activity Flow.

It also allows making comments directly in any of them or to be added as a watcher. To change the Avatar simply

by clicking on the icon a new Avatar can be selected or a file can be uploaded from the local computer.

Image Nr. 61 - User Profile


To edit the Preferences section, click on the icon: (Image Nr. 62).

Image Nr. 62 – User Preferences

Some of the preferences that may be of interest are: changing the language using the Language field or activating

the Keyboard shortcuts.

Any changes made in the preferences section will not be completed without pressing the Update button:


5.2 JIRA CLIENT Side Navigation Menu

The Side Navigation Menu (Image Nr. 63) offers the user full integration with the configuration and data of the

project, as well as the daily management of issues.

The side menu is configurable so it can be adapted depending on the project. Likewise, the order of the links that

compose it can present another layout.

The following are some of the standard links that make up the side menu of JIRA-CLIENT

Image Nr. 63 – Jira Client Side Navigation Menu.

Project and selection of Boards

Active sprints

Versions

See reports

Component management

Query SLA indicators

Backlog

Create shortcuts

Issues

Automatic closing of issues

Disable Reject Issues

Date Management

Add-ons


5.2.1 Project and selection of Boards

Clicking on this first link allows reloading the project data and selecting a board that is assigned to the project by

means of the drop-down menu located under the project name.

The following configured quick filters can be selected: Only My Issues and Recently updated.

Image Nr. 64 – Example of a project Board.

Through the Board drop-down menu it will be possible to Configure an existing board, Copy an existing board,

Create a new board, Hide a detailed view, Increase all lanes, Collapse all lanes, Hide Epic tags, Print cards.

5.2.2 Backlog

It shows the sprints that have been created in the project, the issues assigned to these sprints and the total of tasks

collected in the Backlog. It allows quick filters such as: Recently updated or Only my issues.

Image Nr. 65 – Backlog.


5.2.3 Active Sprints

It shows the sprints that are currently active. From the Board menu it allows the configuration and creation of new

boards. See 5.1.5 Boards.

Image Nr. 66 – Active sprints.

5.2.4 Deliveries

It shows the versions set in the project. With the necessary permissions, it allows to create new versions.

Image Nr. 67 – Delivery View.

5.2.5 Reports

See section: 8 JIRA CLIENT Reports


5.2.6 Issues

It shows all the issues open in the project.

The Change filter dropdown menu allows selecting one of the filters set in the Search window.

From the link See all issues and filters it is possible to access the Search window that contains the filters

included by default, those set by the manager, and others added to the Favorites section. See 5.1.4 Tasks.

Image Nr. 68 – Open Issues.

5.2.7 Components

See section: 5.1.10.1 Components.

5.2.8 KPI Reports

See section: 8.6 Service-Level Agreement

5.2.9 Automatic closing of Issues

In a Standard JIRA Client Project it is possible to automate the transition of issues from a Delivered or Approved

status (by the client, once the job has been delivered), to the Closed status. In a Standard JIRA Client Project with

Approvals, apart from the previous status, the Production Start-up status must be added to some Types of issues,

in such a way that when the issue has spent a certain number of days in one of the mentioned status previous to

Closed, it will be closed automatically, and no manual intervention will be necessary.

This automation is set on the tab Automatic Closing of Issues of the project area. From there, it will be possible

to establish independently the closing time for each type of issue.


5.2.9.1 Configuration

First, it must be taken into account that it is necessary to have permissions of JIRA Project Administrator Role to

perform this configuration.

With the necessary permissions, the tab Automatic Closing of Issues (Image Nr. 69) of the project area will be

accessed. From there, the closing time for each type of issue will be established depending on its status.

Image Nr. 69 – Automatic closing of Issues

Pressing the option: Add configuration, the window with the fields to complete will open.

Image Nr. 70 – Add configuration

The Add configuration window shows three fields with the type of issue, its status and the condition of the number

of days the issue will remain before the programmed closing.

Image Nr. 71 – Configuration fields


In the example displayed in the image Nr. 71, a configuration has been made, so that the issues of Feature type,

which have been in Delivered status for 30 days or more, can be changed automatically to the Closed status.

Depending on the JIRA solution in question, the type of issues and the status to set will vary slightly:

For a Standard JIRA Client project, a configuration can be performed concerning:

Types of issues such as: Corrective, Functional Support, Feature or Big Feature Request.

Status: Delivered and Approved for all the types of issues, except for the type: Corrective, that will be only configurable from the Delivered status (see table below).

Number of days after which the issue will be closed.

For a Standard JIRA Client project with Approvals a configuration can be performed concerning:

Types of issues such as: Corrective, Functional Support, Feature, Big Feature Request, Planned Corrective or Planned Functional Support.

Status: Delivered, Approved and Production Start-up. The last one, for each type of issue, except for: Functional support and Planned Functional Support (see table below)

Number of days after which the issue will be closed.

The table below shows the types of issues and the possible status in which the automatic closing can be set for a

Standard JIRA Client project and Standard JIRA Client project with Approvals.

JIRA type of client Type of issue Status

Standard Corrective Delivered

Functional support Delivered, Approved

Feature Delivered, Approved

Big Feature Request Delivered, Approved

Approval Corrective Delivered, Approved, Production Start-up

Functional support Delivered, Approved

Feature

Delivered, Approved, Production Start-up

Big Feature Request


Planned Corrective


Planned Functional Support

Delivered, Approved

Table Nr. 3


5.2.10 Disable Reject Issues

JIRA – Client offers the option to set up the rejection of an issue once it is closed in a Project Jira. That is to say,

when an issue has already been closed and a predetermined period of time has elapsed, the issue cannot be

opened by the Client (rejection).

The Disable Reject action of the Issues takes effect when completing that action. That is to say, when clicking on

the Reject option in the issue, even though the Reject popup window allows selecting the Reject Reason and

adding a Reject Comment, when the action is validated pressing the Reject lower button, a system message will

warn that it is not possible to open the issue.

Image Nr. 72 – Pressing Reject a message informs that it is not possible to reject it.

5.2.10.1 Configuration

To access the option it is necessary to have permissions of project Administrators.

The option is available in the General Information tab, option Disable Reject Issues.



Then, press the button:

Image Nr. 74 – Add issue.

And select the issue type (Image Nr. 75) that the configuration will apply:


This can be:

ALL ISSUE TYPES: (option by default) it will apply to all the project issues that haven’t their own option set up.

Issue Type: selection of a specific issue in the list. It will be the first to determine the number of days in the issue.

In the Days field, we will insert the calendar days from which it is not possible to transition with Reject any longer

from the client.

Press Save to save the changes.

We can add as many issues as we need to set up in the project.

The days set up shall be considered to have been exceeded taking into account the hours. For example, if one day is set up for issues of Corrective type, it means that after 24 hours from the closing time of the issues, they can already be reopened.

A Project JIRA not set up at this level will always allow the reopening.


5.2.11 Dates management

MInd includes in JIRA some utilities for establishing the automatic date calculation of the issues of each JIRA Project. In that automatic calculation of dates, four factors are involved:

Date of origin for the calculations: date from which the other date is computed.

Calculation deadlines: period of time from the date of origin for obtaining the date to be calculated. These limits are given for each issue type, priority, component and value of the Project Parameter 4.

Service calendar: set of days and timetable in which the service is operational and within deadlines are computed. The Indra supporting team sets the service calendar.

Status of the issue in which can be considered stopped: the time that the issue remains in those statuses will not be taken into account in the deadline calculations.

Following chapters will focus on configuration and usage of Dates Management.


5.2.11.1 Setting dependencies between dates

The specific configuration of calculating dates is performed in the Dates Management area of the JIRA Project.

This area has three sections:

Date Setter

Product Priority Hours

Stop Status Issue

Which are accessed via tabs located at the top side.

Image Nr. 76 – Dates Management

In the Date Setter section, the dependence between the origin and target dates is configured.

Later, in the Product Priority Hours section, deadlines to use on the dependences can be specified in the Date

Setter section.

In the section Stop Status Issue are registered the status that should consider the issue as stopped. Therefore,

the time that the issue remains in that status should not be taken into account within the established deadlines.

The dependence between two dates is specified in the Date Setter section using the steps listed below.

1.- In the Add/Update Dates Configuration form, the type of issue (Issue Type field) on which is going to be

established the dependence between dates must be selected. In addition, two dates must be selected: the date

field (Origin field) from which the calculations are going to be made, and the date field (Target field) which is

automatically calculated from the previous one. In addition, in the Action field, must be specified whether the target

date will take the same value as the origin date (Copy to option) or the period specified in the Priority Product

Hours section must be added to it (Calculated option). In addition, it can be established whether the target field

can be edited by the user (Editable option). In order to confirm the established dependences in the form, the Save

button must be pressed.


Image Nr. 77 – Update Dates configuration

2.- After the previous step, the system shows a message informing that the configuration has been saved

successfully.

Image Nr. 78 – Confirmation message of configuration updated

3.- After closing the previous message, in the Current Configuration list, can be seen how the dependence has

been recorded. If necessary, any previously established dependence can be removed by clicking on its Delete

button.

Image Nr. 79 – The last update is placed on the first line

In cases where the dependence is set to Copy to type, no additional configuration is required. However, if the

dependence is of Calculated type, the deadlines to apply must be assigned. This additional configuration is

detailed in the following section.


5.2.11.2 Setting deadlines in the calculation of dates

As explained in the previous section, when dependencies between two dates of Calculated type have been

declared, the periods to be used for the calculation of the target date must be specified. The system allows

providing different terms depending on the priority given to the issue, the component which the issue belongs to

and the value of the Project Parameter 4 field. To set these deadlines, the Product Priority Hours section should

be accessed and there must be selected in the top drop down the type of issue (Issue Type field) on which is to be

performed the automatic date calculation, the date field automatically calculated (Target field), the priority (Priority

field), the component (Component field), the value of the Project Parameter 4 (if exists any available value for

that JIRA Project) and in the Hours and Minutes fields must be set the period in hours and minutes. Thus, the

target date is calculated by adding to the original date and the deadline set by considering only the working hours

that have been specified in the service calendar. To accept the entered deadlines values the Save Configuration

button must be clicked.

Image Nr. 80 – Current configuration added from Product Priority Hours

After a message that informs that the configuration has been saved successfully, the new row of the saved configuration can be seen in the Current Configuration section.

The process can be repeated in order to insert all the deadlines for all the priorities.

5.2.11.3 Status in which the issue is stopped

The Stop Status Issue tab allows establishing for each type of issue the status in which the issue must be

considered as stopped. The time that the issue remains in those statuses will not be taken into account in the

deadline calculations.

To record the stop status, select the type of issue (Type of issue field), the status (Status field), and press the

Save configuration button.


Image Nr. 81 – Current configuration added from Stop Status Configuration by Issue

In the Current Configuration section can be viewed the status that have been configured as stopped for each type

of issue.

5.2.12 Example of automatic calculation of dates

Once the JIRA Project has been set up as mentioned in the previous paragraphs, the following example will show

how when creating an issue some dates are automatically calculated.

Note about the operation or preference between automatic calculation and manual input of a date in the

workflow

Whenever the date that causes the change is changed, the target date is calculated.

In the case of changing both dates at the same time, the origin date of the change and the target date of the

change, the change of the origin date prevails, and therefore the target date is calculated.

If the target date is changed manually without changing the origin date, the change is made.


The steps for the verification will be the following:

1. Create an issue of Big Feature Request type with a Minor priority and assign to the Request Creation Date

field a value (for example last Monday at 9:01 am).

Image Nr. 82 – Create verification issue

2. Once the issue is created, if the Edit option of the issue window menu is accessed, in the Dates tab can be

seen that starting from the Request Creation Date (Monday 9:01) the Commitment Response Date field has


been automatically calculated (Friday at 9:01). The difference between both dates are four full calendar days of

the service, because for the Minor priority had been established a term of 32 hours and the service schedule

has 8 working hours a day.

Image Nr. 83 – Update in Dates tab

5.2.13 Add-ons

It contains the Project and Changes History fields and Metadata. These data are set up by the tool administrators

and they cannot be changed.

5.2.14 Shortcuts

Jira Client allows adding as many shortcuts (URL) as necessary. For example, links to issues, internal

documentation or external links. These links can be shared with all the support team members in the client.

Image Nr. 84 – Update


6 JIRA CLIENT Reports

To access the reports of a JIRA Client project, we shall select the Projects menu of section: General Information

and option: Reports. (Image Nr. 85)

Image Nr. 85 - General Information Window. Reports.

Below we describe each report.


6.1 Average Age report

The Average Age report shows a bar graph with the evolution, over a period of time, of the average number of

days that the unresolved issues of a JIRA Project or a stored filter have got.

The following fields are requested in the form prior to the report:

Project or filter saved: it establishes from which JIRA Project or filter are obtained the Issues involved in

the report. By default, it will be the JIRA Project from which we have accessed.

Period: time division (per hours, daily, weekly, monthly, etc.) used to measure the graph.

Days previously: number of days of the period of time to be displayed on the graph. This period ends

always in the current day. (Image Nr. 86).

Image Nr. 86 - Average age report filter.

By clicking the Next button a report with two parts is generated, a first graphical part with the evolution of the average time of the Issues, and a second part with the list of the values obtained for each measurement interval. In addition, for each interval, the list shows the number of unresolved Issues and the total sum of the days that these Issues have been open. (Image Nr. 86).


Image Nr. 86 - Average age report view.


6.2 Created vs resolved issues graph

The Created vs Resolved Issues report shows graphically the evolution of the number of issues created and

resolved in a period of time.

The following fields are requested in the form prior to the report (Image Nr. 87):

Project or filter saved: it establishes from which JIRA Project or filter are obtained the Issues involved in the

report. By default, it will be the JIRA Project from which we have accessed.


Days previously: number of days of the period of time to be displayed on the graph. This period ends always

in the current day.

Cumulative Totals: it indicates whether the graph data show the total number of open and closed Issues

accumulated from the beginning of the graph period (option Yes) or whether the data only show the open and

closed Issues in the sample interval (option No).

Show Versions: it allows establishing whether vertical lines representing the delivery date of each version will

be seen in the graph. We can select between not displaying the versions (option No), showing only first level

versions (option Only main versions) or all the versions of the JIRA Project (All the versions).

Image Nr. 87 - Created vs. resolved Filter.

By clicking the Next button a report with two parts is generated, a first graphical part with the evolution of the

Issues created (red line) and Issues resolved (green line) and a second part with the list of the values used for each

measurement interval.


Image Nr. 88 - Created vs. Resolved views.

The areas between the two lines can be represented in red or green, the areas in red indicate that in that period

more Issues have been created than those that have been resolved, while the green areas show the periods in

which more Issues have been resolved than those that have been created.

If the graph shows that the red line grows indefinitely faster than the green one, it will

mean that the team does not have sufficient resolution capacity to follow the rhythm of

the client's requests.


6.3 Pie Chart

The Pie Chart report shows in a pie chart, grouped by a field specified in the previous form, the distribution of the Issues of a JIRA Project or of those returned by a stored filter. This form (Image No. 89) only requests the following two fields:

Project or filter saved: it establishes from which JIRA Project or filter are obtained the Issues involved in the report. By default, it will be the JIRA Project from which we have accessed.

Statistics Type: field of the Issues that will be used to group them in the chart.

Image Nr. 89 - Pie Chart filter.

By clicking the Next button a report with two parts is generated, a first graphical part with the distribution in circular

sectors of the number of Issues according to the values of the selected field, and a second part with the list of

values taken by the field and the number of Issues taking that value. This list also shows the percentage of Issues

taken by each value (Image Nr. 90).


Image Nr. 90 - Pie chart view.

6.4 Recently created issues

It is a bar graph that shows the number of Issues created and resolved per day (or per hour, week, month, etc.)

from a given date to the current time.


Project or filter saved: it establishes from which JIRA Project or filter are obtained the Issues involved in

the report. By default, it will be the JIRA Project from which we have accessed.


Days previously: number of days of the period of time to be displayed on the graph. This period ends

always in the current day.


Image Nr. 91 - Recently created filter.

By clicking the Next button, a report with two parts is generated. A first graphical part that shows two bars for each

measurement interval. The red bar indicates the number of Issues created in that interval, and the green bar the

number of resolved Issues, and a second part that shows the list of the values of created and resolved Issues in

each measurement interval. (Image Nr. 92).


Image Nr. 92 - Recently created view.


6.5 Resolution time

This report shows in a bar chart the evolution of the average time used to resolve the issues.


Project or filter saved: it establishes from which JIRA Project or filter are obtained the Issues involved in the report. By default, it will be the JIRA Project from which we have accessed.


Days previously: number of days of the period of time to be displayed on the graph. This period ends always in the current day.

Image Nr. 93 – Filter of resolution time report.

By clicking the Next button a report with two parts is generated, a first graphical part with the evolution of the

average time used in the resolution of Issues and a second part with the list of the values used for each

measurement interval. (Image Nr. 94).


Image Nr. 94 - Resolution time report view.


6.6 Service-Level Agreement

Note

The SLA establish in Services (AM - Application Management) the maximum resolution and permanence times in

certain status for each type of product (Corrective, Feature Request, Big Feature Request and Functional Support)

and for each level of Priority. The resolution times are not calculated as a natural time but as time within the

calendar and the service schedule agreed with the client. (Example: If a client makes a request at 19:55 hours and

the service schedule ends at 20:00 hours, if the request is resolved the next day at 08:10 hours and the service

schedule starts at 8:00 am, then the time for resolution of the request is only 15 minutes instead of 12 hours and 15

minutes, which would be the natural time elapsed).

The Service-Level Agreement report shows the service calendar time that each request has remained in different

workflow status.

The search data are requested in the report input form. Through the fields Start Date and End Date it is possible to

indicate the time frame to filter the Issues to be displayed in the report. The Issues displayed will be those that are

total or partially “alive” (in a status different from Closed or Deleted) within that frame.

To refine the Issues search data, the form (Image Nr. 95 - SLA Report form) contains the Status fields. This allows

displaying the Issues that, within the selected frame, were in the indicated status, and Status transitioned that

allows defining which Issues have made the transition to the indicated status within the specified time frame,

discriminating those Issues that could make the transition outside that time frame. If any of these dates are not

indicated, they will take the current day. In addition, we can select the priority (Priority), the type of request

(Request Type) and the component (Component).

Image Nr. 95 - SLA Report Form.


Note

In the previous paragraph, the statement "the form contains the Status transitioned to Closed that allows defining

which Issues have made the transition to the indicated status, within the specified time frame” refers to all the

Issues that have made the transition to the indicated status within the defined frame (delimited by Start Date and

End Date).

In the Image Nr. 96 the life lines of several Issues are represented. From all of them, the only ones that would be

within the search criteria would be 3 and 4.

Image Nr. 96- Status transitioned to Closed

By clicking the Next button, the following report is displayed (Image Nr. 97).

Image Nr. 97 - Report


A summary of the search criteria used to obtain the report is displayed on the top right corner. (Image 98).

Image Nr. 98 – Report Parameters

The table Nr. 4 shows the Issues that meet the specified criteria. The columns displayed are:

Column Description

Project Key of the JIRA Project to which the request belongs.

Request Request key.

Summary Request name.

Component Component the request refers to.

Status Current status of the request.

Current Status Date Date of the current status of the request.

Planned Start Date Planned Start Date.

Real Start Date Real Start Date.

Planned End Date Planned resolution date.

Real End Date Real resolution date.

Reporter User who created the request.

Request Type Request type.

Priority Request priority.

Assignee User currently assigned to the request

Due Delivery Date Resolution deadline

Estimation Approval Estimation approval date

Planning Approval Planning approval date

Attended Date on which the request was attended

Sold Units Sold units

Time in 'New' Time in seconds of the Service Calendar in which the request has remained within each indicated status.

Time in 'Previous Study'

Time in 'Assessment'

Time in 'Pending Approval'

Time in 'Approved


Estimate'

Time in 'Approved'

Time in 'Deployment'

Time in 'Estimated'

Time in 'Estimation Rejected'

Time in 'Planning'

Time in 'Pending Plan Approval'

Time in 'Estimated/Planned'

Time in 'Estimation Planning Approved'

Time in 'Approved Plan'

Time in 'Plan Rejected'

Time in 'Design Development'

Time in 'Design Pending Approval'

Time in 'Working on it'

Time in 'Delivered'

Time in 'Approved'

Time in 'Deployment'

Time in 'Reopened'

Time in 'Stop'

Table 4 – SLA report columns.

If the result takes up more than 100 Issues, which is the maximum that a page can display, the browser (image Nr.

99) of pages located at the bottom of the page can be used.

Image Nr. 99 – Pagination of issues views.

The order of the Issues in the list can be established according to a certain field. To do this, the header of the

column associated with the field for which you want to set the order will be used. (Image Nr. 100)


Image Nr. 100 – Field arrangement.

The report data can be exported to Excel. In this way, it will be possible to process the times obtained for each

request (for example, to calculate the applicable penalties for delays). To obtain the report in Excel format, press

the Export to Excel button located in the lower left corner of the report screen.

6.7 Grouped by one level

It allows displaying a list of Issues obtained after applying a filter. They are displayed grouped by a field that can be selected by the user.

In the form prior to the report (Image Nr. 101), the Filter to be applied for obtaining the Issues of the report is requested. In the Static type field, select the field where you want to see the issues grouped.

Image Nr. 101 - Filter of report grouped by level.

The generated report shows the Issues in several blocks. Each block has in the header the value of the grouping

field that is common to all Issues in the block, and to the right of that header it graphically shows with a bar the

proportion of Issues resolved (in green) vs. those unresolved (in red). (Image Nr. 102).


Image Nr. 102 - - View of report grouped by level.

6.8 Time Since Issues

The Time Since Issues report shows in a bar chart the evolution of the number of Issues of a JIRA Project or filter stored with a specific established date field (for example, Created, Updated, Due, Resolved, or a personalized field).

The following fields are requested in the form prior to the report:

Project or Filter Saved: it establishes from which JIRA Project or filter are obtained the Issues involved in the report. By default, it will be the JIRA Project from which we have accessed.

Date Field: it specifies the date field from which we want to record in each measurement period how many Issues have established a value for this field.


Days Previously: number of days of the period of time to be displayed on the graph. This period ends always in the current day.

Cumulative Totals: indicates whether the graph data show the total number of Issues (option Yes) or only the Issues affected in the sample interval (option No).

The following gadgets can be added to the dashboards to show information similar to

that displayed in the Single Level Group By report.

FilterResults Gadget.

Statistics Gadget Request.

Two-Dimensional FilterStatistics Gadget.


Image Nr. 103 - Filter of report grouped by level

By clicking the Next button, a report with two parts is generated. A first graphical part that shows one bar for each

measurement interval that represents the number of Issues to which a value has been established for the selected

field, and a second part that shows the list of the number of Issues to which a value has been established in the

selected field in each measurement interval.


Image Nr. 104 - Time Since issues report.


6.9 Time tracking

This report shows the time tracking information (estimation, performed, estimated time remaining, progress, etc.) of the Issues of a JIRA Project version. It also shows the progress of the version, based on what was performed in its Issues and the estimates of additional time needed to complete the work.


Corrective version: it allows selecting from which JIRA Project version you want to obtain the report.

Classification: it allows establishing the order to present the issues. The available options are: Less complete issues go before: it shows first the Issues with the field Estimated Time Remaining in

a higher position. More complete issues go before: it shows first the Issues with the field Estimated Time Remaining in

a lower position.

Issues: it allows indicating which Issues of the version will be included in the report. The possible options are: All: it includes all the Issues assigned to this version. Issues to be completed only: it excludes Issues that are completed (Estimated Time Remaining =0)

or unestimated (Original Estimate=0). Note: the status of the Issues is not taken into account to show them or not.

Inclusion of subtasks: it allows selecting which subtasks of the version Issues will be included in the report. The available options are:

It only includes subtasks with the selected version: it only includes subtasks belonging to the selected version.

It also includes subtasks without an established version: it includes the version subtasks and those that do not have a version assigned to them.

Including all the subtasks: it includes all the subtasks regardless of the version they belong to.

Image Nr. 105 - Filter of time tracking report.

By clicking the Next button a report with two parts is generated, a first graphical part with overall information of the

version, and a second part with the detail table of the selected Issues and subtasks. (Image Nr. 106).

Subtasks that belong to the selected version, even if their request does not

belong to that version, are always included in the report


Image Nr. 106 - View of time tracking report.

Two progress bars are displayed at the top of the overall information section. They represent the overall time

tracking of the version. The meaning of these bars is as follows:

The first bar (image 107) graphically shows in green the number of working hours recorded in the Issues

and subtasks of the version, and in orange the estimated remaining hours (Remaining). The value shown

in Progress is the ratio between the hours recorded and the sum of the recorded and the remaining hours.

Image Nr. 107 - Progress Bar.

The second bar shows in blue and with the same scale as the previous bar the number of hours initially

estimated in the Issues of the version (Sum of the Original Estimate of the Issues). The value displayed in

Accuracy indicates the percentage of deviation between the initial estimate (in blue) and the current

estimate (green + orange).


When comparing the length of the blue bar with the sum of the green and orange bars, three cases may occur:

1. The version jobs progress as planned (image nr. 103) in the original estimate. The blue bar (next image)

has the same length as the sum of green and orange (Accuracy=0).

Image Nr. 108 - Progress Bar.

2. The version jobs are delayed (image 109) compared to the initial estimate, i. e. more time will be needed to

complete them. The sum of the green bar plus the orange bar (next image) is longer than the blue bar.

Therefore, behind the blue bar a grey bar appears that represents the additional estimated time that will be

necessary to complete the version jobs. In other words, the grey bar represents the delay of the jobs

(Accuracy<0).

Image Nr. 109 - Progress Bar

3. The version jobs are ahead of schedule (image 110) compared to the initial estimate, i. e. less time will be

needed to complete them. The blue bar (next image) is longer than the sum of the green one plus the

orange one. Therefore, the grey bar that appears behind the orange bar represents the amount of time

overestimated in the version as a whole (Accuracy>0).

Image Nr. 110 - Progress bar

The following information appears in the detail table of the Issues and Subtasks:

Original Estimate: initial time estimate needed to complete the request jobs.

Estimated Time Remaining: current estimate of the remaining time needed to complete the request.

Time Spent: amount of time spent on the request. It is the sum of all the job records performed on the request.

Accuracy: accuracy of the initial estimate compared to the current estimate of the request. It is calculated as

the percentage difference between the sum of the fields Time Spent and Estimated Time Remaining and the

field Original Estimate.

If subtasks are displayed in the report, some columns with the summation symbol (∑) are also displayed. There will

be one of these columns to the right of each field (Original Estimate, Estimated Time Remaining, Time Spent and

Accuracy). These columns only have values in the rows of the Issues. The values displayed are the aggregation of

the field to the right of the request, plus the values of that field in its subtasks. That is, these columns show the

totals of each request.


The version totals are displayed in the last row of table Nr. 5.

The information obtained can be exported in Excel format by clicking on the Excel View button located in the upper

right corner of the report screen.

Requ

est

Type

K

e

y

St

at

us

Prio

rity

Sum

mary

Original

Time

Estimated

(min)

Σ Estimated

Time

Remaining

(min)

Σ Total

Time

Spent

(min)

Σ Accuracy Σ Accuracy

(%)

Σ

Table Nr. 5


6.10 User Workload

The User Workload report shows the workload assigned to a user at the current time. For each of the JIRA Project

in which the user is involved, it will show the number of unresolved Issues assigned to it and the Backlog

(remaining) of those Issues. This report does not include the option to export to Excel.


User: it allows selecting or typing the user’s name for which the workload report is to be generated.

Inclusion of subtasks: it allows selecting which subtasks should be taken into account in the report

calculation from the Issues assigned to the user. If we select Only subtasks of the selected user are

included, only the subtasks assigned to the user will be taken into account, while if we select Only

unassigned subtasks are included, then the subtasks assigned to the user and those that are not assigned

to any user will be taken into account.

Image Nr. 111 - Workload report view

By clicking the Next button, the report is generated with a table with the number of unresolved Issues assigned to

the specified user and the Backlog, grouped by JIRA Project. The last line in the table shows the total number of

Issues and the total remaining workload of the user.


6.11 Version workload

This report shows the Backlog data by user and request type for a selected JIRA Project version from which it is

accessed.

It also shows, for the selected version, the list of unresolved Issues assigned to each user, the workload of each

user, as well as a summary of the total remaining workload for the version. This report does not include the option

to export to Excel.


Version (mandatory): it allows selecting the version from which we want to obtain the report. The report will include all Issues included in this version through the Fix Version field.

Show Issues without estimate: it allows indicating if we want to include the Issues not estimated in the report. The possible values are: Yes: it includes all the Issues, regardless of the value of their fields Estimated, Time Remaining or

Original Estimate. No: it excludes the Issues that do not have established their section: Time Tracking (Ex. it has not

specified Original Estimate).

Inclusion of subtasks: it allows selecting which subtasks of the version Issues will be also included in the

report. The available options are: It only includes subtasks with the selected version: it only includes subtasks belonging to the same

version as the parent request. It also includes subtasks without an established version: it includes subtasks belonging to the same

version as the parent request, and those that do not have any version. Including all the subtasks: it includes all the subtasks of the parent Issues (those with the same version,

those belonging to another version, and those that do not have any version).

Image Nr. 112 - Version workload filter.

Subtasks that belong to the selected version, but whose parent request do not

belong to that version, are always included in the report.


By clicking the Next button, a report is generated that includes two sections: Summary and Individual Estimates:

Summary: it summarizes the backlog (remaining) of each user broken down by the types of request included in the version.

Individual Estimates: it shows for each user a table with the list of Issues in the version assigned to them and for each of these Issues it shows the backlog (remaining). These individual lists of Issues are sorted by request type. At the end, another table is shown with all the unassigned Issues of the version (if any). (Image 113).

Image Nr. 113 - Version workload view.

STANDARD JIRA-CLIENT ESTNDAR - Indra · On one side, this allows Indra technicians to work...

Documents

Transcript of STANDARD JIRA-CLIENT ESTNDAR - Indra · On one side, this allows Indra technicians to work...