-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
1
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
Customers utilizing Gadgets which rely on multiple field ordering cannot be re-sorted through the UI to match the original filter. (ex: PROJECT = TEST ORDER BY Priority, CreatedDate ASC). It is also not possible to reset the gadget back to its original filter (see: JRA-46043)
Suggested Solution
Include an option which prevents certain users the ability to sort Gadgets
Workaround
Dashboard Owner can delete and recreate the Gadget so that it adheres to the sort in the Filter
- relates to
-
JRACLOUD-63670 Prevent Gadgets from Being Sorted
- Closed
-
JRASERVER-46043 Reset Filter Results gadget so it shows the results as ordered in the configured filter
- Gathering Interest
[JRASERVER-63670] Prevent Gadgets from Being Sorted
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3054615 ] | New: JAC Suggestion Workflow 3 [ 3690541 ] |
Component/s | New: Dashboard & Gadgets [ 43416 ] |
Component/s | Original: Dashboards & Reports - Gadgets [ 12923 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2619252 ] | New: JAC Suggestion Workflow [ 3054615 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2592584 ] | New: Confluence Workflow - Public Facing v4 [ 2619252 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2359250 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2592584 ] |
Support reference count | New: 1 |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2126696 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2359250 ] |
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.
To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.
Regards,
Jira Server and Data Center Product Management