Mastering Jira Align: Essential User & Admin Guide

Table of Contents

1. Introduction
2. New Objectives Tree Experience
3. T-shirt Size Mapping Update for Admins
4. Sprint Details Syncing
5. Updates to Jira Project Toggle
6. Hidden Functionality Now Available in Standard Administration
7. API 2.0 Updates
8. Defect Fixes
9. Conclusion
10. FAQ

Introduction

In this article, we will Delve into the recent updates to Jira Line version 10.112, which were released to general instances on September 23, 2022, and will be rolled out to production instances on October 7, 2022. These updates cover various aspects of Jira Line, including user experience, administrative changes, syncing capabilities, and bug fixes. We will explore each of these updates in Detail to understand their impact and benefits. So, let's dive in and explore the exciting enhancements Jira Line has to offer.

New Objectives Tree Experience

One of the most exciting updates in version 10.112 is the introduction of the new Objectives Tree experience. This revamped interface provides users with a clearer understanding of their strategic goals, objectives, and key results. It offers improved guidance on progress and areas that require Attention, all while allowing users to delve into specific details when necessary. Please note that to access this new experience, users with existing Jira Online instances created before October 7, 2022, need to contact Atlassian to have it enabled. For instances created after that date, the new experience will be enabled by default. The previous Legacy experience will eventually be deprecated, although Atlassian has not provided a specific timeline yet.

T-shirt Size Mapping Update for Admins

Another significant update that administrators will appreciate is the T-shirt Size Mapping improvement. Previous versions required administrators to map the T-shirt size field exactly to the default values in Jira Align. However, with version 10.112, administrators can now map custom values, making the process more flexible and user-friendly. Additionally, the location of the mapping has been shifted from the Custom Fields mapping tab to the Jira Setup tab, aligning it with similar field configurations. This change ensures seamless workflow management for admins without impacting existing mappings.

Sprint Details Syncing

Version 10.112 introduces enhanced syncing capabilities between Jira Line and Jira Software for Sprint details. Previously, Sprints had to be generated at a team level in Jira Software, with a Sprint goal field for teams to define their Sprint iteration goal. With the latest update, this information will now sync to Jira Line as well. This improvement allows for smoother transitions between the two tools and ensures that team iteration goals are visible to stakeholders at a program or portfolio level. This synchronization enhances transparency and collaboration within the organization.

Updates to Jira Project Toggle

The Jira Project Toggle has undergone two important updates in version 10.112. First, the Detail Panel Settings now include a toggle for the jira project field within the Defect Work Item. This addition allows users to conveniently select and view the associated Jira project for each defect, enhancing project management and organization. Furthermore, the ability to require the jira project field has been moved to the Detail Panel Settings as well. Previously, this setting was accessed through a toggle on the Jira Setup tab, but it can now be configured alongside other fields' requirements. This change streamlines the process for administrators, ensuring consistent data entry.

Hidden Functionality Now Available in Standard Administration

Atlassian has made several hidden functionalities of Jira Line readily accessible through the standard Administration screens in version 10.112. Some of the noteworthy updates include mapping statuses to process steps, hiding standalone features in the backlog, grouping items in the roadmap, and configuring the ideation model. These functionalities were previously limited to Atlassian support team enablement or required additional configuration. By bringing them to the standard Administration screens, Atlassian aims to empower administrators with more control over their Jira Line instance. This update provides greater customization options and flexibility within the platform.

API 2.0 Updates

In version 10.112, Jira Line introduces updates to its API 2.0. This includes the availability of custom fields for risk work items in the API, allowing users to perform various operations such as GET, POST, PUT, and PATCH. Additionally, Atlassian has addressed the error handling for unauthorized endpoint access. Previously, users would receive a 401 error, but now, a more specific 403 Forbidden error will be thrown, differentiating it from other potential issues. These API updates enhance the integration capabilities of Jira Line and provide developers with more flexibility in managing their projects.

Defect Fixes

As with any software update, there have been several defect fixes in version 10.112. Atlassian has identified and addressed bugs related to mapping for shared features, story count on roadmaps, ranking of epics and backlog, proposing end dates on dependencies between scrum teams, and copying an epic with linked features and stories. These fixes ensure a smoother user experience and mitigate any issues that may have arisen in previous versions.

Conclusion

The updates introduced in Jira Line version 10.112 bring significant improvements to user experience, administration, syncing capabilities, and bug fixes. From the new Objectives Tree experience to enhanced API functionality, these updates aim to streamline workflows, increase transparency, and provide greater control and customization options. Whether You are an end user or an administrator, these updates will enhance your Jira Line Journey and contribute to the overall success of your projects.

FAQ

Q: How can I access the new Objectives Tree experience? A: If you have an existing Jira Online instance created before October 7, 2022, you need to contact Atlassian to have the new experience enabled. For instances created after that date, the new experience will be enabled by default.

Q: What changes have been made to the T-shirt Size Mapping feature? A: Administrators can now map custom values for the T-shirt Size field, making it more user-friendly. Additionally, the location of the mapping has been shifted to the Jira Setup tab for easier access.

Q: Can I synchronize Sprint details between Jira Line and Jira Software? A: Yes, version 10.112 allows for enhanced syncing of Sprint details between the two tools. This ensures that team iteration goals are visible in both systems and promotes collaboration.

Q: Where can I find the new configuration settings for Jira Line? A: Many hidden functionalities are now accessible through the standard Administration screens in Jira Line version 10.112. You can find the settings related to mapping statuses, hiding features, grouping items, and configuring the ideation model under the Relevant sections.

Q: Are there any fixes for known issues in this update? A: Yes, version 10.112 includes several defect fixes addressing bugs related to mapping for shared features, story count on roadmaps, ranking of epics and backlog, proposing end dates on dependencies, and copying epics with linked features and stories.

These frequently asked questions should address some common concerns regarding the updates in Jira Line version 10.112. If you have any additional questions or specific inquiries about your instance, it is recommended to consult the release notes or contact Atlassian support for further assistance.