Stories added after commit not tagged with asterisk

Question

I consume data from Jira Sprint Reports to use in Confluence pages.  My understanding is that stories that are committed at sprint start have a "plain" key #, like KEY001.  Stories added after commit have a "*" suffixed to indicate this is a change, like KEY002 *.

This has been consistent across multiple teams using Jira, but lately I have seen examples where a team has added stories, but some do not have the "*" suffix.  None of the Jira users I've spoken to could explain why this would have happened.

Can someone cite examples of how this would happen, and if this is correct Jira operation or an issue with our use/setup of Jira?

Bill Sheboy · Answer

Thanks for clarifying, as it appears you are instead using this addon: https://marketplace.atlassian.com/apps/27447/table-filter-and-charts-for-confluence?hosting=cloud&tab=overview

And...if you are directly copying and pasting from the sprint report then the source of the missing asterisk indicator may be before that point...

There is an open defect that the scope change only appears once on the Sprint Report and burn charts.  That is, if you added/removed an issue from a sprint once and then did it again for another sprint later, the later one(s) will not show.  Is this the case for your Jira issue?

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

Scott Gillespie_ibixpx · Answer

Hi Bill...the Table Transformer macro from Stiltsoft is used in this case to compile the data within Confluence.  It doesn't influence the Jira data because that is copy/pasted from the Jira Sprint Report into a Confluence table before the macro does anything.

All I can tell is that something has changed with our Jira setup such that some added stories don't get the "*" suffix. So far, no one I've asked in my company is aware of any changes to Jira that would cause this.

Are there any Jira settings or situations to explain?

Bill Sheboy · Answer

Thanks for that information.  From your notes, it appears you are using this marketplace addon: https://marketplace.atlassian.com/apps/1219300/sql-powered-table-transformer?hosting=server&tab=overview

I have not used that one, and could not determine from their documentation how the scope change indicator is added for the issue keys.  Please consider contacting their support team (from the marketplace page links) to ask their advice.