How to embed information in a sprint name (like VIN)?

[Nate Mark]

I was given this task by the CEO. Come up with a naming convention for our sprints that embed more information in the name, like the VIN of a car. I think he's asking to see some info about what types of things were worked on (which modules, etc.). Any bright ideas?

We currently simply number our sprints (Sprint 1, Sprint 2, etc.). I'm afraid of losing the value that comes with ordinal sprint numbers. Has anyone successfully done something like this?

[Trudy Claspill]

Hello @Nate Mark 

Welcome to the Atlassian community!

How is the CEO getting information about the sprints?

Depending on how they get their information, maybe you could enter that information into the Sprint Goals field instead?

Or you could use Components or Labels (or another custom field) in the issues to identify the modules impacted by the work.