Problem:
We have Tickets that span multiple Sprints.
However, (in our Custom Filters) when we display the "Sprint" Column it lists every sprint a Ticket may have ever belonged to - we could easily have 10 or more.
This expands the Row height so much.  It is jarring and makes the report unwieldy.

Suggestion:
If we had a "Last Sprint" Column, we could view the Last-Sprint a Ticket was in.
This would be based on the Sprint's End-Date - NOT when it was assigned, created, or closed.
In the event no End-Date is supplied, then fallback to Create-Date.
When sorting to identify the Last Sprint a Ticket was in:
    Do not use: ISNULL(Sprint.EndDate, Sprint.CreateDate) DESC
    Instead use: Sprint.EndDate DESC, Sprint.CreateDate DESC
    (Where "Sprint." is the Table-Alias used for the Sprint Table.)

Example:
I am not familiar with the Jira Schema, but the pseudocode would look something like this:

--Ideally the "LastSprint" will be one of the following (in order of prescedence):
--  1.) The Unopened Sprint the Ticket is Preassigned to work (in the Future).
--  2.) The   Opened Sprint the Ticket is Currently Assigned to.
--  3.) The   Closed Sprint the Ticket was either Closed in or Last-Active in.
--  4.) Null (Never Assigned to a Sprint).
--I say "Ideally" because if you mix Sprints with EndDates and those without, then results are hit-or-miss.
SELECT T.*, LS.SprintName[LastSprint]
  FROM Ticket as T
  OUTER APPLY--Outer-Apply in case the Ticket has not been assigned to a Sprint yet.
  (
    SELECT S.*
      FROM Ticket_Sprint as TS--Cross-Reference of Tickets to Sprints.
      JOIN Sprint as S
        ON S.SprintID = TS.SprintID
     WHERE TS.TicketID = T.TicketID--Outer-Apply Filter.
     --AND S.EndDate IS NOT NULL--Optional: Only Compute LastSprint for Sprints with EndDate's.
     ORDER BY S.EndDate DESC, S.Created DESC--Fallback to Created when EndDate is Null.
  ) AS LS--Last Sprint: Not the last-assigned, but the most-recent/most-future Sprint it was assigned to.

Justification:
We are well aware of an expensive add-on may add similar behavior, but this is not (and never will be) an option where I work.
This Field is something that should come standard (out of the box) - especially for Reporting.
Accessing a field like this in a Jira Filter Online or within an Excel File would allow Team Members and Management to see where things stand now and where they are going
    - not everywhere they've ever been.

Screenshot:
Below is an example of how the Sprint Column currently appears in our Reports.
Instead of 1-Line per Row, it has been expanded to 4-Lines (for 13 Sprints).
Viewing this in Excel is just as bad.

Even the order of the Sprints are inconsistent and appear in a random order for each Cell.
Because of this, we cannot rely on the First or Last Sprint (that appears in the Cell) as our "Last Sprint".

Caveats:
I expect others to point out how we're not Jira'ing or Agil'ing correctly and how if we did, then this wouldn't be an issue.
I get it.  I do.  However, this is not an option for us.
This is how those above my paygrade assign "Sprints".

I work in Maintenance, so we work on things when we can (that is, between putting out all the fires that spring up) and the best laid plans that are thrown into "sprints" will often defer to the next month/window.
I use quotes because these are technically not "sprints" but more like a bucket of work we have waiting for us to complete each month - should we find the time to do it.

As you can see from my little screenshot above, I defer... a lot.
I'm sure management likes to see this - to see how many times we scheduled a Task, only to not complete it in the given window - then use those metrics to either justify more personnel... or arrange a personal check-in with the assignee.

Thank you for reading.