How to change new sprints automated naming convention?

[Script Runner]

After some changes in project management processes, we started an agile way of work in a few-years long project. In a scrum-board, we created a sprint called "projectname sprint 1".

After two weeks, we finished the sprint and started a new one, which should be automatically be called "projectname sprint 2", but in fact the new sprint was called "projectname April". After changing its name to "projectname sprint 2", same situation happened after end of this sprint, new one was called "projectname May" etc.

Currently all new sprints have next month in their name which is completely useless. Additionally it appears, that some time ago, the same team had some experiments with jira, and for some test purpose, there was this monthly convention for a short time and some old tasks appear in current sprints.

How to get rid of this annoying automation of interating an old sprint name and go to a new one?

[Nic Brough -Adaptavist-]

This is not how Jira Software works.  The pre-population of the sprint name is being done by something your admins have set up.  You should ask them what they have configured and get them to change it to something more useful to you.

[Script Runner]

But I am an admin. Where can I change it?

[Nic Brough -Adaptavist-]

I don't know, it depends on how you have done it.