Blog

Many users encounter situations where they’ve created redundant tasks or lists within a project. A common scenario involves having multiple similar items that could have been consolidated. This post addresses a frequent question regarding combining these tasks and offers a practical solution.

A user recently inquired about merging duplicate tasks within a project. The initial response from Nikola Perisic highlighted that the platform, Jira, lacks a direct feature for combining issues. Instead, the recommended approach is to create a link to the duplicate task and add it to the primary item. Nikola clarified that only one issue can be linked to a single item.

Following this guidance, Santana Lor then asked if multiple issues could be linked to the same item. Nikola confirmed that this is not possible. Santana further inquired about hiding the linked task or list after it’s been added, specifically asking if this could be done without deleting the original item from the project.

Ultimately, the solution involves linking duplicate tasks to a single parent task. While hiding the linked items is not a direct function, managing the project effectively through careful task organization remains key.

Source: https://community.atlassian.com/forums/Jira-questions/Combine-multiple-task-list-in-a-project/qaq-p/3057806

As an organization administrator, you should automatically possess access to all Atlassian products, including Jira Product Discovery. However, some users encounter difficulties assigning themselves licenses, even when holding administrative roles. This article addresses a common issue and provides a straightforward solution.

The problem often arises when a user is inadvertently removed from the relevant product access group. This removal can result in a loss of access, despite the user’s administrative privileges. To resolve this, administrators should verify their membership within the designated product access group. Specifically for Jira Product Discovery, navigate to “Product access” in the left-hand menu. Within this section, identify the group to which you should be added and follow the instructions to re-integrate yourself.

Fortunately, the issue was quickly identified and resolved in this case. As Adam Rypel noted, the user’s access was lost due to removal from the product access group. By confirming membership within this group, the access was restored.

Source: https://community.atlassian.com/forums/Jira-questions/Unable-to-assign-license-to-myself-as-an-organisation-admin/qaq-p/2606499

Introduction

This article addresses a common issue encountered when utilizing a database picker field in Jira, specifically the appearance of a “- null” string at the end of dropdown selections during editing. We’ll outline the problem, analyze the root cause, and provide a straightforward solution.

Main Content

The problem involves a database picker field that, while functional, displays a trailing “- null” within the UI when a value is selected from the dropdown. This occurs solely during the field’s edit mode and disappears when the value is actually saved. The underlying SQL query, as shown in the provided configuration, appears to be generating this string when handling null or empty values in the `INITIATIVE_NAME` field.

The solution, as suggested by Tuncay Senturk, involves modifying the `renderOptionHtml` function. Specifically, replacing the “No Name” string with an empty string (“”) resolves the issue. This eliminates the trailing hyphen and ensures a clean display of the selected initiative ID and name. The corrected function is: `renderOptionHtml = {String displayValue, GroovyRowResult row ->def init_id = row[1]?.toString() ?:””def init_name = row[2]?.toString() ?:””$init_id – $init_name”}`.

Conclusion

By adjusting the `renderOptionHtml` function to handle null values gracefully, the “- null” string is eliminated from the database picker field’s display. This simple change provides a clean and accurate representation of the selected initiative data, resolving the reported issue.

Source: https://community.atlassian.com/forums/Jira-questions/Database-picker-field-showing-null-at-the-end-of-drop-down/qaq-p/2894225

Many users encounter the “Atlassian updated” notification within Jira, which can be disruptive to workflow. This message indicates a system update, but it’s often persistent. Fortunately, there’s a straightforward solution to manage this notification.

The notification is typically a custom announcement added by the Jira administrator. If you hold this role, you can resolve the issue by navigating to Settings > System > User Interface > Announcement banner. This section allows you to disable or modify the banner, effectively silencing the “Atlassian updated” message.

By following these simple steps, Jira administrators can quickly address this common notification concern and maintain a more focused and productive workspace.

Source: https://community.atlassian.com/forums/Jira-questions/How-to-hide-the-Atlassian-updated-notification/qaq-p/3057822

Introduction
When managing multiple teams working on a single project, determining the optimal Jira project structure can be a complex decision. The question of whether to utilize multiple projects or a single project is frequently raised, particularly when considering factors like team visibility and workflow efficiency. This article explores a common scenario and offers a practical solution based on best practices.

The Dilemma
A team has established two Jira projects to accommodate two distinct teams – one focused on coding and integration, and the other on server architecture. Initially, this approach was implemented to prevent confusion and ensure team members only viewed relevant tasks. However, team members are now questioning whether a consolidated project with multiple boards would provide better overall project visibility.

The Solution
The most effective strategy involves maintaining separate Jira projects but utilizing multiple boards within each project. Each board should be filtered to focus on the specific needs of a team. For example, one board could be filtered by “Project = A” while another could use a label like “for-team-A”. This allows each team to maintain a clear view of their assigned tasks without being overwhelmed by irrelevant information. Furthermore, the Product Owner and Scrum Master can utilize a third Kanban board to provide a consolidated overview of the entire project.

Conclusion
By strategically employing multiple boards within separate Jira projects, teams can achieve both focused task management and comprehensive project visibility. This approach addresses the concerns regarding confusion and irrelevant information, ultimately streamlining the workflow and enhancing team collaboration.

Source: https://community.atlassian.com/forums/Jira-questions/To-use-2-Jira-projects-or-just-one/qaq-p/2606522

Many users have recently transitioned to Jira Cloud and have encountered a challenge regarding the epic panel within the backlog. Previously, the panel included a search bar, allowing for efficient navigation between epics directly within the interface. However, the current Jira Cloud version, expanded via the “E” button, lacks this convenient feature.

While the Epic dropdown menu at the top of the backlog offers a search function, it doesn’t effectively address the primary need for rapid navigation between epics for Product Owners. This limitation has prompted a question within our community regarding the restoration of the search bar.

A change request, JSWCLOUD-21463, exists to address this issue. Users are encouraged to add their vote to this request to demonstrate demand for this functionality. This change request provides a pathway to reinstate the missing search bar within Jira Cloud.

Source: https://community.atlassian.com/forums/Jira-questions/Jira-Cloud-Epic-Panel-in-Backlog-Missing-Search-Bar/qaq-p/2894331

Considering the ACP-120 certification? Many individuals are exploring this option, and it’s understandable to seek guidance on preparation and its value. Let’s examine the key considerations for those planning to undertake this course.

One common question revolves around the worth of investing time and effort into the ACP-120 exam. While it can certainly elevate your chances of securing interviews, it’s important to recognize that this certification isn’t always a mandatory requirement.

A valuable resource to consult is the YouTube video by TheJiraLife, specifically focusing on the 27:50 mark, which offers insightful preparation strategies. Additionally, Atlassian Learning provides practice questions tailored to the exam content.

Ultimately, the decision to pursue the ACP-120 depends on your individual career goals and the specific demands of your role. However, utilizing resources like the recommended YouTube video and Atlassian Learning practice questions can significantly enhance your preparation.

Source: https://community.atlassian.com/forums/Jira-questions/Hi-I-am-planning-to-take-ACP-120-prep-course/qaq-p/3057832