Category: Uncategorized

Data protection is a critical concern for any Jira administrator. Many users require a method for backing up their entire Jira instance, often with the goal of storing it locally. This post addresses this common need and provides a straightforward solution.

The Atlassian Confluence documentation offers a comprehensive guide for backing up all Jira data. Specifically, the page located at https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html details the process thoroughly. This resource outlines the necessary steps for creating a complete backup of your Jira instance.

Following the instructions provided in this documentation will ensure your Jira data is securely backed up, offering a safeguard against data loss and providing a reliable recovery option.

Source: https://community.atlassian.com/forums/Jira-questions/Jira-Platform-Backing-up-all-the-data/qaq-p/2606465

Introduction

This article addresses a common challenge within agile workflows: controlling access to ticket additions and removals within active sprints. We’ll explore a solution to restrict this functionality to Product Owners once a sprint is initiated, while still allowing team members to contribute to future sprints for planning.

Main Content

Currently, there isn’t a dedicated project permission specifically designed to limit ticket additions to active sprints. However, a robust automation rule can be implemented to monitor changes to issue sprint assignments. This rule would detect when the Sprint field of an issue is modified, specifically within an active sprint. The rule would then check the initiator of the change. While this automation won’t prevent the addition of the issue, it can generate an email notification upon occurrence. Furthermore, it’s possible to remove the issue from the sprint after the change is detected, though this functionality hasn’t been directly tested.

Conclusion

By leveraging automation rules, teams can effectively manage sprint access, ensuring that Product Owners retain control over ticket additions once a sprint begins, while maintaining flexibility for future sprint planning.

Source: https://community.atlassian.com/forums/Jira-questions/Limiting-Sprint-Permissions-in-Active-Sprints/qaq-p/2894176

Introducing a more efficient method for alerting your team about newly created tickets. Many teams utilize Direct HTML templates for intake, but relying solely on mentions within the description can be unreliable. This article outlines several streamlined approaches to automate notifications and ensure your team receives timely updates.

Currently, you may be using Direct HTML to populate tickets for intake. A common workaround is to utilize mentions in the description field to notify team members. However, this method isn’t always effective. Mentions within the description do not consistently trigger notifications within Jira. To address this, consider implementing automation rules within the Project Settings.

Specifically, you can establish an automation rule that triggers upon issue creation. This rule can then perform several actions, including adding a comment mentioning a user, sending an email notification, or integrating with platforms like Slack or Microsoft Teams. Alternatively, you can configure the automation to automatically add specific users as watchers to the issue, ensuring they receive immediate updates. Finally, if the appropriate team member is known beforehand, automatically assigning the ticket to them will trigger a notification.

It’s important to note that using usernames or HTML tags within the description field will not initiate notifications. Jira’s parsing of mentions differs from its handling in comments. Therefore, leveraging automation rules to add comments like “Hi [~accountid:abc12” is the most reliable strategy for notifying team members about new ticket creations.

In conclusion, automating ticket notifications through Project Settings and well-defined automation rules provides a more dependable and efficient solution compared to relying on mentions within the description field. This approach ensures your team receives timely updates and streamlines the intake process.

Source: https://community.atlassian.com/forums/Jira-questions/Using-Direct-HTML-as-an-intake-template-for-my-team-need-help/qaq-p/3057805

Are you experiencing confusion due to multiple teams with the same name within your Jira Cloud environment? It’s a common issue where teams with distinct IDs and members are created, often leading to duplicated efforts and increased complexity. This article outlines a practical solution to address this challenge and maintain a streamlined team structure.

The ability to create teams with identical names, despite differing IDs and members, can cause significant operational difficulties. Many users independently establish teams, particularly for specific projects, further compounding the problem. To mitigate this, administrators can implement several key strategies.

Firstly, establish clear naming conventions for all teams. This proactive approach significantly reduces the chance of duplicate names being used. Secondly, adjust user permissions within Jira settings to restrict team creation to authorized administrators only. Specifically, navigate to Jira settings > Issues, access Permission Schemes, and modify permissions to limit project and board creation to administrator roles. Thirdly, educate your team members on the established process for requesting new teams, reinforcing the requirement for administrator approval. Finally, regularly monitor team setups, identify and merge duplicates, and consistently enforce naming conventions.

By implementing these measures – establishing naming standards, controlling permissions, educating users, and actively monitoring team configurations – you can effectively manage team creation in Jira Cloud, minimizing confusion and fostering a more organized and efficient workflow.

Source: https://community.atlassian.com/forums/Jira-questions/How-to-prevent-teams-with-the-same-name-from-being-created/qaq-p/2606497

Introduction

JIRA email notifications have recently experienced inconsistencies for some users, presenting a challenge for efficient workflow management. This article addresses a reported issue where certain users receive detailed JIRA ticket notifications, while others only receive a basic mention alert. We’ll explore the potential causes and provide a solution to ensure consistent notification delivery.

Main Content

The variation in JIRA notification formats stems from several configurable features. Standard JIRA notifications, known as Jira (internal) notifications, are configured by Jira Administrators and cannot be customized by end-users. These notifications are triggered by events and sent to specific users based on a defined Notification Scheme, which can vary across projects. For team-managed projects, the project administrator controls these schemes.

However, JIRA Service Management (JSM) projects introduce a distinction. Customer notifications, sent to clients rather than agents, *are* configurable by the Project Administrator. This allows for tailored content based on user roles – Agents (Service Desk Teams) versus Customers. Furthermore, Automation Rules can also generate emails, adding another layer of potential configuration.

Conclusion

To resolve this discrepancy, it’s crucial to identify whether the affected user is receiving standard JIRA notifications or JSM customer notifications. Confirming the project type and verifying the notification scheme settings, managed by the Project Administrator, will pinpoint the source of the difference. Addressing these settings will ensure all users receive the complete JIRA ticket information they require.

Source: https://community.atlassian.com/forums/Jira-questions/JIRA-email-notification-format-template-has-changed-for-some/qaq-p/2894196

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