Enhancements and Features
Configuration bar filtering by Organization Structure and Product: Roadmaps
The Roadmaps page now supports filtering by the Organization Structure field in the Configuration bar. When filtered by organization structure, work items are shown when the owner is a member of the selected structure or child levels of the structure. The Organization option has been removed from the Filters menu for page-level filtering.
The Roadmaps page now also supports filtering by the Product field in the Configuration bar:
- When using the Features view, features assigned to the selected product or any child products will display
- When using the Feature by Capability or Feature by Epic views, features assigned to the selected product or any child products, and the feature's parent epics or capabilities, will display
The Product option has been removed from the Filters menu for page-level filtering.
Configuration bar filtering by Organization Structure and Product: Backlogs
Backlog pages for stories, features, capabilities, and epics now support filtering by the Organization Structure field in the Configuration bar. When filtered by organization structure, work items are shown if that item's owner belongs to the selected structure or child levels of the structure.
Backlog pages now also support filtering by the Product field in the Configuration bar, depending on the product assignment of a parent or child feature:
- Story Backlog: Stories that have a parent feature assigned to the selected product or child products will display
- Feature Backlog: Features assigned to the selected product or child products will display
- Capability Backlog: Capabilities that have a child feature assigned to the selected product or child products will display
- Epic Backlog: Epics that have a child feature assigned to the selected product or child products will display if the work item hierarchy does not contain capabilities. When capabilities are enabled as children of epics, the Epic Backlog will not be filtered by the selected product.
Note: Changes for product and organization structure filtering apply to all list and kanban-based views available in the specified backlog pages.
New REST APIs available
The following objects and methods are now supported in the API 2.0:
-
Objectives can be updated using the PUT or PATCH methods
Defect Fixes
Performance | |
JIRAALIGN-1997 | The Scheduled Email Log link found at Administration > Settings > Email > Scheduled Email displays a whoops error message when clicked |
JIRAALIGN-2053 | Some users are logged out of Jira Align when attempting to access the search function from the left-side navigation bar |
API 2.0 | |
JIRAALIGN-2000 | After updating a feature through the API, some fields are edited unexpectedly |
JIRAALIGN-2063 | GET calls made for users result in HTTP 400 errors when a user is assigned to several hundred teams |
Administration | |
JIRAALIGN-2026 | Users who have system role permissions that allow the management of programs are able to view all programs, instead of only programs they are members of |
JIRAALIGN-788 | Lengthy email addresses overrun field boundaries in the Invalid Login Activity section found at Administration > Logs > Use Trend |
Backlog | |
JIRAALIGN-2029 | The Themes view of the Strategic Backlog displays “Project” in the Count column when the label should be “Epic”, tied to Platform Terminology |
Epics | |
JIRAALIGN-1976 | Date entries made for value streams from the Time/Skills tab of an epic’s Details panel are not saved |
Features | |
JIRAALIGN-1942 | After canceling a feature, the audit log incorrectly displays that the feature was deleted |
Forecast | |
JIRAALIGN-1822 | The Value Stream column on the Forecasts page does not display any changes made to Platform Terminology settings |
JIRAALIGN-1988 | An expanded section for a program increment is automatically closed when viewing the details of an epic or capability |
JIRAALIGN-1876 | The Apply Backlog Rank function does not order work items correctly |
Ideation | |
JIRAALIGN-2032 | The labels that display current filters applied to the Ideation page overlap the Apply Filters button |
Jira Connector | |
JIRAALIGN-829 |
The table found at Administration > Connectors > Jira Management > Jira Boards does not display a “No Project Found” error message after a Jira board is changed to point to a new Jira project |
Portfolio Room | |
JIRAALIGN-2007 |
Labels for program increments do not display any customizations made in Platform Terminology settings |
Program Increments | |
JIRAALIGN-1958 / JIRAALIGN-2036 | The Audit Log link disappears when loading a program increment’s Details panel |
JIRAALIGN-2025 | Web browser autocomplete suggestions block the visibility of the date picker in the Start Date and End Date fields within a program increment’s Details panel |
Program Room | |
JIRAALIGN-2050 | Lengthy team name values overrun field boundaries in the Team Progress and Team Load vs Capacity cards |
Reports | |
JIRAALIGN-2041 | The WIP report does not display statistics for capabilities |
JIRAALIGN-2044 | The Velocity by Team (Trend) report displays sprints in the reverse order on a chart’s x-axis |
Roadmaps | |
JIRAALIGN-1787 | The Chat column does not display the correct icon when there are active discussions on a work item |
JIRAALIGN-2019 | Filter settings for the Theme Group field do not display any customizations made to Platform Terminology settings |
Time Tracking | |
JIRAALIGN-1795 | Users are unable to use the User Attributes Export option in Time Tracking unless the Administration > People permission is enabled for their system role |
Misc. | |
JIRAALIGN-1970 | Text that displays below progress indicators inside of epic and feature Details panels is not aligned vertically |
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.