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 request for the addition of new Themes/Epics/Features in the FIWARE Backlog - FIWARE Forge Wiki

How to request for the addition of new Themes/Epics/Features in the FIWARE Backlog

From FIWARE Forge Wiki

Jump to: navigation, search
FIWARE WIKI editorial remark:
This page is no longer in use. The Use Cases are no longer active contributing backlog items

FIWARE follows an Agile methodology in its development. This means that FIWARE Features are ultimately mapped into entries in Backlogs linked to each FIWARE Chapter.

Requests for new FIWARE Features are therefore mapped into requests for addition of entries (Themes/Epics/Features) in any of the FIWARE Backlogs. Such requests are issued via a ticketing system (FusionForge Tracker). This tutorial explains how to issue, follow-up, and close such a so-called “Request for additional entry in the FIWARE backlog” ticket.


  • A registered account at FIWARE FusionForge (see previous tutorial) and membership in the FIWARE project.
  • Creation of entry in the "Unclassified Entries Backlog" section of the FIWARE Wiki which provides full description of the entry (Theme/Epic/Feature/User-Story) that is submitted for consideration

How to Issue a Ticket

Login http://forge.fiware.org, proceed to the FIWARE project, select the “Tracker” tab, and select “FIWARE Feature Requests”



This should direct you to a page where all tickets related to requests for FIWARE features are listed, where you can click on “Submit New” to create a ticket

Provide the information related to your request. As a general rule, the more valuable and precise information is provided the better/faster your request can be handled.

  • Select the FIWARE Chapter and GE you consider relevant to your request (choose "None" if unknown)
  • Add keywords that may be useful to build personalized queries that will help you to browse the tracker later on
  • Provide URL link to the FIWARE Wiki page where full description of your proposed backlog entry has been registered
  • Provide the Id of the proposed backlog entry as contents in the summary
  • Provide additional info that may be helpful for the FIWARE team
  • Add related documents / attachments that help to understand motivation, background, requirements, etc

Please follow the convention that has been defined for the Id field in entries of FIWARE related backlogs. In the case, of entries for the Unclassified Enablers Backlog:

   <backlog id>.<category>.<name>


  • <backlog id>::= <name of UC project> | "FIWARE"
  • <category>::= "Theme" | "Epic" | "Feature" | "Story"
  • <name> is the value of the Name field of the entry, which should be a meaningful acronym.
  • <name of UC project> is the name of the UC project that issues the ticket (other UC projects may support your request, but this will documented in the "Stakeholders" field in the full description of the backlog entry published in the Wiki)

Note that you may submit information about the FIWARE Chapter and GE you believe your request fits (this are optional fields in the ticket you submit). This is indeed rather helpful information which can accelerate handling of your request, but is not mandatory.

Mind that „starred“ (*) forms are mandatory. Press „Submit“ to issue the ticket.

How to Follow-up open Tickets

Once a ticket is issued its consistency and completeness will be evaluated. If the ticket passes this step it will be assigned a ticket owner by the FIWARE support team. In addition, a task will be created and an assigned to a FIWARE Chapter leader / Chapter Architect for handling the ticket.

Check the tutorial on How to follow-up a tracker in FusionForge to find out how to follow-up open tickets.

How Tasks and, ultimately, related Tickets are closed

The decision about an appropriate approach for handling individual requests is taken jointly and case-by-case between the ticket issuer and the related task owner. Any interaction, progress, status update is to be recorded in the tracker (via commenting on tasks and tickets). This way asynchronous interaction is possible and the status / progress of a task/ticket can be recovered at any point in time.

Recall, tickets lead to assigned tasks. Once the request associated with a task if fulfilled the task will be closed by the task owner and this action is to be recorded before setting the status to “closed” along with some expressive information that allows to reproduce final settlement.

Upon this, the respective ticket can be modified by commenting that this task was closed.

If all tasks related to a ticket are closed, then the ticket will be closed as well. Again, any interaction, progress, status update related to the ticket is to be recorded by the involved persons, that is the ticket issuer, ticket owner, and tasks owners in the “comments” tab.

Personal tools
Create a book