+1

Please, increase the sprint name length

Hmm ... this is an unfortunate limitation. We had named a sprint based on the Subversion development branch name. For our own convenience, we usually create a single branch that applies two of our main closely-related products. But they have different version numbers. So the format is "product1 version-series-1 - product2 version-series-2". In fact, the branch in question has the following 27-character format:

• aaaaa 1.5.x - bbbbbbb 1.9.x

We have since decided to split the sprint into two sprints. Just adding " (1)" or " - 1" put us over the 30-character limit, and taking away other characters is not very convenient, especially where we would like to match the branch name.

We will abbreviate something, I suppose, but 30 characters is quite low. I think that we should be able to configure a higher value and put up with the sprint name display not being what we want in all cases. When configuring a higher value, Jira could simply warn that more than 30 characters is not recommended. Configurer beware.

It's ok, lets try your way, thank you for your time!

benja1 - thanks for the additional information. The additional field will allow for a separation of concerns and more concise menu items and search results.
Increasing the character count, while adding some flexibility, is likely to negatively impact the user interface in many cases.

Kind regards,
Martin
JIRA Software

Yes, I have long sprint names, useful to find them quiclky, I am including the project key, to avoid creating issues in a wrong project (I have a "report" sprint for 3 projects), I am including a "sprint version" and the main goal between parentheses.

Maybe I am using too many info, I dont know if an extra field will be useful, why not doing both? increase characters and add an extra field?

I think increase the field characters sounds easier.

Regards!

benja1 - the use case provided for increasing the character count is to display a sprint goal. We will be supporting this with an additional optional field. Does your use case differ to this?

Kind regards,
Martin
JIRA Software

I already found too many request to make the Sprint name longer than 30 chars, they are all closed and redirecting to the JSW-7308, I think this is wrong, the JSW-7308 is to add a new field, we do NOT want that, all what we want is increase the sprint name characters.

Many thanks for reporting this issue. We are resolving it as a duplicate of the linked issue GHS-5396, as the main request here is to support the definition of a sprint goal.

Please watch the linked issue for updates.

Regards,
JIRA Agile Team

where is this item on the dev queue at atlassian? after using jira for a year, this is one of the issues that consistently drives me crazy. I agree that it would be best to keep the name itself short, but having a description that appeared under it in grey would provide a lot of communication value to the team each sprint.