In-place story estimation in release Aug 02 2020

New Features

In-place story estimation

Now it is possible to estimate the stories inside the list of stories for the planning sessions, e.g. they are not removed from the list after estimation. Instead, they remain there and estimating them again is on a one click distance. The option for enabling the new feature is in the core settings page.

After the option is enabled, the estimated tickets won’t be removed after the estimation and instead will show the estimates inline.

The estimate is shown on the left of the ticket and if the ticket is not yet estimated in this session, an empty hourglass icon is shown.

Below the list of estimated stories is a summary of the estimates. If only story points are used, only story points summary is displayed. Mixed story points/time is also supported and when time estimates are used there is the possibility to choose between the time stretch – hours, days, weeks, months.

An example use case is to do estimating until the capacity of 2 weeks is reached or the story points equal to the current sprint capacity is reached.

Numeric labels extension

The “Numeric labels on cards” option previously only showed labels on the cards which did not make any sense for regular and Fibonacci cards. Now this setting has an extra meaning – to not map the result to a card. This way, the accurate average can be selected. For example 3 and 5 the average is 4 and this is what’s offered as an average. It can be overridden to any arbitrary value such as 4.5 for example.

Below is an example what happens when “Numeric labels on cards” is selected and the result is not matched to a card:

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!

Comments in async voting in release Jul 26 2020

Introduction

The new release contains some small but nice usability features and enhancements that our customers have recently requested. They have been in the backlog for quite some time, but due to the refactoring they have been pushed back. Now when Scrumpy’s core has been refactored to sustain the load, the new features are being implemented one by one.

New Features

Comments in asynchronous voting

Before, asynchronous voting was just setting the vote in advance by the team members and leaving it as is. The scrum masters had difficulties understanding the reasoning behind the votes.

Now it is a bit easier to get the idea why someone voted with a given vote – there is also an additional comment. Everything starts by setting the comments for asynchronous voting to required. This can be done from the room settings, just bellow the asynchronous voting checkbox. Certainly the asynchronous voting has to be checked to be able to use the require comments option.

After the require comments option has been enabled, when setting a vote in advance a new dialog box pops up.

The comment is a free text that will be useful to the scrum master (moderator) who will accept the votes and convert to estimate in the ticket.

Board local search

Before some customers wondered why all tickets are accessible and not only the tickets that are available under the selected board. Having access to tickets from other boards and projects can be convenient, but sometimes it is too much information that can be limited.

Now the tickets that are displayed in the search box can be limited only to the current board. This setting is available in the Integrations -> Jira setting

After the option is enabled, searching by ticket number or by JQL will yield only tickets from the current board.

Hide the average vote

Sometimes it is not nice to show the average vote since the voters are convinced that the average vote is the right vote and this might not be always the accurate estimate. Instead, it would be better to first discuss the chart displayed and only then to show the average vote after the consensus has been selected.

The feature is available in the core settings

Once enabled, the summary box won’t show the average vote. Instead it will show an alert message that to be able to complete the voting, the average vote should be shown.

After the discussion about the results, the average vote can be shown and the voting can be completed.

Override free-scale voting

Before it was not possible to override free-scale voting both in story points and in time. Now there is a slider after the vote completes so that the scrum master can override it.

Fixed Bugs

User avatar and name sometimes not automatically set in Jira Cloud

Sometimes opening the room didn’t automatically set the participant’s name and avatar and this had to be manually entered which was kind of awkward. This was a regression caused recently and it has been fixed now.

Days/Weeks/Months always visible

For free-scale time-based voting the scale switch was fully visible. Now the days/weeks/months buttons are hidden in case the scale won’t be able to stretch to this level.

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!

Performance improvements in release Jul 19 2020

Introduction

It has been a while since we announced an official release. There have been multiple small updates and releases since then though. Scrumpy Poker was silently being substantially refactored in the background. New features have been frozen for some time for the sake of improving the stability and connectivity issues that we used to have.

Scrumpy grew significantly from just a few hundred users to tens of thousands recurring users from 1800+ companies actively using it. It has been a bumpy ride and quite a challenge to sustain our growth and still keep the product free of charge. Our user base spans from small software businesses to big enterprise and government organizations and many Fortune 500 companies. And it is not just about software – any task that can be estimated, any risk that can be assessed, any value that can be measured are the sweet spot of Scrumpy Poker. That’s why we achieved almost 20% MoM growth rate from companies trusting our solutions.

Welcome to the new Scrumpy Poker!

New Features

Asynchronous Voting

This feature request has collected quite some votes. It seems that even though voting is a collaborative process it still brings value to be able to estimate in advance and do either a smaller voting sessions with less participants or simply go over tickets and collect the votes that were added during the last few hours/days. That’s why the feature was renamed from Early Voting to Asynchronous Voting and has been extended as per the requirements that our users provided.

When the Asynchronous Voting is enabled, anyone can hop-in the room and add an estimate to the ticket from the context menu button at the right side of the ticket

After the stories are estimated, one option would be to just start voting with whoever is able to be online at the time of the session or just simply collect the results. The votes of the people who voted earlier are appearing in a separate section of the sessions screen.

And finally the most anticipated feature according to our feature requests – collecting the votes!

When pressing the donut button the regular summary box is popped up and the Scrum Master can adjust or just press the completion button to assign the story points or time to the ticket. This can be done without any voting session. The Scrum Master (a.k.a Moderator) can open the Planning Poker room and collect the asynchronous votes of all previously estimated stories.

Note: soon both real-time and asynchronous voting will be integrated inside the Jira Issue view. Stay tuned!

Volume control

You know this loud sound when the Moderator honks the horn to remind you to vote or just when voting has started. Sometimes it is too loud and intrusive. That’s why now by default the volume is set to 50% and there is volume control in the personal settings (yes, controlled individually by each user). You can still get the old style of sound if you pump up the volume to 100%. You can also make it very discrete, just enough to get a notification when on another browser page.

Import/export of room settings

When opening a new room on another project/board or just starting an ad-hoc room, the settings that you’re used to are gone. Instead the configuration starts from scratch including card presets and voting rules. This takes some time and can be annoying to adjust it again and again.

Now there is a new feature to export the room settings to a file and then import the settings to another room.

The downloaded file has a binary encrypted content so that any Slack webhooks or external API tokens are not visible.

The settings can be imported by dragging and dropping the binary file to the drop area or just clicking the drop area.

Reset room settings

When fiddling around settings something might go wrong and you could forget what was changed. There is a convenience shortcut now to reset the settings to their initial value.

The option is also convenient if you would like to wipe off all information in this room and make it completely empty right away. Scrumpy Poker would delete everything after one month of inactivity. With this shortcut this can be done immediately.

Clear search list

Before it was difficult to clear the list of tickets in Jira when the wrong query was used. Now there is a shortcut to clear the current search list so that the list can be started from scratch.

Room Description

A multi-line fixed-font description of the room is now available in the room settings. The description can serve for some additional instructions to the voters, mapping tables, or just a welcome message.

After the description is set, it appears below the stories/chat list as follows:

Bug Fixes

PWA Add To Home Screen was not available

Installing the PWA mobile application was temporarily not available. Now the PWA configuration has been fixed and the Add To Home Screen is available when shooting the QR code in the room.

Additional Channels

Service Desk/Support

We’ve added a service desk support system where you can file support tickets and watch for their implementation. The page is available at this location.

Status Page

Now you’ll be able to know for on-going or scheduled maintenance, incidents and health status of the system. The status page is available at this location.

SLA page

Now you’ll be able to monitor in real-time our up-time status. And this is not just the overall status but also our sub-system status. The system automatically smoke-tests the system for issues. The system can be found at this location.

Discussion forum

We’ll try to bring more life to our feature/support discussion forum. The forum is available at this location.

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!

Story extra info section in release May 19 2019

Introduction

The new release contains new features like an extra additional information section in the Jira collaboration view as well as some minor usability enhancements like the removal of the save confirm dialog and bug-fixing.

New Features

Additional Information

The major new feature this week is the section containing extra information for the selected issue. The extra info section contains information like the creator of the issue, the current assignee, when it was created and updated as well as some more information like priority, progress. etc.

Additional information section

The new section shows the information as read-only and cannot be edited.

Export session to CSV

There is import/export from CSV for the stories to be planned, but before this release there was no export to CSV from the session results. Now, there is a shortcut in the context menu of the refinement session that allows export to CSV of the planning session.

Export session to CSV

Collaboration view recognizes more styling

Now the collaboration view for Jira integration is able to display tables properly, as close to the Jira display as possible.

Showing fonts and tables

Usability Improvements

No edit confirmation

Before there was an annoying message box asking to confirm the change of story summary and description. Now updating the story is done silently and makes the user interface friendlier to the scrum master, especially when no Jira/GitHub or GitLab is used.

Bugfixing

Onine/offline message appears twice

Sometimes, when disconnected the offline message appeared twice. Same when disconnected for too long and reconnecting has failed (no internet, network or other reason) about the online message. Now the online/offline message is displayed only once.

UI glitch in CSV import

When importing CSV planned stories, there was an overlap to the copy-to-clipboard and close buttons of the CSV import dialog. Now this glitch is no longer viisble.

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!

Jira Cloud add-on configuration in release May 04 2019

Introduction

The new release contains only important new features like the Jira CLoud add-on configuration. No bugs have been reported and fixed.

New Features

A couple of new features have been implemented which also give the foundation to implement some of the most anticipated new functionalities in the upcoming weeks.

Support configuration to projects/boards in Jira

Now the Planning Poker link can be enabled/disabled per project and per user. Additionally the root Planning Poker link at the project’s root dashboard can be also enabled/disabled.

This feature is particularly useful for bigger organizations which do not have all teams and members participating in the voting sessions. When the Planning Poker is disabled for certain users globally, they don’t see the Planning Poker link at all. When the link is disabled for certain projects tat don’t have tickets for estimation, the Planning Poker link is not visible for any Jira Cloud user.

Note: Please upgrade Scrumpy Planning Poker to version 1.0.5-AC.

To enable or disable the Planning Poker permissions globally, go to the Global Permissions in the Jira settings and configure the Allow Planning Poker permission (e.g. which users/groups/roles are allowed to use planning poker globally). By default, Planning Poker is enabled for any logged in user.

Configure Global Permissions

To enable or disable the Planning Poker permissions per project, go to the Project Permissions in the particular Jira project settings and configure the Allow Planning Poker permission.

Configure Project Permissions

Foundation for the future add-on configuration pages

In addition to the permissions control which is introduced in this release, future versions of Scrumpy Planning Poker for Jira Cloud will be fully configurable. The add-on now shows a Configure button that shows a configuration page with options that will be extended in the upcoming releases. Please submit new features or up-vote existing configuration features in our Feature Requests page.

Configuration button in the add-on panel

When pressing on the Configure button, the Scrumpy Planning Poker configuration page is loaded.

Planning Poker configuration page

Include parent issue information

For the Jira integrations (Cloud, Server, API token integration), now the parent issue key and summary are shown just above the summary box for the issue in the details view.

Show parent issue information in details view

The parent issue is also shown in the list of planned stories.

Show parent issue in the planned stories list

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!

Initials as avaratrs in Release Apr 28 2019

Introduction

The new release is mostly a bugfix release due to the Easter holidays. There is one new feature released – initials instead of avatar when using anonymous users.

New Features

Only one new feature is implemented for this release

Initials as avatar

When using anonymous users (just a name) and no social login or Jira add-on use, now instead of the boring user icon the initials of the user are shown.

Initials as avatar

Bugfixing

This release includes bugfixes of some small but annoying bugs in the system.

Scrolling issue in the Jira add-on

Now it is possible to scroll with the mouse wheel in the settings dialog in Chrome. Before this was possible only by clicking on the scroll bar.

Selection of the Add All Stories menu.

Before it was difficult to select the add all stories with the mouse and possible with the keyboard or at the second attempt. Now it is always possible to select the Add All Stories when there is more than one story listed.

Kanban board timing estimation

Before there was an issue not allowing to estimate Kanban tickets with time. Now this bug is fixed and the Kanban board’s Original Time Estimate and Remaining Time are updated.

Note: To be able to estimate Jira tickets with time, please map the story points to hours in the Settings dialog and also enable numeric labels on cards so that the time estimate is printed on the cards.

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!

Facebook sign-in in release Apr 21 2019

Introduction

The new release is out and contains several new features as well as some bug fixes on issues reported by our customers.

New Features

Facebook sign-in

Now it is possible to sign in with your Facebook account. This is done from the main screen after you sign-out from the Settings page or create a new room. The Facebook application as well as all the rest sign-in integrations read only the public data – name and avatar which are displayed in the application.

Facebook sign-in now available

After sign in, inside the left pane the information which platform was used to sign in, or “Anonyous user” is displayed.

Information on the sign-in platform used

Preserving settings when signing in from another browser or device

Now when you sign in from one device with one of the social sign-ins, the settings you make are preserved and are loaded when you sign in from the same account on another device.

Add all stories

In Jira, GitHub and GitLab there is a new button on top of the stories list that allows you to add all stories that are in the drop-down list as long as there is more than one story there. For example, this way you can add with one click all un-estimated stories from the next sprint. It works well in combination with the bookmarked story queries.

Add all stories to refinement list

Settings optionally changeable by any user

Now there is an option in the settings page to allow anyone from the team to change the settings. When this option is set, the settings can be adjusted by any participant during the time when there is no current vote.

Settings optionally changeable by any participant

Disallow moderator changes during the refinement session

Sometimes participants intentionally (or not) click on the Request Moderatorship button and change the currently active moderator. The Scrum Master is not happy and tries to restore the moderator state unless some other participant “steals” it.

To avoid this, there is an option in the settings page that disallows any moderator change requests once the room has an active connected moderator. Unless this moderator disconnects from the room, nobody else can become a moderator.

Disallow moderator change

Bug fixes

In rare cases connection cannot be established (Jira add-on)

In some rare cases, some of the users of the Jira add-on could not connect. Now this is fixed.

PWA broken

Installing the mobile app (Add to desktop) allows installation of Scrumpy Planning Poker as native application. When installed this way and starting the app for the second time caused it to loop the loading screen forever. Now this is fixed and the PWA application starts normally.

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!

Jira Server in release Apr 14 2019

The new release is out and it contains 2 major and long anticipated improvements like the JQL bookmarks and Jira Server as well as some minor bug fixes.

New Features

Jira Server

The Jira Server is finally approved and available for installation on your Jira Server instances The marketplace link is here.

When installed, the add-on behaves like the well known Jira Cloud add-on. There is still no Confluence integration with automatic summary generation though.

Jira Server add-on

Recent queries and query bookmarks

Finally, we introduced a great improvement on the way how JQL queries are maintained (same for GitHub and GitLab queries).

The drop-down box for the queries now shows the recent queries, the bookmarked most-often used queries and example queries which can be used as a starting point. Note that the bookmarked queries are excluded from the recent queries to save space in the drop-down box.

Bookmark queries and recent queries

Bugfixes

Gravatar sign in

The Gravatar sign in now works again. It works by first entering the e-mail address of the profile, then the avatar appears on the right side of the e-mail box and then when pressing this button with tooltip “Sign in as <your user>”, the Gravatar profile is used.

Add To Home Screen

Sometimes after installing the Scrumpy Planning Poker as a mobile application, starting it leads to infinite loop. Now the most recent room is open and the application starts immediately.

Disabled cookes

Navigating to a room with the local storage (cookies, etc.) disabled caused by add-blockers, anonymizing tools, etc. lead to inability to enter the room. Now Scrumpy can be used with those tools.

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!

GitHub and GitLab integration in release Apr 07 2019

Introduction

In this release there are quite some major improvements. A lot of work has been done to improve the performance and add support for new platform integrations.

New features

The quite big set of new features include GitHub, GitLab, Confluence summary improvements and complete refactoring of the code to allow great performance in the browser.

GitHub support

Now it is possible to integrate with GitHub directly and using GitHub queries it is easy to list and add stories for estimation. Both issues from free public repositories as well as private repositories can be estimated.

Sign In with GitHub

Signing in Scrumpy Planning Poker can now be done with GitHub. Just select the button from the list of social sign in and you’ll be listed in the planning poker room with your GitHub avatar and name:

Sign In with GitHub

After signed in, others will see your GitHub profile, but access to issues is still not set up.

Integration

To complete the configuration, go to the Settings page and set the GitHub access token that was previously created.

Configure GitHub integration

To create a personal access token for access with GitHub, go to your settings page and choose Personal Access Tokens.

As in the Jira Cloud integration, there is an option to add comments to issues that are being estimated. The comment includes a link to the poker room as well as the result of the estimate.

Listing issues

To find the issues that will be estimated and add them to the list of planned story, as usual, search for the issues in the query box. The queries supported are GitHub queries which can be used to find any issue in both public and private projects. For example, to list only issues in a particular project, use the repo: prefix, for example repo:scrumpypoker/test. You can list stories assigned to a user, created by a user or just do a free-text search for example Abracadabra+repo:scrumpypoker/test will search for all issues that have Abracadabra in the summary or description and belong to the scrumpypoker/test project. More information about the GitHub queries can be found in the GitHub Search documentation.

In case you forget about this link, it is always accessible from the story context menu (About GitHub queries):

Show more information about GitHub queries

Editing issues

The collaboration editor is integrated with GitHub so you can edit in-place the GitHub summary, description and labels as in the Jira add-on.

In-place GitHub issue editing

Estimating the stories

Since there is no field that is designated to story points in GitHub, this is done using labels. The label estimate:<points> is used to mark the estimate of a story. Any previous estimate is removed prior to assigning a new estimate.

Estimate story through the labels

GitLab support

Now it is possible to integrate with GitLab directly and using GitLab project-based free-text search, it is easy to list and add stories for estimation. Both issues from free public repositories as well as private repositories can be estimated.

Sign In with GitLab

Signing in Scrumpy Planning Poker can now be done with GitLab. Just select the button from the list of social sign in and you’ll be listed in the planning poker room with your GitLab avatar and name:

Sign In with GitLab

After signed in, others will see your GitLab profile, but access to issues is still not set up.

Integration

To complete the configuration, go to the Settings page and set the GitLab access token that was previously created.

Configure GitLab access token and project

Except the personal access token, the GitLab integration needs also a root project that will be bound to this planning poker room. All queries for issues from now on will be for this project only. This is a bit different from the GitHub integration due to the GitLab specifics.

Note: you cannot start estimating stories until both the token and the project is selected. You can generate a personal access token from the GitLab settings page. Just make sure you give it API scope.

Listing issues

Issues can be listed from the search query using free text and wildcard matching as described in the GitLab search documentation. For example, exception free text pattern matching, you can use #1 for for issue number 1, #2453 for issue with IID 2453, etc.

Search for issues in GitLab project

Editing issues

The collaboration editor is integrated with GitLab and the currently focused issues can be edited as usual. Additionally, comments can be viewed (only the ones added by real people, e.g. excluding the system comments) and labels can be edited.

In-place editing of GitLab issues

Estimating the stories

As in GitHub, story estimation happens in the labels. When a story is estimated, a label is created with the value estimate:<points>. When the story is estimated again, the old estimate is removed and the new one is added.

Estimation in the labels

As in the GitHub and Jira integrations, when the Add Comment option is checked, a comment is added in the issue after each successful estimate:

Comment generation and history record from the issue

Manual Confluence summary generation

Now there is an easy shortcut to generate a Confluence summary page after the refinement session is over. Previously, this was done automatically. From now on, this option is available only for manual trigger. The generation can be triggered from the … context menu of the refinement session when the root Confluence Page that will hold the reports has been assigned from the Settings page.

Generate Confluence summary page

Fixed Bugs

Together with the features, several bugs have been fixed.

Social login not working

Due to Twitter requesting extra information and Google migrating away from Google Plus, those two social login buttons did not work. Now they are back in order.

Social login working again

New Room creation not always successful

Sometimes, creating a new room required you to manually refresh the page to see the cards. Now this is no longer required and the room is open as soon as it is created after pressing the Poker Now button.

Confluence not able to select a root page

The configuration to choose the root Confluence page in the settings was gone and now it is back in place:

Select Confluence page for summaries

Open voting in release Dec 9 2018

Introduction

The new release includes valuable new features requested from the feedback form like open voting, extra cards, custom Jira story points numeric field, etc.

New features

The following new features are included in the latest release.

Open voting

The open voting feature is accessible from the settings and discovers the vote of each participant as soon as it is done. This is also called open voting and allows immediate discussion of each vote in the team.

To open the voting, go to the Cards tab in the Settings page and check on the Open voting checkbox:

Open voting
Open voting

Once it is enabled, during the voting process the the votes of each participant are open and visible to the others.

The open voting is both available as a global setting as well as a preset that can be assigned to particular tickets.

Custom Jira field for story points

Some Jira projects have a non-standard structure and the Next Gen field Story point estimate or the Jira software’s Story Points are not the used field for story points. Now a custom field for the story points is available to be configured from the Integrations tab of the Settings page. The new option is called Jira estimate field and is used only when there is neither Story point estimate nor Story Points field in the project’s Edit screen.

Jira estimate field
Jira estimate field

Note: as a kind reminder, if the story points is not updated, please make sure that either Story point estimate or Story Points or the new custom field is available in the Jira project’s Edit screen. Please contact your Jira project administrator to configure those fields properly in case of non-standard Jira setup.

Extra cards

Now optionally there are 6 more cards available for voting. They increase the scale for all types of cards. Those cards are a natural extension in case the highest estimate points/time value is higher than the available cards.

The new “Joker” cards are disabled by default, but can be quickly enabled from the Cards tab of the Settings page globally or per preset as any other voting set card.

Additional cards
Additional cards

Some extra choices of card backgrounds

Optionally, per-participant it is possible to change the card background out of several available options. In the near future we’ll add more and improve the existing backgrounds.

Those backgrounds are available only when the simplest monochrome types of cards are selected from the personal settings tab of the settings page.

Card backgrounds
Card backgrounds

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!