Update story points to the issue summary using automation.

[Samuel Prathipaty]

Hi,

When user update the story points of an issue, that story points should be added to the Issue Summary and this we have done through the automation and it's working fine.

The problem is. after that automation triggers, if you update the story point field again, the results become something like "summary name <8.0> <5.0>". For the above example is to add a step before it creates the new summary to remove any references to previous story number points. So the number could be anything. Need to replace only the old story points with the updated one in the summary.

[Bill Sheboy · Accepted solution]

Hi @Samuel Prathipaty 

You could use substringBefore() first to truncate off any earlier sizing, and then add on the new story points string.

Please look here for more information on that function:

https://support.atlassian.com/jira-software-cloud/docs/smart-values-text-fields/#Smartvaluestextfields-substringBefore(Stringseparator)

I am curious: why are you adding the story points to the summary when it is already a separate field?  Thanks!

Best regards,

Bill

[Samuel Prathipaty]

Hi @Bill Sheboy 

This works fine. Thanks!

[Samuel Prathipaty]

Hi @Callum Carlile _Automation Consultants_  @Bill Sheboy 

Story points are not getting displayed when the swimlanes are based on stories.

Eg-

[Bill Sheboy]

Samuel, is that a Company-Managed (classic) or Team-Managed (next-gen) project?

When I use swimlane by stories, I am still able to see the story summary at the top of the lane for company-managed.

[Samuel Prathipaty]

Bill, it's a company-managed project. Am I missing something over here? Could you please share me your screenshot?

[Callum Carlile _Automation Consultants_]

@Samuel Prathipaty In your board settings under Card Layout, you can add certain field values to the tasks on the backlog and/or active sprint board, so if you do this for the Story Points field then they should be displayed on the board.

[Samuel Prathipaty]

@Callum Carlile _Automation Consultants_  Still not getting displayed, It's getting displayed for the sub-task cards under the stories when the swimlanes are expanded.

[Callum Carlile _Automation Consultants_]

@Samuel Prathipaty Is the Story Points field definitely on the screen associated with the parent tasks? I.e. when you click on one of the issues which isn't displaying the story points on the Sprint view, can you see the story points field within the issue itself?

[Bill Sheboy]

@Samuel Prathipaty this is what I see for a company-managed project when using swimlanes by story.  I have highlighted where I see the summary.

[Samuel Prathipaty]

@Callum Carlile _Automation Consultants_  Yes. story points are associated to the screen and it's showing up on the detailed view. It showing up on the cards. we need SP to be displayed for the parent issue (FJT-187)

[Samuel Prathipaty]

@Bill Sheboy  Ohh no. Yes, summary is dispayed. I said story points are not getting displayed, that's the reason we choose to update the issue story points to the summary using automation.

[Bill Sheboy]

Thanks, Samuel.  I understood that...I thought you meant summaries were not displaying for *your* swimlanes so I wanted to confirm.

[Callum Carlile _Automation Consultants_]

Hi @Samuel Prathipaty , This won't be possible with your current setup, as like you say, you will always be adding the number onto the end of the summary (which may contain at least one reference to story points)... There is no way of adding a dynamic field within the Summary which updates as the other field updates.

You could set something up which copies the Summary into another custom field upon creation, and then each time the Story Points are updated you can set the summary to {{issue.Cloned Summary Field}} <{{issue.Story Points}}. This however is quite clunky, and you could very quickly run into issues whenever the Summary is manually changed.

My question is, why do you need the number in the Summary? If it's to see the story points on boards and backlogs, then you could add this field to the issue cards so that they are displayed in addition to the Summary/Assignee etc.