How to stop the "New Sprint Name" carrying over

[Stephen Powell]

I have a cross team board, with approx seven teams.  Each team, within my board is creating their own SPRINT.  I want each team to be able to name their own sprint and be prompted to rename their new sprint, BECAUSE by default Jira names the NEW sprint automatically, and just adds a one to the week numbers, it copies over the latest new sprint that was calculated.

I want the initiator to be prompted to name their new sprint every time they make a new sprint.

[Nic Brough -Adaptavist-]

You can't do this. 

Atlassian have seen a few requests for "force people to enter a sprint name", and have closed them with "most people don't want to have to enter the sprint name every time, so we default them one they can edit later (and most people don't edit them)". 

I think there's actually a different problem here.  A board's primary purpose is to track a team's work (and when it's a scrum board, sprints are created by a team, in a board)

They are not intended to be "cross team".  The tools and functions in boards are built for "a team uses a board".

So, with that in mind, I'd suggest you can work around your need by changing the way you use the boards a little.  Essentially, create a board for each team, and have them create their sprints in their board.  Retain your cross-team board, but do not create sprints in it (or not ones that people will work on directly anyway).  It will show the sprints from the teams, and enable most of the reporting.

[Stephen Powell]

It's very kind of you to offer your "advice" @Nic Brough -Adaptavist- but just in the same way, I'd suggest you keep your opinion about "how i and my team should work" to yourself. 

You could have.... and I would suggest, that you SHOULD have just stopped at the end of the first paragraph.

But thanks for taking the time anyway.

[Nic Brough -Adaptavist-]

Ok, I think I phrased that badly.  Sorry.

I was not opining about how you should work.  I was offering a suggestion about how you might work better with the tools.  

They're not intended to support the way you're working, so there's a bit of clunkiness where you're working around that. 

With with some minor changes to how you're using the tool (not actually the way you're working), you could make much better use of it.