DevOps Automation: More ways to work with sprints: set sprint to sprint ID, sprint name, "triggering sprint"; smart values for active sprint or next sprint, trigger on sprint scope change, new actions/triggers for sprints

As a Jira Project administrator, I would like the option to schedule my sprints to start and end, by the dates and times I have selected and to have options automatically implemented, so less manual work is required and consistency is maintained from sprint to sprint.

I would like to have options when it comes to starting/completing sprints:

1. Who can start/complete sprints (and options to add back-ups) - more than the permissions allow
2. Provide a method for a naming convention (choosing fields to use and in an order we can choose)
3. Select start date and time
4. Select end date and time
5. Choose whether I want this to be auto-scheduled, and for how long
6. Choose what to do with items that are not "done"
   1. Move items to the backlog
      1. if the last active date was more than X days before the sprint was completed
      2. if the story is less than x % complete
      3. whatever other condition the teams choose to implement
   2. Move items to the next sprint
      1. if the last active date was less than X days before the sprint was completed
      2. if the story is more than x % complete
      3. Priority is X
      4. the story points are X
      5. whatever other condition the teams choose to implement
7. Options to send out a notification of the sprint results (completed/moved to backlog/moved to next sprint)
8. Option to create a report from the results - not the Jira reports, but of what we want to see, from the available metadata