Child pages
  • Administrator's Guide
Skip to end of metadata
Go to start of metadata

1. Configuration

1.1. General

This section allows you to configure the plugin for all your projects.

1.1.1. JIRA Agile Integration

This option is enabled by default for the Jira Agile (known as GreenHopper) integration. If this option is enabled, the plugin will be Jira Agile aware if a project is Jira Agile enabled.

Precisely, the plugin will take "start date", "end time" and "release date" into consideration of planning. And the version parent/child relationship of GreenHopper will be used to display in tree of the SpreadSheet and containment.

1.1.2. User configuration

This option provides the possibility to enable or disable the gantt-charts for all users or for some users. By default, all users are enabled. This option is convenience choice but it is not best one from point of view of performance. If there is a huge users in your Jira server, it'd better to minimize this list. 

To set up the specific users, click on check box "Apply to these users" first and then add the desired users by clicking on the button "Add', This button opens the JIRA user selector in a dialog:

You can select one or more users in once. 

It is possible to disable the selected users by clicking the button "Remove". The modified list is kept in the page until you click the button "Update", which validates your modifications. Therefore, after the modifications, don't forget click the button "Update" to save the all changes. 

When an option "Apply to these users" is enabled, another option "Only Assignable Users" gets activated.By default, the option "Only Assignable Users" is checked. When this option is checked, only the selected users in the "Userconfiguration" can be used as the assignable users in gantt-chart. When this option is unchecked, the assignable users of JIRA configuration in project will be used as assignable users in gantt-chart.

1.1.3. Project configuration

This option provides the possibility to enable or disable the gantt-charts for all projects or for some specific projects.  
By default, all projects are enabled. This option is convenience choice but it is not best one for performance for the gantt-charts of Project Portfolio. If there is a huge projects in your JIRA server, it'd better to minimize the list. 

To set up the specific projects, click on check box "Apply to these Projects" first and then move the desired users from "Disable Projects" to "Enable Projects" by double click or select some users and then click on the button ">>". In the same way, you can disable some users by moving from "Enable Projects" to "Disable Projects".After the modifications, don't forget click the button "Update" to save the all changes. 

1.1.4. Date Format

This option allows to set up a date format for everyone. 

By default, the value is "Automatic". With this value, the date format will depend on the language selected by each user. A specific value will force the data format for all users. 

Each link of Jira consists of two references: forward and backward. The option "Use Direct Link" indicates to use which reference to handle the the parent/child relationship. When it is enabled, the forward reference will be used. Otherwise, it is the backward reference.

1.1.5.1. Start time and End time

By default, JGCP can provide the project planning with standard fields to find start and end date of issues.

But it is possible that users want other plugin to access the start and end time scheduled or reuse the fields defined by other plugins in custom fields. These settings are useful to add a physical storage over the Jira standard fields.

Since our plugin provides the capability to schedule at the granularity of hour and minute, only the fields of type "Date Time Picker" can be used for the start and end time. All others fields are filtered out including the fields of type "Date Picker", which can store the date time in day same as field "Due Date".

The detail algorithm to resolve the start and end time are explained on the page Jira Issues.

The Child-Issue link is used to define the containment relationship between issues. By default, Jira supports it. But there are two limitations:

    • A child must be a sub-task
    • Only one level, a sub-task cannot have another child.

This custom child-issue link can be used to replace the Jira standard link and bypass the above limitations. 

 

1.2. User Data

This administration tool allows to manage user data about context of gantt-charts stored in server and User Calendar.

1.2.1. Context Management

When you select a user in the Users list, all his/her are grouped by the Gantt-chart type, which are filled in the "Gantt-chart type" list. By default, only the current user is listed in the Users list. You can add a specific user by clicking the button "Add" or you can all users using the button "Load All". The "Load All" may take some time if there are a lot of users in Jira.

When you select a Gantt-chart, all contexts for this Gantt-charts are displayed in the "Contexts" list. Below each list, a button "Delete" can be used to remove the selected data from Jira server. 

List

Description

Mutilple selection

Contexts

Delete only the selected contexts

Yes

Gantt-chart types

Delete all contexts of the selected gantt-charts 

Yes

Users

Delete all contexts of the selected users.

Yes

 

1.2.2. User Calendar

Same as the context data above, when you select a user, its calendar can be edited as below:

After the modifications of fields, you need to click the button "Update" to save them.

1.3. Team Working Schedule

JGCP relies on the one parameter defined in Jira HoursPerDay to calculate the start date and End date of an issue through a duration. The format of this parameter must respect the locale    Project Planning relies always on a detail working schedule to make a precise and detail planning. A working schedule can be difference not only from one country to another, but also from companies in same country. Hence, a flexible working schedule tool is the primary element in a task time planning solution. 

JGCP relies on the one parameter defined in Jira HoursPerDay to calculate the start date and End date of an issue through a duration. The format of this parameter must respect the locale. 

1.3.1. Week-End

This panel defines the working calendar of week.

1.3.2. Non-Working Days

This panel completes the definition of Week-end above to add individual holiday. 

1.3.3. Working Days

This panel allows to turn the week-end as working-day.. 

1.3.4. Daily Schedule

This panel defines the working hour in a working day.  

2. Performance

Here are some basic rules to respect to keep the JGCP in good performance. All measures to take here is to minimize the issues to load.

2.1. Appropriate configuration of Jira and Database

Jira is an application developed in Java. By default, Java virtual machines are allocated 64 MB of memory, no matter how many gigabytes of memory your server may actually have available. 64 MB is inadequate for medium to large Jira installations, and so this needs to be increased. Here is a documentation on this tropic:Increasing Jira Memory The performance of database used by Jira could be another bottleneck. It should be configured and optimized correctly.   

2.2. Change already released versions to "Released" state

When a version gets released, it'd better to change it immediately as the state "Released". This minimizes the number of issues to load at the bootstrap.

2.3. Minimize unscheduled issues and versions.

Unscheduled issues have not a due date. They are not part of the query by the timeline. So at the bootstrap, all unscheduled issues will be loaded and displayed.

2.4. Minimize users

In Jira, there are 3 groups of users:

  1. Administrators
  2. Developers
  3. Users

 

The best-practice is to put each user in some groups and set the permission of project per group.Another possibility is to enable some specific users to use gantt-chart via "Global" administration. 

2.5. Minimize Projects for gantt-chart

You can enable some specific projects to use gantt-chart via "Global" administration. 

3. Permission & Security

Gantt Chart Project for Jira respects totally the security scheme of Jira.

4. Modifications in Jira

One of the main design goals is to use maximum existing elements and minimize the introduction of new elements in Jira system. But for some concepts, in order to work correctly to provide a complete Project Management solution, JGCP has to extend some Jira model and concepts. Here is a summary all elements created by JGCP in Jira.

Element

Name

Nature

Description

Field 

Units

Mandatory

It is used for the partial time planning.

Field

PercentDone

Mandatory 

It is used to turn on the manual management on progress state, and keep the value.

Field

DueTime

Mandatory

DueDate contains only the Date information, all hour and minutes are left out. It is used to complete the DueDate to store the hours and minutes.

Link

Child/Parent

Optional

N-level sub-issue support.
If this Link is not provided in General panel of Administration, the only standard Sub-task of JIRA will be used.

Link

Finish-to-Start dependency
Finish-to-Finish dependency
Start-to-Finish dependency
Start-to-Start dependency

Mandatory

Standard dependency management.
In case of uninstallation of JGCP, these links can be deleted.

5. Upgrade guide

When you upgrade to a new version of our plugin, you need to make sure that your license is still valid for the maintenance. If not, you cannot use the new version of our plugin and furthermore, you may have a problem to find the version of you have used. 

We recommend the following steps:

Write down the version number of the current plugin and save the plugin jar in a safe place Install a new version Start Jira, If you have any problem, you can go back to the previous installed version. 

 

 

 

  • No labels