We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
How to create and configure trackers in FusionForge - FIWARE Forge Wiki

How to create and configure trackers in FusionForge

From FIWARE Forge Wiki

Jump to: navigation, search
FIWARE WIKI editorial remark:
Manual no longer in use - the forge trackers are now replaced by JIRA


Contents

Creating a tracker

Creating a tracker in FusionForge is pretty simple. We will illustrate the process by creating a tracker for “Backlog Management” within a given FI-WARE Chapter project in FusionForge.

Only members of a project with the right privileges can create trackers in that project. Check how to admin user roles in a project here (note: tutorial pending). By default, only users with the Admin role can create trackers in a FI-WARE project.

If you have the right privileges, you just have to log in into your account in FusionForge, navigate to the project home page and then click on the “Tracker” Tab.



A page showing available trackers will be displayed. In our example below, there is a “Task Force Management” tracker listed, which provides a mean for managing and monitoring task forces as well as discussion threads within the chapter. You have to click on the Admin option that is displayed at the upper left corner to get access to the home Admin page for trackers.



Following are the instructions to setup a “Backlog Management” tracker that will be used for managing the lifecycle of entries in the Backlog associated to your FI-WARE Chapter.

In order to create a new tracker, you just need to fill up the form you will see in this web page (see screenshot below) and click on the “Submit” buttom. You can setup the following information for the new “Backlog Management” tracker you want to create:

  • The name you assign to the tracker (“Backlog Management”)
  • A description of the mission for the tracker (“Provides a mean for managing the lifecycle of entries in the <name of chapter> Backlog” where <name of chapter> would be the name of your chapter)
  • Decide whether you want to make the tracker publicly available (recommended action: NO – check below)
  • Decide whether you want to allow creation of tickets by users who do not have an account in FusionForge (recommended action: NO)
  • Decide whether you want emails reporting changes to be sent to some given email address
  • Decide how long tickets are valid in the system (we suggest that you assign a value here that is long enough)
  • Info at header of some of the web pages linked to some operations in the tracker

Making a tracker publicly available means that not only you allow everyone to read tickets but allow FusionForge users (even those who have not joined your project) to submit tickets. Therefore, the recommended action for “Backlog Management” trackers linked to FI-WARE Chapter projects in FusionForge is that they are not publicly available.



You can configure a number of aspects of a tracker by clicking on the “Admin” operation under the “Tracker” tab and then clicking on the tracker:



Configuring a tracker

Managing custom fields linked to entries of a tracker

By clicking on the “Manage Custom Fields” option in a given tracker Admin web page, you will get access to the web page from which you will be able to create and configure custom fields linked to tickets in that tracker.



These custom fields will be created and linked to any ticket in addition to a set of standard built-in fields that are linked by default to any ticket in any tracker in FusionForge:


Name of field

Description

“Status”

Used to identify the status of the ticket. Will be based in the workflow you define for the tracker.

“Assigned to”

Person you can assign a ticket to. When creating a ticket, this field will show you a list of all members of the project who have been assigned a role with “Tech” privileges for this tracker. Check here to find out how to assign “Tech” privileges to users in your project.

“Priority”

A priority assigned to a ticket.

“Summary”

A summary describing the ticket. For the “Backlog Management” tracker, we suggest that we always use the Id assigned to the entry in the Backlog that will be associated to the ticket as Summary.

“Detailed Description”

Additional information which may be helpful for managers of the tracker.


We will illustrate how to add custom fields to a tracker by showing how you can setup and configure some of the recommended custom fields for the “Backlog Management” tracker in a FI-WARE Chapter project. Of course, you are required to have an “Admin” role to be able to setup this configuration.

We recommend you to create at least the following custom fields for the “Backlog Management” tracker in FI-WARE Chapter projects. Some of them were also defined for tickets in the overall “FI-WARE Feature Requests” tracker linked to the FI-WARE project in FusionForge so you probably will be able to check them accessing that tracker. Keep in mind that “Custom Field Name” matches the name that will be displayed linked to a field:


Custom Field Name

Field Alias

Type

Pre-defined values (rows/colums for Text Area fields)

Description

Issuer Keywords

issuer_keywords

Text Area

1/40

Useful for creating advanced queries

FI-WARE Backlog Entry Type

fiware_backlog_entry_type

Radio Buttoms

Theme, Epic, Feature, User-Story


FI-WARE Generic Enablers

fiware_generic_enablers

Multi-Select Box

Select proper values from list of values linked to the “Generic Enabler” custom field in the “FI-WARE Feature Request” tracker

Used to identy the FI-WARE Generic Enabler(s) a ticket is linked to

Link to Backlog Template on FI-WARE Wiki

fiware_backlog_entry_URL

Text Area

1/80

Used to register the link on the FI-WARE Wiki where full description of the backlog entry is provided

FI-WARE Release Id

fiware_release_id

Text Area

1/20

Used to identify the Release where this Feature/User-story has been planned

FI-WARE Sprint Id

fiware_sprint_id

Text Area

1/20

Used to identify the Sprint where this User-story has been planned


To create the “FI-WARE Generic Enablers” custom field, you just need to fill the boxes for the “Custom Field Name” as well as the “Field alias” and then check the “Multi-Select Box” option as the “Type of Custom Field”.



When you click on “Submit” you will see that the new Custom Field “FI-WARE Generic Enabler” has been created.

Sometimes you are not able to write down the whole name of the custom field you want to add. It’s a bug of the FusionForge tool you can easily workaround. Simply, enter the name of the custom field up to the number of characters you are allowed and click on submit. Then, edit the custom field. You will find that you can enter more characters this time.

By editing the custom field you registered you can also mark it as mandatory.



Since the “FI-WARE Generic Enablers” custom field is a Multi-select Box, you have to add choices (same applies when you deal with Select Box Custom Fields). You can add the choices just clicking on “add choices”



You just need to write down the name of each choice. At any time, you can change the order in which choices will be displayed. For consistency reasons, you should use the values displayed for the “FI-WARE Generic Enabler” field you will see when you try to submit a ticket to the “FI-WARE Theme/Epic/Feature Requests” tracker in the FI-WARE project.

Sometimes you are not able to write down the whole name of the choice you want to add. It’s a bug of the FusionForge tool you can easily workaround. Simply, enter the name of the choice up to the number of characters you are allowed and submit the new choice. Then, edit the choice. You will find that you can enter more characters this time.




Configuring how tickets are browsed in a tracker

Once you have defined all of the custom fields for your tracker, you should customize the fields listed when users browse tickets recorded in the tracker. You can do this by clicking on “Customize List” operation.



You can select not only the fields but the order in which they are listed (from left to right). As an example, if you configure fields listed as shown below:



You will see tickets in the tracker listed as follows whenever you browse de tracker:



Configuring the workflow linked to a tracker

By default, tickets in any tracker can be just opened and then closed. However, you can configure a more complex state workflow for your tracker. For doing so, you rely on custom fields of type “Status” you add to your tickets.

We will illustrate how to configure a workflow for a tracker by showing how you can setup and configure the recommended workflow for the “Backlog Management” tracker in a FI-WARE Chapter project. Again, you are required to have an “Admin” role to be able to setup this configuration.

First, as we have mentioned, you have to add a “Status” custom field we will name as “Workflow State” (it could be any other name but we recommend to use the same name for “Backlog Management” trackers linked to FI-WARE projects):



Custom fields of type “Status” have values “Open” and “Closed” as pre-defined states. You can add more states in your workflow by clicking on the “add choices” operation.



Regarding “Backlog Management” trackers linked to FI-WARE Chapters, we recommend to add a new state “Under Execution” that helps to determine whether a User-Story (Feature) is being addressed in the current Sprint (Release).




Once you have created this custom field, you can configure the workflow transitions. You can do this by clicking on “Manage Workflow” and then configuring what are the transitions you will consider valid. Find below the workflow transitions configured as valid for “Backlog Management” tickets. You can also specify what project member roles are allowed to perform a given transition:



Configuring access rights to a tracker

In order to configure access rights to a tracker, you have to go to the space for administering users and user roles.

You will, of course, be able to administer users and user roles only if you have the right privileges (typically, only users with the “Admin” role have such privileges).

You can get to that space by clicking on the “Admin” tab of your Project page and then clicking on “Users”



Users in a FusionForge project have a given Role assigned. You can learn how to create and configure Roles here.

We recommend that you review the privileges defined for the different Roles in your project. You have to select the name of the Role you want to review and click on “Edit Role”.



Roles can be assigned the following privileges linked to trackers:


Privilege

Meaning

No access

They even can’t see the tracker.

Read (create and monitor tickets)

They can see the tracker and submit tickets.

They can monitor how tickets evolve.

They can add comments to tickets.

They cannot change (other than adding comments), delete or assign tickets.

They cannot create tasks assigned to tickets.

They cannot configure the tracker (e.g., add custom fields).

Tech (devoted to solve tickets)

They own Read privileges (except they do not add comments on tickets because they are supposed to add follow-ups).

They can be assigned a ticket (because they are actually the ones devoted to solve tickets)

They can change values of custom fields in tickets but not standard built-in fields.

They can create tasks assigned to tickets.

They cannot delete nor assign tickets.

They cannot configure the tracker (e.g., add custom fields).

Admin Only (govern assignment of tickets and configuration of tracker)

They own Read and Tech privileges but cannot be assigned a ticket.

They can create tasks assigned to tickets.

They can change all fields in a ticket, delete or assign tickets.

They can forward tickets to another tracker within the same project.

They can admin the tracker.

Tech & Admin

They own Tech & Admin Only privileges. However, they can also be assigned to a ticket.


We suggest that you assign “Tech & Admin” privileges to the “FI-WARE Chapter Project Member” role while assigning the “Tech” role to the “FI-WARE Project Member” role. You may want to establish a distinction among “FI-WARE Chapter Project Member” and only assign “Tech & Admin” privileges to a few members of your FI-WARE Chapter project (e.g., people leading development of a given FI-WARE GE). For doing so, we would recommend that you create a new role “FI-WARE Chapter GE Lead” and assign it “Tech & Admin” privileges while keeping “Tech” privileges for the rest of people with the “FI-WARE Chapter Project Member” Role.

Here it is how we have setup the privileges for members owning the “FI-WARE Chapter Project Member” in the FI-WARE Data Chapter.



and the “FI-WARE Project Member” roles in the same project.


Personal tools
Create a book