Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What is the length of the Sprint field?

Mark Dorros January 11, 2023

What is the length of the Sprint field? It's shown as type "Jira Sprint Field". Or, how get I get it? Is there a DB query?

Background: We have an integration with Salesforce with this field sync'd from Jira to SF and we need to know how large to make the field in SF - apparently it can be over 255 characters. (For issues that have been carried from sprint to sprint to sprint :-(  

1 answer

0 votes
Tinker Fadoua
Community Champion
January 11, 2023

@Mark Dorros 

Did you check in the admin console under General Configuration? I will check our instance tomorrow then get back to you. Mine is cloud which is useless in this case.

Best,

Fadoua

Mark Dorros January 12, 2023

@Tinker Fadoua I didn't see anything under Admin | System | General Configuration, nor the other screens under System

Regards,
Mark

Tinker Fadoua
Community Champion
January 12, 2023

@Mark Dorros I checked as well it is not there .

Found that the field can handle 30 characters, However it is safe to increase the size through DB.

https://jira.atlassian.com/browse/JSWSERVER-12499

I hope this helps.

That's all I was able to find

Best,

Fadoua

Mark Dorros January 18, 2023

Hi Fadoua - That's the name of the sprint in the Agile board which is different than the custom field called "Sprint" that appears on individual issues, and contains every sprint that issue has ever been a part of.

Regards,
Mark

Mark Dorros February 6, 2023

Hi Fadoua - Do you have any update on how long this field is?

Tinker Fadoua
Community Champion
February 6, 2023

Hi @Mark Dorros 

Oh I see let me check please

Mark Dorros February 17, 2023

Hi Fadoua - I received this response from Atlassian Support:


Just to recap my understanding of the question, you are looking for the maximum length of the sprint name field within Jira. Not the name of an individual sprint, but text returned in the field itself (which could contain multiple sprints if issues are rolled from sprint to sprint).

I do not believe there is actually a fixed length to this field. It notes in the Jira UI that the field displays data in a non-standard way. So the value you see in the UI is not actually stored within the database as that string anywhere. The way this works is that:

  • Within the customfieldvalue table, an ID value is stored within the stringvalue column for the issue. There could be multiple rows stored in this table for a single issue for this sprint field.
  • This value connects to the ID column within the AO_60DB71_SPRINT table which identifies the sprint.
  • Upon load of the UI or calling of this field, these values will be compiled and displayed so that the name stored in the AO_60DB71_SPRINT for each row for the sprint field for that issue within the customfieldvalue is displayed a comma separated list.

So there is no limit to the size of this field theoretically. It should just display as many values as are stored within the customfieldvalue table for that issue. There is a limit to the size of a sprint name at 30 characters as noted by JSWSERVER-16256. But that doesn't really come into play here since the UI is compiled dynamically you could have 100s or 1000s potentially of 30 character sprint names on a single ticket and Jira would not limit that. The only time Jira would hit a limit here is if you had an integer larger than 255 characters for the count of sprints in the system. So that would be ~10^255 sprints in the system I believe.

So if you were looking to size a field in Saleforce, you could do one of two things:

  • Store this value into a large text field in Salesforce which doesn't have a character limit.
  • Determine the max number of sprints you would expect an issue to potentially rollover, multiple that by 30 and then add a buffer just incase and set the Salesforce value to be that large.

Thanks for your help on this,
Mark

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.22.2
TAGS
AUG Leaders

Atlassian Community Events