Product Updates

We hear from you, and respond every month.
Here are the latest updates to Jile!

It only gets more exciting with the arrival of Jile 3.0! Hope you enjoy Jile 3.0 as much as we enjoyed building it for you!

In this digital world, the challenge is for organizations having multiple structures, methodologies and practices to adopt and scale Agile, that too in a consistent and repeatable manner.

Jile 3.0, will be a more powerful and flexible platform that can help organizations of all sizes deliver valuable software by adopting and accelerating Agile software development, scaling Agile across the enterprise, and transforming them into new age Digital enterprises. The core capabilities of 3.0 are summarized below. Please share your feedback at!



Configurable Organizational Hierarchy

A configurable hierarchy, representing the various Business Units, Portfolios, Product Groups or Projects that forms the organizational structure can be setup for each Workspace. Agile Planning and Execution across the hierarchy is managed in the workspace.
[As Workspace Admin, navigate to Workspace Setup Settings Work Area Types]

Note: While creating a workspace through templates, default 'Work Area types' that define the hierarchy are created. These can be further customized based on organizational structures.

Synchronized Release Planning and Tracking across multiple organizational levels

Release schedules created at Enterprise or higher levels ensure that all the underlying 'Work Areas' in the hierarchy borrow the same schedule. This helps all units in the Enterprise to synchronize planning and tracking, both output and outcome from these releases at all levels.
[Navigate to Release Schedule]

Enterprise Reporting and Roll-ups

With Jile 3.0, data from all the 'Work Areas' are rolled-up across all levels to the higher levels, all the way up to the Enterprise Level. Configurable reports at the Enterprise level can give complete visibility into the delivery progress across the enterprise structure.
[Navigate to Work Area (Parent or Topmost) Reports]

Capabilities as Backlog Items

Capabilities are high-level Product or System characteristics. For large systems, requirements are managed as a backlog of 'Capabilities' first, which are further broken down into Features and Stories. In the Product Backlog, 'Capabilities' can be managed and further broken down into Features and planned into releases.
[Navigate to Product Backlog Capabilities]

Team Dashboards

Intuitive 'Team Dashboards' with many real-time metrics like Burndown, Cumulative Flow, Story Summary and so on are available, giving insights into the delivery progress at one glance.

Refreshed Interface for Boards

All the boards namely, Initiative Board, Product Backlog, Team Backlog, Task Board, Test Board and Issue Board have a refreshed interface with a 6 column layout, enabling you to see more data. You can also collapse to hide columns.

SAML Support

Jile supports SAML based Integration that enables users to be authenticated via Enterprise LDAP or Active Directories. This enhances security and governance.


Jile 3.0 supports REST APIs for all key entities. This will enable teams to read data from Jile or update data into Jile, thereby building interfaces to 3rd party systems in the ecosystem.

Other Updates:

  • Workspace Definition- A 'Workspace' is a logical container to manage the Agile Planning and Execution tracking for an Organization. The 'Organizational Structure' is defined as a hierarchical set of Work Areas.
  • Workspace Templates- While creating a workspace, any desired 'Template' can be selected. A 'Template' pre-populates a set of hierarchical 'Work Area Types', defining a 'Structure' supported in the Workspace.
  • Work Area navigator now displays the organizational structure with the Work Area types.
  • You can now break down large initiatives into smaller 'Sub-Initiatives'.
  • Release Versions- All 'Component Versions' released as part of one or more 'Release Schedules' can be viewed. The list of Features and Defects released as part of a 'Component Version' can be linked to these versions.
  • Modules namely, Initiatives, Personas, Constraints, Components, Backlog, Versions, and Schedule show data corresponding to the 'Work Area' and the data rolled-up from the 'Child Work Areas'.
  • Enablers- An Initiative, Capability or Feature of type 'Enabler' are visually shown on all cards.
  • With 'Code Commits' into GitHub, developers can also use custom 'Tags' to update Story or Issue status in Jile.

Jile speaks Spanish now! As we strive to expand our global footprint, this month we are happy to announce our support for multiple languages. Introducing Jile's multi-lingual support, starting with Spanish. Watch out for many more in the coming releases.

Here are quick highlights and other updates of this roll out that will help you improve your ways of working on Jile. Please share your feedback at!



Multi-lingual Support

Jile is architected to support multiple languages. Currently, Jile supports English and Spanish.
[ To choose your language -
Navigate to Language Icon, and select your language settings ]

Cycle time and Through-put metrics for Kanban Teams

Kanban teams can view their 'Cycle Time' and 'Through-put' on a weekly basis. The 'Cycle Time' is the average time taken for stories to get done, and 'Through-put' is the number of stories done per week.
[ Navigate to Team Level of a Kanban Team and click on 'WORK' and the 'Track' icon ]

Detailed Synchronized Planning for Kanban Teams

The detailed planning screen for a Release, which is used in the big room synchronized planning, can now be used by Kanban Teams. These teams can:

  • Break features into stories
  • Classify the priority
  • Validate if the stories taken up in the release are in line with their average through-put
[ Navigate to Release Schedule Plan Iteration Plan ]

Component Versioning

You can mention the versions of the components being moved as part of a Release Schedule and tag the respective features and defects to this version.
[ Navigate to Release Schedule Plan Iteration Plan ]

GitHub Code Commits traceability to Stories

GitHub Code commits against stories will now show the list of modified files with a direct link to the change history in GitHub. [ In a domain with GitHub Integration configured, navigate to Story single page view, go to 'Code Commits' Tab ]

Other Updates:

  • Product Backlog will only have those features that are not planned in any Releases. Prior to this, features as part of the ongoing releases, along with their statuses were also present in the Product Backlog.
  • Role based permission is applicable for moving the Initiatives, Features and Stories to the 'Done' or the baseline state.
  • Reports Module is enhanced such that Tables and Charts can include 'Custom Fields'.
  • GitHub code commits against stories will now show the list of modified files with a direct link to the change history in GitHub.
  • The notion of 'Kanban support team', which was present to support the Production support scenario, will be discontinued. Teams could be either of type 'Scrum' or 'Kanban' that represent cross-functional agile teams, delivering software incrementally.
  • For Domain Administrators, under the Usage Analytics, you can download the list of Active or Inactive users in your domain.

It is New Year folks! And this New Year, Jile brings to you the bundle of joy with its brand new capabilities!

Out of the many capabilities rolled out for this release, the “Kanban for Development Teams” is the most exciting one. Scaling Agile is about 'Team of Agile Teams', synchronously planning and delivering value incrementally. On the ground, agile teams can follow either 'Scrum' or 'Kanban'. In Kanban, cross-functional 'Feature teams' can choose to operate through a continuous flow of features and stories, thereby constantly aiming to improve the overall cycle time and through-put.

Here are quick highlights and other updates of this roll out that will help you improve your ways of working on Jile. Please share your feedback at!

Jile wishes you all a very Happy New Year 2019! Stay connected!



Kanban for Development Teams

An Agile team that is part of a large product of 'Team of Teams' can choose to follow a Kanban methodology. The team works on a continuous flow of Features and Stories within a common release scope that is shared by many agile teams.
[ Navigate to Manage Teams New Team (of type Kanban – Dev) ]

Work board of Kanban Development Teams

Kanban teams will have a board to view the flow of Features and Stories. They can associate a Standard, Urgent or Fixed Date priority to stories, track their cycle time and through-put. The teams can also manage their 'Work in Process (WIP)' limits and pull work based on these limits. [Navigate to Team Level of a Kanban Team and click on 'WORK']

Integration with Git Hub

The out-of-box integration with Git Hub will now enable users to install the Jile GitHub app, and connect the GitHub repository to a Jile Workspace. Once the connection is established, developers can tag a user story and its status to a commit. Hence, every commit will be tagged and shown against the user story in Jile.

Notifications for Feature and Story Owners

When owners are assigned to features and stories, the respective owners are notified in the 'Notifications' section.

License consumption and Usage Tracking

Domain administrators can track the license consumption and adoption by users on-boarded. The trend of adoption can be visualized on a line graph.

Other Updates:

  • Introducing 'Status - Backlog | Sub-Status – Ready' as default status for Features and Stories. All the created features and stories will have the Status as 'Backlog' and Sub-status as 'Ready' by default, until they are planned into a Release or an Iteration respectively. Once these features or stories are planned into a release or iteration, the status gets updated to 'To Do'.
  • Move to 'Next Release' option for Feature cards in 'Release Backlog', such that any feature can be moved to the Next Release or the Product Backlog.
  • Feature, Story and Defect 'Completion Date' is shown in the single page view. This specifies the date on which the entity was moved to 'Done' [the Baseline status]. Users can also update this date through the 'Edit' option.
  • In addition to the existing grid view, a visual representation of dependencies of stories in the Story single page view is shown.
  • Objectives also have a rank, and users can prioritize the objectives through drag and drop.
  • Product and Area 'Delete' Option is now available.
  • The Enterprise Administration, through which Domain Administrators define enterprise settings like the enterprise name, tagline, adding workspaces and so on, is moved to a separate area called the 'Enterprise Setup'. It can be accessed from a new 'Setup icon' on the Product Navigator.
  • Domain Administrator can configure specific email subdomains, which will be allowed for registration by users. This is to prevent unauthorized email IDs of users in Jile.
  • Custom Fields for 'User Entity' is available now.