Release Notes for 10.29

New Enhancements

Team and Sprint configuration

Visibility on user allocations across sprints and teams

On team and sprint configuration, a Scrum Master or another person editing or viewing allocations is now warned if a team or sprint member is allocated in other teams or sprints and can check the user’s allocations across teams and sprints.

Icons highlighted on a screenshot will inform a Scrum Master or other person editing or viewing allocations that a user is allocated in other teams or sprints. Clicking this icon will open a dialog box with detailed information about the user's allocation in:

  • Other teams (when opened from the Allocations dialog box on the team's slide-out panel):

 

  • Other Sprints (When opened from Allocations dialog box on the Members tab of the sprint's slide-out panel):

See also

Create a Sprint

Create Agile Teams 

Recycle Bin for Defects and Tasks

Recycled bin functionality is now available for defects and tasks. Now when deleting a defect or a task, it’s not permanently removed from the application but moved to the Recycle Bin. From the Recycle Bin, a user can restore a defect or a task with all its attributes or delete it permanently from the application.

See also

Delete and Restore Backlog Work Items

Roadmaps

  • Moved Roadmap names to the bar

On the Roadmap Work View, the work item names have been moved to the bars to open up more visual real estate. This doesn’t mean you can’t view the work item names as a column; this is now an option in Custom Columns under View Configuration. Clicking the bar names will slide out the details panel, and hovering will give you the full name of the item.

  • Story roll-ups background color auto update on drag

Story roll-ups were hard to read and were often lost when users dragged a bar with roll-ups showing white. The color now dynamically updates as users drag the bars.

See also

Visualize Roadmaps in Work View

Program Board

In Extra Configs, users can now toggle on a row that renders all features that don't have stories assigned to a team.

See also

Program Board 

Excluding Time Tracking Release Vehicles in JIRA

When using Time Tracking, a release vehicle that’s only used for Time Tracking has the option to be omitted from the JIRA sync. When this option is turned on, users will not see this release vehicle as a fix version in JIRA.

See also

Create a Release Vehicle for an Actual Release to Market

Snapshots

When allocating a budget for organizations under snapshots, the view now shows the clear organizational hierarchy instead of a flat list. The roll-up also appears to track the budget against what has been allocated.

See also

Create a Strategy Management Snapshot

Team Configuration

Added the ability to show the user’s external ID in team configuration. This enhancement will be useful for large companies that might have users with the same first and last names.

You can turn this option on the Users tab of the Platform settings in Administration. When Show External ID along with First Name and Last Name is turned on (set to Yes), the user’s External ID will appear in the Members selection drop-down menu for Agile, program, and portfolio teams, and sprints.

See also

User Record Settings

 

Defect Areas Fixes

Tasks

  • Removed the ability to assign a task to an accepted story via import.

Backlog

  • Updated the Backlog to show the Product column for stories when it was selected in the Columns Shown dialog box.
  • Fixed an issue in IE where the Backlog orphans screen was not functioning the same as in Chrome.

Objectives grid

  • Added the ability to sort the objectives grid by the Program column.

Milestones

  • Fixed an issue where epic's Fixed-Date Milestones wouldn’t render with only a target date set.

  • Fixed an issue where epic's Fixed-Date Milestones wouldn’t render if no objectives existed.

Team Room

  • Fixed the Capture functionality in the Team Room reports. Now a user can capture the Sprint Progress, Sprint Health, and Capacity reports. 

Work Codes

  • Users can now search work codes by a description as well as a title on the feature's and epic's slide-out panels.

Roadmaps

  • Fixed an issue where the delineation defaulted to semicolon on the Roadmap CSV export.

  • Fixed an issue on Roadmaps where filtering by theme on parent epics was not rendering their child capabilities – addressed all other scenarios where children we unintentionally filtered out.

  • Fixed an issue when program increments had identical start and end dates on the Roadmap; it was duplicating work that existed in both program increments.

Misc.

  • Fixed an issue where group release vehicles were not applying correctly as a filter in the Work Tree when selected on the Configuration bar.

  • Performance updates have been made to the Configuration bar. It now loads faster. Additionally, the auto-filter functionality is more responsive when typing in a name in the search area, especially in environments with a large number of portfolios, programs, and PIs.
  • Performance updates have been made to the advanced configurations on the Configuration bar. It now loads 230% faster.
  • Fixed an issue with the warning about the required Needed by field even when Needed by date was defined. Now, this warning appears only when the Needed by field was set to required and the user tries to save a dependency with no Needed by date set.

  • Fixed an issue with child features count in the epics grid. Previously deleted features were counted against total in the Features Count column in the epics grid.

  • Updated color coding for epic states in Portfolio Room. Now state bubbles for epics in Portfolio Room are tied to color coding scheme defined by the user.

  • Updated label for the option that allows users to include the list of children objects in export to describe functionality in a cleaner way.

  • Updated the Sprint Defect Trend report to show defects closed as a burnup line. Before this fix, it was spiking below zero on the Y-axis.

  • Removed Points from the Progress widget in the Team Room as it’s impossible to identify a portion of points assigned/completed by a user.

  • Fixed an issue with the parent epic, capability, and feature filters not working on maps. With these changes, the user will be able to filer a list of items that can be added to a column on the story, feature, or capability map based on their parent.

  • Updated the application not to close a sprint when running a stand-up on the last day of the sprint. Previously, the sprint was automatically closed when finishing the stand-up on the last day of the sprint.

  • Updated the Work Tree to shorten work item names based on the same rules. Previously, the epic's title was shortened even when there was space for the whole title. Now titles for all work items are limited to 100 characters. Longer titles are cropped.

  • Fixed an issue with the objectives tooltip in the Program Room. Now it shows only the title; odd tags were removed from the tooltip.

  • Fixed an issue with the Dependency Wheel not showing information for the selected Team. Now when clicking on the Dependency Wheel slice, the information for the appropriate team appears on the slide-out panel.

  • Fixed an issue with the Team Room not displaying stories when switching from one sprint to another. Now when switching to the Select One option in the Sprint drop-down menu and back to some sprint, the Team Room will load all data that is tied to selected sprint.

  • Updated the sprint's Members tab not to show a warning if a user is assigned to a team and has a role defined at the team level. The user's role is imitated from team to sprint, so warning to select a role is not needed.

  • Updated the grid on the Select a Feature dialog that appears when searching for a feature from the dependency's slide-out panel. Previously, the grid had select check boxes that did nothing. We have removed the check boxes and added an instruction to click an item to select it. These changes were applied to all similar dialog boxes.

  • Added the ability for the Jenkins connector to map Build Streams to Jobs that are held within a folder in Jenkins.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.