Scrum teams need a backlog they can order quickly, sprints with clear dates and a board for the current sprint. Both Jira and Starlex cover this; Starlex removes the friction around it.
One backlog, drag to plan
The Starlex backlog lists open sprints above the backlog. Drag issues into a sprint, reorder by priority and start the sprint when it is ready. Issues waiting for triage appear in the backlog too, so nothing hides in a separate queue.
Story points when you want them
Points are off unless a project turns them on. Teams that estimate in hours or not at all are not forced through a field they never use.
Epics and sub-tasks
Any issue can have a parent, so epics group stories and stories hold sub-tasks. Moving an issue to another project keeps its old key as an alias, so links and bookmarks keep working.
Compared with Jira
Jira surrounds sprints with board configuration, estimation settings and report screens. Starlex keeps sprint planning where the work is, on the backlog and the board, and puts the dates on a Gantt chart and calendar the whole team can read.