Default issue type per preset in release Jan 30 2022


The new release has few new features and mostly bugfixes.

New features

Default issue type for preset

Before it was a tedious process to assign presets to tickets as the tickets are added to the list of stories to refine. Now certain presets can be automatically assigned to Jira issues at the moment of adding them to the list. This is done by assigning an issue type per preset from the room settings page.

After the default issue type is assigned to the preset, when adding a new story to the list this preset is automatically assigned to the newly added stories of this type. Existing stories are left intact.

The presets can be certainly manually unassigned, or another preset assigned to a ticket with an already assigned preset.

Note: Please make sure to have selected a preset first, otherwise the new setting won’t appear.

If all is ok with the assignment of the issue type per preset, adding new story will automatically assign the presets:

New T-Shirt card images

We have now new images for the T-Shirt cards that bring more joy! Now except by the T-Shirt size you can make fun with the size of the animal wearing the T-Shirt on the card. There will be more card sets soon, so stay tuned!

New cards on the block!

Bugs fixed

Jira estimate field was not always used when specified

Jira estimate field now always overrides default board settings if present. Before in some cases the board’s default estimation took precedence over the specifically assigned Jira estimate field.

Note: when voting in a board room, by default the board settings for estimation are used and you don’t need to do any custom configuration. Only when using time as estimation you need to map points to time in the room settings so that the cards with points and the free scale tool can work.

Error notification now popping when estimation has failed

Before if estimation failed, the game silently continued. Now an error is popped up in the top-middle side of the screen. The error describes in more detail why the estimation has failed. Usually this is due to missing field in the edit screen or permission issue or a general field configuration problem. Additionally, in the browser log there are more verbose messages when performing the estimation, prefixed with ‘ESTIMATION: ‘ which can be used for additional diagnostics. More on why the estimation can fail and how to troubleshoot you can read here.

Warning hints on stories that may fail estimation

Some stories may not be properly estimated in the given room. This is because they might be part of a different board, a different project and may not match the estimation configuration set up into the current room. In this case there is a small yellow warning sign that indicates more details on the problem.

Warning on tickets that may fail estimation

Happy voting!

All those nice features (and fixed bugs) have been completed thanks to our users – they have requested and we have implemented them. Please help Scrumpy Planning Poker become even more convenient for you by submitting a feature request/bug to our Feature Requests page or up-vote an existing feature that you find useful. Thank you!