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!

Custom steps and days/weeks/months breaks in release 25 Nov 2018

Introduction

The new release is out and has some small bug fixes on the free scale voting as well as some extensions for the scale and steps for the free scale voting. The release also gradually prepares for the future addition of custom cards and support for private Jira instances.

New features

Custom step for the free scale

Now the step for the free scale can be changed between 1, 0.5 and 0.25. This brings fine granularity for the ad-hoc voting. The scale step can be changed from the Cards section of the Settings page as shown below:

Custom free scale step
Custom free scale step

Custom days/weeks/months breakpoints

The breakpoints when switching between hours to days, days to weeks and weeks to months can be now explicitly defined instead of using the default values only. The default breakpoints are set to switch from hours to days after reaching 8, days to weeks after reaching 5 and weeks to months after reaching 4. Those can be completely customized allowing to estimate with 32.5h or 8.5 days for example. The breakpoints can be adjusted from the Cards section of the Settings page as shown below:

Custom measure breakpoints
Custom measure breakpoints

Better backgrounds for card images in monochrome mode

For the most simplified cards version, now the background is a bit nicer. This small improvement opens the door for custom card backgrounds in the future release.

Better card images
Better card images

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 support in release 18 Nov 2018

Time labels for sized cards

Introduction

The new release is out with one major new feature – support for Jira Server. Finally, integration is possible through username and password from the Settings page. Jira Cloud has support for the Next Gen projects field “Story point estimate”. Additionally, this release opens a lot new possibilities with time estimation and ad-hoc voting.

New features

Jira Server support

The Integrations tab of the Settings page now has the ability to connect to Jira Server using username and password. The password is entered where the token field is located for Jira Cloud. The Scrumpy Planning Poker is now smart enough to detect if it is connecting to Jira Cloud or Jira Server and properly authenticate. Just specify your username and password for Jira Server and the application will be able to integrate with Jira Server.

Jira Server integration
Jira Server integration

Briefly, use API Token for Jira Cloud and your password (plain text) for Jira Server.

The special check box called “Use HTTP instead of HTTPS” is used to communicate with Jira Server using insecure protocol. Although this is not recommended, some instances run insecure.

The Next Gen projects

There are new agile projects in Jira Cloud which have the Story point estimate field by default. This field was so far not updated by the application. Now we’re updating it.

Next Gen support
Next Gen support

Using estimate values over sizing for T-Shirt

For some users the L/XL/M/3XL etc. cards were a bit confusing. Now there is an option to add a label for each card with the custom mapping value. This can be either story points according to the custom mapping table or time in case the story point to time mapping is activated.

Prefer card values
Prefer card values

Additionally, the participants votes are displayed as values (1.1w, 5.6h, 42, etc.) instead of L/XL when using values is preferred. Same goes to the results in the left pane.

Numeric labels on sized cards
Numeric labels on sized cards

When the story point to time mapping is configured in the Settings page, the card labels, user votes and results are displayed using time instead. The format of the time is 2.5h (hours), 4.7d (days), 1.2w (weeks), 4.4m (months). This is particularly useful for projects using time estimates.

Time labels for sized cards
Time labels for sized cards

Note: that when using time estimates, the Jira Cloud/Server stories are updated with time too. This can happen though if only the project to which the ticket belongs is properly configured to use time estimate instead of Story Points or Story point estimate. Make sure those fields are removed from the edit screen of projects that use time estimates.

When using presets, some stories can be estimated with time, some with points.

Mixed estimates
Mixed estimates

Time estimates

This is another major improvement in the latest version that allows to estimate with time not only with T-Shirt, but with the other card sets. Additionally, this option is available not only to Jira users, but to all our customers.

Time estimate is enabled only when the mapping between story point and time is configured in the Settings page.

Story point to time mapping
Story point to time mapping

When using time estimates with Jira integration, it’s recommended that the Jira project to which the ticket belongs is properly configured to use time estimates instead of story point estimates. Otherwise the stories will be updated only instead of the time.

The time estimate can be part of any card preset so for some stories it is possible to have a different story point to time mapping. This is particularly useful when estimating stories from different teams, or there is specific overhead for some set of stories that needs to be reflected.

Time estimates work well with card labels (values) and T-Shirt cards. On each card there is a custom mapped value displayed. The value is calculated as the card story points multiplied by the time mapping in hours and converted to the shortest representation of time, e.g. 1.1w if more than 5 days.

Free scale voting

This is kind of free ride with voting as it allows to vote with any arbitrary value. The free scale voting can work equally well on story points as well as on time. Certainly, as all the other card set settings, free scale voting is available in the card presets.

Free scale voting
Free scale voting

When using free scale, the minimum and maximum story points form the T-Shirt mapping scheme are used to determine the size of the scale. In case you don’t see the large numbers on the scale, please make sure that the big values in the T-Shirt story points mapping is enabled and properly set. For example, in the image below the minimum scale value is 2 and the maximum is 58 (assuming that all cards above 44 are disabled).

Min/Max scale values
Min/Max scale values

After the min/max scale ranges are configured, it is time to finally display the nice new voting window that allows arbitrary points or time estimates.

Free scale voting with story points
Free scale voting with story points

The step when voting with story points is 0.5 so that 18, 18.5 and 19 can be selected by sliding the thumb of the slider. The voting widget also displays the currently selected estimate as well as the overall complexity of the task. The more time it takes, the more complex it is. When you move the thumb to the rightmost side, it will show 100% complexity.

The color of the thumb and the circular progress bars change with the complexity of the ticket. It starts from green color for the least complex tasks and and goes to red color for the most complex.

The – and + buttons on the two sides of the slider can be also used to move the thumb one step (0.5) to the left or to the right.

Note: after the value is properly selected, you need to press the Vote Now! button. If you don’t press it, your vote won’t be regarded. The more you vote with different estimates, the more the vote uncertainty will decrease. The voters and summary sections will display the certainty level as when voting with the regular cards.

When the story point to time (in hours) mapping is configured to non-zero value, the time estimates become active. The free scale voting gets one more extra sub-widget to select the time scale for easier voting with less slides and convenient estimate. This widget appears on the upper left corner of the voting screen.

Free scale voting with time
Free scale voting with time

Additionally, the extra cards are also displayable from the upper right corner. Still, you can vote to rest, have a snack or indicate no idea what’s going on or emphasize the complexity by voting with infinite estimate.

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!

Time estimates in release 11 Nov 2018

Introduction

The new release contains very few bug fixes as well as new features including time estimates through the T-Shirt styles, better view for the cards when some of them are not active and started with writing the full documentation and instructions for Scrumpy Planning Poker

New features

Time estimates

For the Jira integrations now it is possible to estimate tickets with time. The Jira estimated time and remaining time fields are automatically updated after the voting. To enabling using time, you should first properly configure Jira to use time estimates instead of story points and the Time Tracking and/or Log Work fields are enabled in the default screen for the project.

Voting with time is enabled only for the T-Shirt styles. When you switch to T-Shirt preset or switch to T-Shirt voting, a new section will appear in the Settings page that will enable to create a mapping between a story point and time (hours). If the mapping is 5.75, this means that for each story point the team will need 5.75 hours. When the accepted vote is 2 story points, the estimate will be set to 2 * 5.75 = 11.5 hours or 2 days 3 hours and 30 minutes when estimated in work time. By specifying custom story points for each T-Shirt card and using the time multiplier, it is possible to properly estimate each task with time instead of story points.

Story point to time mapping
Story point to time mapping

The time estimates will not be updated in Jira if the mapping is not set or set to 0 (the default). If the current Jira project is configured to use story points, time estimates will not be used.

Hiding disabled cards

Now the cards that are disabled are not shown on the screen instead of showing a disabled card. This increases the concentration of the team during the refinement process since the cards that are not used are not visible at all.

Hide cards instead of showing disabled card
Hide cards instead of showing disabled card

Detailed documentation

It will take some time until this documentation is fully completed, but we’ll be working on it with priority. This documentation will help a lot to new users that are getting used to Scrumpy Planning Poker. It will define every aspect of the use cases and details, tips and tricks for smooth planning sessions.

The documentation can be found on our web site or using the new shortcuts in the application on the right pane and the Welcome screen.

Shortcuts to documentation
Shortcuts to documentation

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!

Chat and labels in release Oct 14 2018

Introduction

The new release contains nice new features like chat, labels and flags, vote reminders, carousel view for attached images as well as some fixed bugs.

Fixed bugs

Votes of disconnected users were displayed.

Now the votes of users who have been disconnected (mostly by turning off the screens on mobile phones) are hidden and revealed only after the session is over.

Game could not be paused when all participants have voted

Now the pause and resume works as expected all the time.

New Features

Chat support

As a courtesy to our thousand supporters on Facebook we’ve released a surprise feature – Chat! The feature allows exchanging text messages with links during a voting session, which is a very common case for collaboration and saves the time and effort to use another chat software.

Chat support
Chat support

We’ve also paid attention to using the proper notifications for each chat message, both visual and audible, which is shown on the next screenshot:

Chat notifications
Chat notifications

Are we going to soon support video and audio in Scrumpy Planning Poker? Let this be another upcoming surprise 😊

Labels and flags

Especially for our Jira users, we’ve added the ability to see and modify the labels attached to an issue. With a single click new labels can be added as well as issues can be easily flagged. Flagged issues are also displayed in red in the list of stories to refine.

Labels and flags
Labels and flags

Voting reminders

This is an old feature that was pending in the list of requests. Finally, it was implemented and now there is a button during voting which creates an inviting sound to all the users as well as a visual message that it is time to vote. Sometimes discussions can go for ages and a reminder to stop chatting and start voting is very useful unobtrusive attraction of attention.

Send reminder to vote
Send reminder to vote

Carousel view

Before it was not much convenient to view the image attachments in a ticket as the images had to be downloaded before viewing. Now the images are displayed in a carousel view and displayed on the bottom of the screen. This way the navigation is still usable while the bottom half of the screen is occupied with the image carousel. The old way of downloading the images is still possible when clicking on the file name.

Image carousel
Image carousel

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!

Vote certainty in release Sep 30 2018

Introduction

In the new release you can find nice new features like vote certainty level, guest mode, collaboration view for mobile users as well as significant improvements in the way how votes of disconnected users are displayed and few bugfixes.

Fixed bugs

Confluence add-on

Now the Confluence add-on is separated from the Jira add-on as required after the latest updates of Atlassian APIs. If you need to generate nice summary page after each refinement session ends automatically, please install the Confluence add-on located here (currently reviewed by Atlassian)

Confluence add-on
Confluence add-on

Story search box

When the vertical space was not enough to fit most of the stories retrieved using JQL query, the drop down search box was a bit off hiding the search field. This lead to inability to add new stories to the list of stories to refine.

Fixed height of stories drop-down
Fixed height of stories drop-down

New features

Vote certainty level

If enabled from the settings panel, the number of different votes that each participant gave will be displayed on the as badges. The idea is that if during a discussion people vote more than once with a different card this means that they are not certain enough. When the certainty level drops too much, it’s recommended to discuss again the task and re-vote.

Enable vote certainty
Enable vote certainty

Once the setting is enabled, the number of different votes for each participant and the calculated certainty level is displayed on the right pane as follows:

Number of different votes
Number of different votes

The calculation is as follows: If someone votes twice, this vote weights 0.5, if someone votes 3 times differently, this vote weighs 0.33 and so on. The certainty level is considered in info, warning and error level according to the following percentages:

  • Between 50% and 75%: info level
  • Between 25% and 50%: warning level
  • Below 25%: error level

For voting count, the levels are calculated as follows:

  • 2 votes: info level
  • 3 votes: warning level
  • 4 votes: error level
  • 6 votes is the maximum that is accounted

The voting certainty level is also displayed in the summary panel. The team’s scrum master can make a decision whether to re-vote the story or accept the current certainty level.

Certainty level in summary
Certainty level in summary

Guest mode

Recently we had a request to implement guest mode. The guest mode does not allow to participate in the vote, but the guest participant can still watch the voting process and be part of the discussion. The list of guests is separated from the list of regular participants in the right pane:

List of guest users
List of guest users

The guest mode can be enabled from a switch on the bottom of the planned stories.

Guest mode setting
Guest mode setting

The option is not available for the moderator. If the moderator is not allowed to vote, there is a separate setting about this in the settings panel.

Disconnected participants

Sometimes when using smartphones, participants get disconnected when they switch them off during a discussion. Now the disconnected users who voted are displayed in a separate section in the right pane so that their votes are visible:

Disconnected participants
Disconnected participants

Collaboration view for mobile users

Before the collaboration view was available for desktop users. Now the stories, the comments and attachments can be also viewed on smartphones. This removes the need to switch between tabs in the mobile browsers to read the story.

Collaboration view for mobile users
Collaboration view for mobile users

The collaboration view for the currently selected story can be open with the large round button on the bottom left corner:

Open mobile collaboration view
Open mobile collaboration view

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 and attachments in release Sep 16 2018

Introduction

In the new release you can find great new enhancements like comments and attachments in the collaboration view, an option to disable voting auto-start as well a small number of bug-fixes.

New features

Show Jira comments and attachments in the Collaboration View

Sometimes the important information about a ticket is not only in the ticket’s description. Comments and attachments are important so now they are also displayed in expandable sections.

The comments section lists each comment in it’s own paragraph citing the author as follows:

Comments section
Comments section

The attachments are displayed each in their own paragraph and a thumbnail if the file format supports thumbnails (e.g.  image)

Attachments section
Attachments section

Add an option to disable voting auto-start

For some teams it is natural that any participant can vote at any time, even before it is officially announced that voting is enabled. For other teams this sometimes breaks the concentration of participants or causes awkward questions why some people vote too early. To overcome this, there is a new option in the Settings box to disable voting auto-start by any participant. When enabled, only the moderator can start the vote.

Disable voting auto-start
Disable voting auto-start

Add preset to download and upload stories

Now it is possible to import/export the stories together with their voting presets. This means that each story can have its own voting style like T-Shirt for bugs, Fibonacci for normal stories, etc.

Card presets as shortcut under the stories list

Now it is possible to switch presets ad-hoc from a button just bellow the list of stories. Note that this resets the default voting preset for all stories that have no explicitly assigned a preset. If this is done by accident, the old setup can be restored from the Settings page. At least 2 presets are needed to make the button visible.

Add-hoc presets
Add-hoc presets

Add temporary maintenance page

We’re working towards disabling any maintenance issues at all with smooth zero down-time deployment. Until this is implemented, we’ve added a maintenance page which will show that there is an undergoing maintenance which usually lasts between 15 and 25 seconds.

System under maintenance
System under maintenance

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!

Card presets in release Sep 08 2018

Introduction

The new release includes a bit more bug fixes than usual and few new features including card presets which help to use different cards per planned story.

New Features

Card presets

The card presets introduce different set of cards (a combination of card types and enabled cards) per each planned story. The presets can be defined from the Settings dialog box in the Cards tab as follows:

Card presets
Defining a preset in Settings

Pressing the (x) button in the preset chip deletes it. Pressing the (x) button in the preset combo box switches to the default voting cards.

Changing card types and enabled cards while a preset is active will change only the selected preset. The default voting cards will be left as is.

Each preset must start with a unique letter so that this letter is used as a badge for planned stories that have presets defined. By clicking on the story avatar, a menu appears from which a preset can be selected. The menu is available only if there is at least one preset defined.

Selecting a preset per story
Selecting a preset per story

The selected preset can be removed with the Clear preset menu entry. Once a preset is defined for a story, the voting cards will switch as soon as this story is selected.

The early voting for stories with an assigned preset will also show the set of cards that are allowed to be used.

Improved drag & drop

The drag & drop now shows empty space for the item that is being dragged. This makes drag & drop more intuitive and shows exactly where the item will be dropped.

Improved Drag & Drop
Improved Drag & Drop

Add an option to switch adding new stories to bottom or top

Sometimes it is more convenient to append stories to the end of the planned stories list instead of placing it always at the top. There is now an option that allows placing stories at the bottom of the list:

Adding new stories to the bottom
Adding new stories to the bottom

Invite via e-mail

Sometimes it is more convenient to directly send invitation to a list of users via e-mail. This is now possible from the share button:

Invite via e-mail menu
Invite via e-mail menu

A dialog box pops up where a list of e-mail addresses can be entered. All e-mail addresses must be valid to be able to send the invitation:

Send invitation via e-mail
Send invitation via e-mail

Disabling moderator vote

Now the disable moderator vote is more intuitive and is more clear that the moderator cannot vote. A question mark in grayed out state appears as the vote of the moderator to indicate that this will be the default vote if no other participant voted at all:

Moderator not allowed to vote
Moderator not allowed to vote

If there are participants voted or there are early votes, the There be dragons vote of the moderator will disappear.

There is also a +1 suffix to the total number of participants to indicate that the moderator cannot vote and is added passively on top of the other participants.

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!

Import/Export CSV in release Sep 01 2018

Introduction

The new release includes a big new feature assisting users that have no Jira integration (CSV Import/Export) and also some minor improvements on how to reach out for help or ask ad-hoc questions.

New Features

Import and Export CSV

When using Scrumpy Planning Poker as estimation tool for which we don’t have direct integration, our users have to write each story by hand or copy-paste the title and optionally the summary and description.

Now it is possible to import a CSV (comma-separated value plain text content file). The encoding of the file must be UTF-8 to be able to keep the special characters inside. The import/export shortcuts are available just below the cards:

Import/Export shortcuts
Import/Export shortcuts

When you click on the upload button (the leftmost one), a dialog box will appear where you can either select files directly by clicking on the outlined area or drag & drop files from a folder:

Drag & Drop upload
Drag & Drop upload

The format of the CSV file is as follows:

  • Comma-separated values
  • Quoted string entries and unquoted number entries (e.g. current story points)
  • UTF-8 encoding

The header is the following:

  • assignee: The assignee of the ticket
  • avatar: The icon for the ticket indicating if this is a bug, story, epic, etc. (32x32px or vector image)
  • description: A more detailed explanation of the ticket
  • key(*): An obligatory ticket ID, for example AB-1234
  • link: A URL to the system where the ticket is located
  • status: The current ticket status (in progress, to refine, etc.)
  • statusAvatar: The icon for the current ticket status (16x16px or vector image)
  • storyPoints: The currently assigned story points
  • summary: A short description of the ticket

The easiest way to check the format is to export an existing list of stories with the export button.

More shortcuts to interactive help and support

We’ve seen that  some customers ask ad-hoc questions via the feedback form so we decided to add shortcuts for sending e-mail to our info address and an invitation shortcut to our #Slack discussion board. This way we’ll be able to immediately respond to questions on how to use certain feature.

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!

Collaboration editor in release Aug 26 2018

Introduction

The new release from Aug 26 2018 contains many new features like the Collaboration Editor that we believe will make the use of Scrumpy Planning Poker even more fun!

Bugs fixed

New Room

The New Room menu entry is now operational again. Pressing this item creates a brand new Planning Poker room

New Features

Confluence Spaces and Pages

Before, only up to 25 Confluence Spaces and Pages could be displayed, and this caused troubles when setting up a summary page for Jira instances with a lot of spaces and pages. Now the limit is raised to 500, which should be enough to list the needed spaces and pages.

Show the JQL errors

When typing a JQL query, especially when it is a complex one, there is always a chance for making a mistake. Before, the query silently failed returning no results. Now the JQL error is printed just below the wrong query giving a detailed hint what might have gone wrong:

JQL errors displayed
JQL errors displayed

Display the meaning of the special cards

People often ask what is the meaning of the special cards. Well, they were intentionally left without description to let users put their own meanings and semantics. Now there is a short introduction with the most common usage for those cards in the welcome (help) page:

Display the meaning of the special cards
Display the meaning of the special cards

Play sounds when game starts/ends or is about to end

Usually, when the team is focused on reading and discussing the story, some participants tend to start the voting process earlier, before it was officially announced. Also, while being focused on reading the description, it is common to skip the announcement of the voting session start. That’s why, Scrumpy Planning Poker now plays discrete sounds when the first vote is made or the session starts. Also, when the game ends, a notification sound is played too. The sounds can certainly be switched off from the settings panel (active per participant):

Disable sounds setting
Disable sounds setting

Display Jira ticket description

Before, participants had to switch to external systems (e.g. Jira) to view the story details. Now, a separate split pane is displayed which contains the story description. It is now hopefully more convenient to stay in the Scrumpy Planning Poker application and discuss the issue summary and description without having to switch to Jira and then go back:

Split pane with story description
Split pane with story description

Add split pane for summary for non-Jira accounts

For the regular accounts that do not use the Jira integration it was a bit difficult to fit story details in only one sentence (the story title). This caused troubles for the team to get introduced to the story being refined. Now, the user story summary and description are available for display and edit on the right pane (collaboration view). It is now more convenient to enter and show story details that are visible to the team:

Summary and description for non-Jira users
Summary and description for non-Jira users

Collaboration editor (split pane)

And finally, the most important feature in the current release – the wysiwyg collaboration editor. The right pane of the screen, where summary and description is displayed, actually now allows direct editing with a single mouse click (by the moderator only). To add special styles like bold, italic, heading, links, etc. you need to select the text that needs special formatting. Don’t forget to press the Save icon to persist the changes! When Jira integration is active, the changes are directly persisted in the Jira ticket. Also, when edited and styled in Jira, the formatting is also available in Scrumpy Planning Poker! Here is how the collaboration editor looks:

Collaboration editor
Collaboration editor

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!