-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
When customers are faced with a multitude of fix versions in Jira, the process of setting the versions can quickly become cumbersome and time-consuming. Without a streamlined method to accurately sort through these versions, users are left with the tedious task of manually scrolling through a lengthy dropdown list in search of the correct version. The request at hand is to implement a solution that simplifies the selection process for customers, whether through the introduction of sorting capabilities or any other enhancement that enhances usability and efficiency.
Reordering becomes challenging for projects with many releases (fixVersions). Moving the latest release to the bottom after multiple extensions is not straightforward. Sorting and reordering seem impossible in this scenario, making it a less-than-ideal solution
- mentioned in
-
Page Failed to load
[JRACLOUD-84361] Sort values of 'Fix Version/s' field
| Support reference count | Original: 5 | New: 6 |
| Support reference count | Original: 4 | New: 5 |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| Support reference count | Original: 1 | New: 2 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 947230 ] |
| Support reference count | New: 1 |
| Description |
Original:
When customers are faced with a multitude of fix versions in Jira, the process of setting the versions can quickly become cumbersome and time-consuming. Without a streamlined method to accurately sort through these versions, users are left with the tedious task of manually scrolling through a lengthy dropdown list in search of the correct version. The request at hand is to implement a solution that simplifies the selection process for customers, whether through the introduction of sorting capabilities or any other enhancement that enhances usability and efficiency.
Reordering becomes challenging for projects with over 60 releases (fixVersions). Moving the latest release to the bottom after multiple extensions is not straightforward. Sorting and reordering seem impossible in this scenario, making it a less-than-ideal solution |
New:
When customers are faced with a multitude of fix versions in Jira, the process of setting the versions can quickly become cumbersome and time-consuming. Without a streamlined method to accurately sort through these versions, users are left with the tedious task of manually scrolling through a lengthy dropdown list in search of the correct version. The request at hand is to implement a solution that simplifies the selection process for customers, whether through the introduction of sorting capabilities or any other enhancement that enhances usability and efficiency.
Reordering becomes challenging for projects with many releases (fixVersions). Moving the latest release to the bottom after multiple extensions is not straightforward. Sorting and reordering seem impossible in this scenario, making it a less-than-ideal solution |
| Description | Original: When customers are faced with a multitude of fix versions in Jira, the process of setting the versions can quickly become cumbersome and time-consuming. Without a streamlined method to accurately sort through these versions, users are left with the tedious task of manually scrolling through a lengthy dropdown list in search of the correct version. The request at hand is to implement a solution that simplifies the selection process for customers, whether through the introduction of sorting capabilities or any other enhancement that enhances usability and efficiency. |
New:
When customers are faced with a multitude of fix versions in Jira, the process of setting the versions can quickly become cumbersome and time-consuming. Without a streamlined method to accurately sort through these versions, users are left with the tedious task of manually scrolling through a lengthy dropdown list in search of the correct version. The request at hand is to implement a solution that simplifies the selection process for customers, whether through the introduction of sorting capabilities or any other enhancement that enhances usability and efficiency.
Reordering becomes challenging for projects with over 60 releases (fixVersions). Moving the latest release to the bottom after multiple extensions is not straightforward. Sorting and reordering seem impossible in this scenario, making it a less-than-ideal solution |