Skip to content

v1.5.101
Compare
Choose a tag to compare
@JimmyKB JimmyKB released this 10 Mar 10:06
· 112 commits to master since this release
v1.5.101
9bb2fb6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

v.1.5.101 - 2023-03-10

Improvements

• Risk upgrades - Added filters, options, and more
• Added option for on-premises environments to update the license key.
• Start & Target date view can now fetch items based on start and target date instead of iterations with a new toggle.
• Added load charm for bugs.

Bug fixes

• Scale can now load more than 20,000 work items.
• Adding a new team to an ART rearranged the order of the teams, new teams are now added to the bottom and the order is kept.
• Editing more than one capacity field in Start & Target date boards disabled the function.
• Added correct fields in the configuration view when first installing Scale and changing work item types.

Risk upgrades

We've added more functionality to risks. Now you're able to toggle if you want to include the project's default area or not.

We've added areas as a filter function:

Updating license key on-premises

If you're using our offline solution you can now update with a new license key if you head into Collection Settings -> Scale -> Subscription. A new button "Edit license" will be visible.
Edit On-prem License2

Fetching work items based on Start and Target date

We've added more functionality to our Start & Target date view. With this new option, you're able to load work items outside of the iterations/sprints and load items based on start & target date as well.

In this example. I'm able to load a work item from another iteration, as long as the Start & Target date is within the correct time period.
I've got 5 sprints visualized in Scale, but the feature is put on the parent iteration PI1, and I'm still able to load the work item in the board.

Added Load charm on bugs

If teams are managing bugs as requirements and if you assign it story points, Scale will add the story points/effort of that bug to our load and capacity function. This is also shown within Scale:

Assets 2
Loading