• Making planning items mandatory in project models and projects in standard mode

    This feature already existed in Classic mode and now works in “Standard mode” as well. In project models and projects in standard mode, planning items can now be made mandatory. By making an item mandatory, it cannot be removed (by the project manager/support person) from the project schedule. How it…

  • Tasks as plan items

    On the kanban boards in the projects app, the following 3 functionalities have now been added: Be able to add labels to Kanban cards Being able to select fields on the Kanban cards Be able to create Jira items from a Kanban card and relate it to existing Jira items

  • Report on Kanban cards in the projects app

    It is possible to report on the tickets on the Kanban board (Reports > Planning Items). This makes it possible to show these items in list overviews in the application and also to include them in automatic (Excel) reports. In this report you will find both all the plan items…

  • Reduction in the number of webhooks Jira Connectivity app

    In previous versions of Fortes Change Cloud, webhooks were created per team when the various Jira teams were created in the Jira Connectivity app. These webhooks ensure that changes in Jira are synchronized to Fortes Change Cloud. As of this release, a webhook is created per application link instead of…

  • Move project reference in Jira Connectivity app

    In previous versions of the Jira connectivity app in Fortes Change Cloud, the references to the project in Jira were specified in the configurations linked to the teams (portfolio and program level). This caused many situations to require specific configurations to be created for each team. To ensure that the…

  • 2-way synchronization in the Jira connectivity app

    Before version 12.0, it was only possible to transfer information once from Fortes Change Cloud to Jira when creating items in Jira. Here, in accordance with the field mapping in the configuration linked to the Jira team, information from fields is passed through. After which there is continuous feedback of…

  • Working with multiple Agile Programs on a single Portfolio Item

    Record and show that Program contributes to Portfolio item that is not self-initiated On the Split tab of an Agile Program, you can bring in a Portfolio item. Only one Program can bring in a Portfolio item on the Split tab. However, in practice, multiple programs may contribute to the…

  • Labels and fields displayed on items in the PI schedule

    In the PI planning of the ‘Agile program app’, the items of the kanban board are shown in the left list. These are then scheduled on the right side in the different sprint of an increment. The labels and fields shown on the left side on the tickets are now…

  • New Reporting tab in Agile Program

    In the Agile program app, a reporting tab was created to display the various program items in the program in a the form of a list. In this list you can also use filters and sorting to create the desired overviews. These work in the same way as explained under…

  • Portfolio properties panel

    In the portfolio app a portfolio properties panel has been added. In the panel, a large part of the properties of the portfolio that can be set are conveniently grouped together. This makes the pages easier to read and you no longer have to search for which settings you can…