Blog

Are you struggling to monitor issues that have been transferred between projects? This common challenge can complicate workflow management and reporting. Fortunately, there are effective solutions available.

Many teams face the need to understand the history of issues as they shift between projects. While Jira doesn’t always offer built-in tracking of these movements, a robust approach can provide valuable insights. Our team developed the Issue History for Jira app to address this precisely.

This application allows you to track changes to the project field of each issue in a dedicated column. By utilizing Issue History for Jira, you can easily determine how many tickets were moved from one Jira project to another, gaining a clear audit trail of issue assignments.

Ultimately, understanding issue movement is crucial for efficient project management. Issue History for Jira offers a straightforward solution for tracking these transitions and providing valuable data for your team.

Source: https://community.atlassian.com/forums/Jira-questions/History-of-moved-issues-from-one-project-to-another-project/qaq-p/2606559

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 does offer a search function, it doesn’t effectively address the primary need for rapid navigation between epics for Product Owners. This absence creates a noticeable obstacle in managing and reviewing project epics.

A change request, JSWCLOUD-21463, exists to address this issue. Users are encouraged to cast a vote on this request to advocate for the return of the search bar functionality within the Jira Cloud epic panel. This proactive step will contribute to the development of a more streamlined workflow.

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

Many users encounter a limitation when viewing the table of child issues associated with a Jira work item. Currently, a horizontal scroll bar is present at the bottom of the table, allowing access to additional columns. However, the absence of a scroll bar at the top creates an inconvenient experience, requiring users to scroll repeatedly up and down to navigate the table’s content.

To address this usability concern, we can implement a horizontal scroll bar at the top of the table. This addition would provide a more intuitive and efficient method for viewing all child issues, eliminating the need for constant vertical scrolling.

This enhancement would significantly improve the user experience and streamline the workflow for those managing Jira work items with numerous child issues.

Source: https://community.atlassian.com/forums/Jira-questions/Can-there-be-a-scroll-bar-added-to-the-top-of-the-table-that/qaq-p/3057842

Many users are encountering difficulties when implementing approval workflows within our system. A recent question highlighted a common problem: the instructions for setting up approvals, specifically involving workflow editing and custom fields, are not appearing as expected.

The user reported attempting to follow the provided guidance, including the steps to modify the workflow via the pencil icon and utilizing custom fields associated with issues. Despite verifying their administrative role and confirming that this is a company-managed project, neither of these functionalities were accessible.

The solution involves a recent system update that streamlined the approval process. The pencil icon and custom field options have been consolidated into a single, more intuitive interface. This change was implemented to simplify workflow management and reduce potential user confusion.

We appreciate the user’s feedback and apologize for any inconvenience this may have caused. We are continuously working to improve our documentation and user experience.

Source: https://community.atlassian.com/forums/Jira-questions/Approval-setup-not-appearing/qaq-p/2606575

Introduction

This article addresses a user experience issue observed within Company-managed software projects where the “Approvals” field persistently appears at the top of screens. This can be disruptive and confusing, particularly when the feature is not relevant to the project type. We will explore the potential causes and provide a solution for removing this field.

The Issue

Users have reported encountering the “Approvals” field on top of screens within Company-managed software projects, even when the feature is inactive and not utilized. This issue was initially noted several weeks ago and continues to appear across all new issues created. The field’s presence is considered unnecessary and detrimental to the project workflow.

Resolution

The “Approvals” field is typically managed through the Screen Scheme and Issue Type Screen Scheme within Jira. A Jira Administrator can access these settings to remove the field from the screens associated with the specific issue types used in the project. This configuration change will prevent the field from appearing on subsequent issue screens.

Conclusion

By adjusting the Screen Scheme and Issue Type Screen Scheme, Jira Administrators can effectively eliminate the persistent “Approvals” field from Company-managed software projects, improving the user experience and streamlining the workflow.

Source: https://community.atlassian.com/forums/Jira-questions/Company-managed-software-project-with-Approvals-field-on-top/qaq-p/2894371

Introduction

We’ve received feedback regarding a recent change in Jira Service Management behavior concerning ticket status updates. Specifically, users have reported that the system now defaults to adding an internal note instead of replying to the customer when a ticket’s status is modified. This article provides a straightforward solution to address this issue.

Main Content

The default comment behavior during ticket status transitions can be adjusted. To change the system’s default setting, please refer to the following article: https://community.atlassian.com/forums/Jira-Service-Management-articles/New-Jira-Service-Management-settings-toggle-Set-default/ba-p/3056534. This resource details how to modify the settings for Comments in Transition Screens within Jira Service Management projects.

Conclusion

By following the steps outlined in the linked article, you can successfully change the default comment behavior and ensure that your team consistently replies to customers when updating ticket statuses.

Source: https://community.atlassian.com/forums/Jira-questions/Default-Field-When-Changing-Ticket-Status-Internal-Comment/qaq-p/3057871

Hello, I understand you’re seeking guidance on generating a visual report detailing issues categorized by timeframe, similar to the example provided.

To address this request, you can access the dashboard’s reporting functionality. Navigate to the reporting section and select the option to create a custom report. Within the report builder, choose the issue field and set the grouping criteria to ‘period’ or ‘age’ as desired. This will automatically generate a graph displaying issues segmented by the selected timeframe. Ensure you save your report settings for future use.

We hope this clarifies how to create the desired issue report. Please don’t hesitate to contact support if you require further assistance.

Source: https://community.atlassian.com/forums/Jira-questions/help-with-dashboard-please-report-issues-per-period-or-age/qaq-p/2606583

This article addresses a reported issue regarding the ‘select filter’ dropdown on the board configuration screen, where users are only seeing the initial filter option. We’ll explore potential causes and offer a resolution for this problem.

Several users, including project administrators, have encountered this limitation. The issue manifests when the dropdown menu only displays the first filter from a list of available options. One administrator, utilizing Microsoft Edge, confirmed that clearing cache, cookies, and attempting the issue on a different machine did not resolve the problem. A colleague with identical administrative privileges also experienced the same symptom. Despite both users possessing project and board admin rights, the discrepancy in the dropdown display persisted.

The root cause was identified as a conflict arising from the organization’s Single Sign-On (SSO) policy. This policy redirects users to a standard version of Edge, preventing the use of incognito mode. Therefore, attempting to access the board configuration screen within Edge’s incognito mode was unsuccessful.

To resolve this, users must adhere to the organization’s policy and utilize the standard Edge browser. Further troubleshooting steps, such as alternative browsers, are not recommended due to the SSO configuration.

Source: https://community.atlassian.com/forums/Jira-questions/Board-config-screen-select-filter-dropdown-only-showing-first/qaq-p/2894418