You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We started using the timeline view, which is a great feature!
But I do not see any option to sort the issues by start date, priority or assignee?
I could work around by using filters, but this is just time consuming and never gives the full overview.
Hello @Jonas Zumkehr,
Thank you for reaching out to the Atlassian Community!
On the Timeline, the tickets/issues are currently ordered by Issue Key/ID and it’s not possible to change that.
There are some filters available, but they won’t change the order of the tickets as well.
There are feature requests suggesting improvements for that:
Please, click on vote and also watch both tickets to receive updates from our product managers.
TLDR; The item order in the timeline is actually determined by the order the items are listed in on the "List" view (which, initially, is equal to the key order)
A quick update to this. On my Jira instance (We are using the "Business project" template and I think Jira Cloud), the order in the timeline is actually determined by the order that the items appear in the "List" tab. If I click and drag the items in the "List" tab the change is reflected in the timeline tab. NOTE, this doesn't work if you simply "sort" the list tab using the built-in sort you can access by clicking the submenu that appears in each column... it ONLY works if you physically move them yourself.
Its not a graceful solution, but it works for now.
Also, if you create items by "clicking" on the line between the items in the timeline, the item will appear (and stay) at that location, even if the item's key isn't sequentially between the items.
I find that sorting changes when filters are applied. It doesn't seem to be based on the parent, child IDs or dates. So in a filtered result set, a sub-task can end up at one location with it related sub-tasks some where else and other non-related sub-tasks between them. Its only with the visible connectors that one knows the split sub-tasks are related to each other.