04 - Milestone administration

From version 1.12
   4.1 General information


The Milestones page displays the following informations :


  • A button [Back] permits to go back to the administration page.

  • A control button [Active/Inactive].

  • A button [Add] permits to create new milestones.

  • A button [Clone] permits to copy an existing milestone.

  • A button [Synchronize] permits a milestone to be automatically with all or part of the objects of another milestone.

  • A button [Remove] permits to remove milestones.

  • The table shows the milestones set in the application.


   4.2 Creating a new milestone


C
lick on the button [Add].To create a milestone, follow this procedure:

  1. A pop-up opens,you must fill in at least the compulsory informations : Name and Term Date.

  2. Click on the button [Add].

  3. The milestone is created and appears in the table.

FOCUS

The attributes "Scope", "Owner", "Creator" and "Creation Date" are automatically filled by the system. If the status is not specified when creating, the status 'Planned' will default.

The notion of 'Scope' should be known for the use of a milestone after its creation, for information only an administrator or project manager can create a milestone, according to the profile that created the milestone scope will be different.

In the case an administrator create a milestone:

• The milestone scope will be 'Global', a global scope milestone can be associated with all the projects and objects as far as status allows.

In the case a project manager create a milestone:

• The milestone scope will be 'Limited', a limited scope milestone can only be associated to projects included in this scope, and by any user with a  'Project Manager' profile on one of these projects, or by an administrator as far as the status allows it. It can not be associated to a project that is not part of the association scope  of the milestone. The association scope is formed from all projects on which the profile 'Project Manager' has the rights.


   4.3 Deleting a milestone


The procedure for deleting a milestone can be performed as a unit or in bulk:

     4.3.1 Removing only one milestone

  1. Click on the button [Basket] in front of the milestone you want to delete.

  2. A pop-up opens, click on the button [Confirm], the pop-up closes-up, the milestone is delete.

FOCUS

All projects and objects that are bind to the milestone will be disassociated.


     4.3.2 Removing mass milestones

  1. Select the milestones you want to delete and click on the button [delete].

  2. A pop-up opens, click on the button [Confirm], the pop-up closes-up, the milestones are delete.

FOCUS

All projects and objects that are bind to the milestones will be disassociated.



   4.4 Cloning a milestone

To clone a milestone, follow this procedure:

  1. Select the milestone you want to clone.

  2. Click on the button [Clone].

  3. A pop-up opens, you must fill in the fields : Name, Status, Due Date and Comment, you can also select the duplication options about the requirements, test cases and campaigns.

  4. Click on the button [Add], the pop-up closes up and the cloned milestone appears in the table.

FOCUS

For information only an 'Administrator' or 'Project manager' can create a milestone, according to the profile that created the milestone scope will be different.

In the case an administrator create a milestone:

  • The milestone scope will be 'Global', a global scope milestone can be associated with all the projects and objects as far as status allows.

In the case a project manager create a milestone:

  • The milestone scope will be 'Limited', a limited scope milestone can only be associated to projects included in this scope, and by any user with a  'Project Manager' profile on one of these projects, or by an administrator as far as the status allows it. It can not be associated to a project that is not part of the association scope  of the milestone. The association scope is formed from all projects on which the profile 'Project Manager' has the rights.

It is important to know this notion because depending on the original milestone (source milestone) and the profile which will create a new milestone by duplication (target milestone), the result will be different.

The original milestone must be to the status' In Progress' or 'Completed'.
 
The attributes "Scope", "Owner", "Creator" and "Creation Date" are automatically filled by the system. 

In the case duplication of options on the requirements 
or / and test cases have been checked, the cloned milestone is automatically associated with the objects (Requirements, test cases) of the original milestone according to what has been checked.

According to the user profile 'Administrator' or 'Project Manager', the milestone resulting from duplication might not recover all properties of the original milestone.

From an administrator profile, milestone created from duplication recover all the properties of the original milestone (Scope, perimeter, associations, owner)

With
a project manager profile, milestone created from duplication recovers the original associations milestone in terms of its scope :

Global scope (created by an administrator): Only objects in the perimeter of the original milestone on which the project manager profile is the project manager.

Limited scope (created by the project manager himself): All objects associated with the original milestone.

Limited scope (created by another project manager): Only objects in the scope of the original milestone on which the project manager profile is the project manager.

The milestone created from duplication will each time be in limited scope and owner of the project manager.

Reminder: The objects refer to requirements, test cases and campaigns of a project.



   4.5 Synchronizing milestones

To synchronize a milestone, follow this procedure:

  1. Select the milestones you want to synchronize.

  2. Click on the button [Synchronize].

  3. A pop-up opens, you can choose as target one of the two selected milestones or an union between the two milestones.

  4. Click on the button [Confirm], the pop-up closes-up, the milestones are synchronized.

FOCUS

Synchronization enables a milestone (target milestone) to be automatically bound to all or part of the objects bound to another milestone (source milestone).

The behaviour of the feature 'Synchronization' is influenced by several criteria that is useful to know : 

The user profile : two profiles are empowered to synchronize : the administrator and the project manager. Both profiles have different rights to synchronisation.

The administrator profile is not subject to any restrictions for synchronization except for the status of milestones.

For a project manager profile, synchronization only impacts the objects belonging to projects where it is the project manager.

The scope of selected milestones : Synchronisation uses the principle of range that was discussed earlier in the chapter of the cloning.

The perimeter of selected milestones :The perimeter of a 'Restricted' range matches all the projects on which the project manager who creates the milestone, has a project manager profile.
The perimeter of a 'Global' range extends to all the application projects.

The status of synchronized milestones : Synchronization is only possible if the target milestone is in status 'In progress'or 'Finished'. As part of a union, the two selected milestones must be in status 'In progress' or 'Finished'.

The synchronization modes : 

The are three synchronization modes : 

  • Two modes without reciprocity :
            - A -> B : The target milestone 'B' will be bound to objects of the source milestone 'A'.
            - B -> A : The target milestone 'A' will be bound to objects of the source milestone 'B'.

  • A mode with reciprocity : 
            - Union : Milestones synchronized in 'Union' mode will mutually share their associated objects.

 

Jalon A Scope

Jalon B Scope

Synchronization mode

A -> B

B -> A

A<->B (union)

Globale

Globale

X

x

x

Globale

Limited

V

x

x

Limited

Limited

v

V

v

 

Caption :

A->B : The target milestone ‘B’ will be bind to the milestone objects  ‘A’ as a source

B->A : The target milestone ‘A’ will be bind to the milestone objects  ‘B’ as a source

V : The synchronization is possible but under conditions

x : The synchronization is not possible



FOCUS

In the synchronization pop-up is located an accessible option in case the project manager has selected the option 'Target' and that he is the owner of the target milestone. Otherwise, it is not usable.
If the project manager checks the box, the source milestone projects that did not belong to the scope of the target milestone will belong to the scope of the target milestone.

   4.6 Consulting/ Modifying a milestone

Clicking on the milestone name displays the information as follows:


A button [Back] permits to go back to the milestone workspace.

A button [Rename] permits to change the milestone name.

A button [Delete] permits to delete the milestone for good.

A table listing the various projects in which the milestone is associated.


     4.6.1 Renaming a milestone

To rename the milestone, follow this procedure:

  1. Click on the button [Rename].

  2. A pop-up opens,  you can enter the new name of the milestone.

  3. Click on the button [Confirm].

FOCUS

This field is compulsory, it must be less than 30 characters and must be unique.


     4.6.2 Modifying the term date

To modify the milestone term date, follow this procedure:

  1. Click on the term date.

  2. Enter the date manually or choose it from the calendar.

  3. Click on the button [Confirm].

FOCUS

The date is compulsory.


     4.6.3 Modifying the status

To modify the milestone status, follow this procedure:

  1. Click on the status (When creating a milestone, the default status is 'Planned' if no status had been chosen)

  2. From the list, select the wanted status (Planned, In Progress, Finished, Locked)

  3. Click on the button [Confirm].

FOCUS

Each status confers different rights in terms of :

  • Milestone association with a project or an object

  • Creation / removal / modification of objects associated with the milestone

 

 

Bind / Undo a milestone to a :

Authorize the objects creation

Authorize the objects removal

Authorize the objects modification

Project

Object

Planned

v

x

x

x

x

In progress

v

v

v

v

v

Completed

v

v

v

v

v

Locked

x

x

x

x

x


     4.6.4 Filling or modifying the description

To fill or modify the milestone description, follow this procedure:

  1. Click on the description

  2. Enter the wanted description

  3. Click on the button [Confirm].

FOCUS

The field description is optional.


     4.6.5 Deleting the milestone

To delete the milestone, follow this procedure:

  1. Click on the button [Delete].

  2. A pop-up opens, click on the button [Confirm].

FOCUS

In the event that the milestone was associated with a project, requirements, test cases or/and campaigns, it will be disassociated and deleted.


   4.7 Binding/ Undoing projects to a milestone

     4.7.1 Binding a project to the milestone

To bind projects to a milestone, follow this procedure:

  1. From the consultation window of the milestone, click on the button [+].

  2. A pop-up opens where you can choose one or more projects that you want to associate with the milestone. To do this, tick the checkbox in front of the project that is to be associated.

  3. Click on the button [Confirm], the pop-up closes up and the selected projects appears in the consultation table of the milestone.

FOCUS

You can filter the rows of the table with the field "Search". Help links under the table permits to select all rows, deselect all the rows or reverse the current selection.

The association to projects is only possible if the milestone is the to status 'Planned', 'In Progress' or 'Completed'.


     4.7.2 Unbinding a project to the milestone

It is possible to disassociate projects to a milestone by an unitary manner or mass.

                 4.7.2.1 Unbinding a project to the milestone unitarily

To undo a project to a milestone unitarily, follow this procedure:

  1. Click on the button [-] at the end of the line of the project you want to unbind.

  2. A pop-up open, click on the button [Confirm], the pop-up closes up, the project is unbound. (If the milestone is bind with the project objects, it will also be unbound from these objects)

                 4.7.2.1 Unbinding projects to the milestone massively

To undo a project to a milestone massively, follow this procedure:

  1. Select the projects you want to unbind and click on the button [-] in the buttons bar.

  2. A pop-up open, click on the button [Confirm], the pop-up closes up, the projects are unbound. (If the milestone is bind with the projects objects, it will also be unbind from these objects)

FOCUS

The disassociation to projects is only possible if the milestone is the to status 'Planned', 'In Progress' or 'Completed'.


   4.8 Enabling/ Disabling milestones functionalities

You can enable or disable the feature set that concern the management of milestones, for all users of Squash TM.

     4.8.1 Switching from active to inactive status

To switch milestones from active to inactive status, follow this procedure:

  1. Cick on the button [Inactive].

  2. A pop-up open, click on the button [Confirm].

FOCUS

The transition to active status, causes the appearance of a tab 'Milestone' in the spaces 'Requirements', 'Test Case' and 'Campaigns' and allows them to be associated with milestones.


     4.8.2 Switching from inactive to active status

To switch milestones from inactive to active status, follow this procedure:

  1. Click on the button [Active].

  2. A pop-up open, click on the button [Confirm].

FOCUS

The transition to inactive status, disables the feature set associated with milestones for all users Squash TM. Consequently, this causes the disassociation of milestones to the requirements, test cases and campaigns present in the application, as well as the disappearance of the tab 'Milestone' in space 'Requirements', 'Test Case' and 'Campaigns' .


   4.9 Associated rights

 


Rights

(If ¹ Administrator profil)

Administrator (Role)

Project manager

Create milestones

5 - MANAGEMENT

Y

Y2

Delete milestones

5 - MANAGEMENT

Y

Y3

Consult milestone

5 - MANAGEMENT

Y

Y

Modify a milestone/ Modify a milestone perimeter of ‘Limited’ scope

5 - MANAGEMENT

Y

Y3

Modify the milestone scope

5 - MANAGEMENT

Y

 

Bind / undo projects to a milestone from the consultation page of a milestone

5 - MANAGEMENT

Y4

Y1,3,4

Bind / undo milestones to a project from the consultation page of a project

5 - MANAGEMENT

Y4

Y1,4

 

(1) Only for projects where the user is entitled as "Project Manager".

(2) The 'Project Manager' can only create milestones with scope 'Restricted'.

(3) Only for milestones which the user is the owner.

(4) For milestones with scope 'Restricted', only for projects included in the scope of the milestone.



Subpages (1): 04 - Milestones admin.
Comments