Gitlab, sorting and voting improvements in release Sep 20 2020

Introduction

The new release is out and this time it contains more bugfixing and improvements rather than new features. Most of the improvements are due to customer feedback. Yes, we’re glad when we receive a support request with a usability improvement, a new feature or a reported bug! Bugs are fixed as soon as reported aiming for the same day release.

New Features

The new feature are small and we hope most of you will treat them as convenience improvements. Also special attention is paid to our friends who translate Scrumpy Poker in their language. We’re so glad that we already have Portuguese (Brasil) translation! Now translation is way easier than before and can be tried out immediately inside the app.

Free scale voting with input box

Some customers find the slider not convenient enough when voting using free scale both for story points and for time estimates. That’s why now the free scale is available also as numeric input box and is synchronized with the slider.

The rounding on hours, days and weeks depending on the switch settings of the story preset might not be convenient for all users as snapping may not result in accurate estimate. To solve this, there is a shuffle button the switches between snapped and unsnapped free scale voting. Toggling the shuffle button hides the hours/days/weeks/months switch button.

The unsnapped voting allows entering expressions like 1w 2d 4h or 2d - 4h. The values will be synchronized with the slider.

Sorting of stories

The order of stories was previously fixed. In some cases it’s convenient to sort them by estimate value or by title. When sorted by estimate value it would be obvious which are the most heavy tasks to implement and which are the lightest to implement. Additionally, sometimes stories are added ad-hoc and it’s convenient to sort them by title.

The sorting order is applied to the current user only, e.g. not to all participants in the voting room. That’s why, for the moderator, the drag handle for moving issues up and down will disappear since order is now overridden. The visible order can be applied to all users (e.g. all stories reordered) by pressing the “Apply for all participants” button. Then the custom sorting will be reset and the drag handle for manual sorting will appear again, this time the order of the stories will be according to the new sorted order.

The widgets are as follows:

  1. Sorting subject (either estimate or title)
  2. Sorting order (either ascending or descending)
  3. Apply this order to all participants
  4. Reset current sorting order

Sorting is also available in the history drawer. The sorting order there can be set independently for the sorting order of the planned stories.

Gitlab weight and time estimate

Before the Gitlab integration was setting the story points as labels in the format estimate:3. Now the estimate is set to the Weight field of the issue and those labels are no longer used.

Before the Gitlab integration wasn’t able to update the time estimate at all. Now the time estimate field is updated when time mapping is used in the room settings.

Mini Poker now also in Jira Cloud Mobile

The Mini Poker (e.g. issue extra compartment) is a nice UI extension for ad-hoc estimations inside Jira Cloud. As of this release it is now available also in Jira Cloud Mobile (iOS and Android).

This way voting can be done from inside the mobile app without any join requests for registered Jira users in the current instance. For all external voters the old rules apply – using the PWA Scrumpy Poker mobile app with a request to the moderator to join the planning session.

Dynamic translations

Warning: developer zone. We had quite some interest in our translation program. Our friends have contributed Portuguese (Brasil) translation. We’ve found out that it’s a bit tricky to translate and then wait for the next release cycle to see the results.

That’s why we’ve added a new feature targeting people who translate the texts – the current translation can be automatically tested in the browser both for the add-ons and standalone.

The procedure starts by creating a free PASTEBIN account (if not already available). Then create a new paste out of the translation file that you have so far, e.g. es_AR.json for example and remember it’s ID. The ID is the identifier at the end of the PASTEBIN URL. For example, if your URL is https://pastebin.com/raw/V1S2ae8D, the identifier that you need is V1S2ae8D.

After the paste identifier is available, please copy it to the clipboard and press the “Select new translation” button in the language menu at the top right corner (the one with the translate icon).

Note: if you click the Translate… text or the Github icon you’ll be redirected to our translation repository. So click on the translate button on the right.

Then you’ll see a small input dialog box where you can finally paste the identifier of your paste.

If the ID is valid and all went well, the new translation will appear at the top right corner inside the language menu.

The “New translation” language behaves as the other languages when selected – it changes the language of all widgets as specified in your PASTEBIN paste.

You can switch between languages to compare the result. When you edit your paste inside your favorite PASTEBIN editor and then reload the page, the new translation will be immediately available. This way you can use the PASTEBIN editor for editing the text and view the changes from inside Scrumpy Poker.

Bugfixes

Clear stories list while typing

Before, while typing a JQL/Gitlab/Github query in the search box the stories results were merged leading to enormously huge lists of stories. This was not convenient at all when all the stories had to be added to the list of planned stories.

This has now been fixed and after each editing of the search box the results are cleared. This way only the last result after typing has stopped will be visible in the drop down.

Not able to complete voting from Micro Poker

The complete button in the Micro Poker section of the Jira Cloud add-on was not visible and thus not able to complete the voting. Now it is visible and the Micro Poker section can be fully utilized for ad-hoc voting.

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!

Micro and Mini poker in release Sep 13 2020

Overview

The new release brings many new improvements some small bugfixes. The most prominent new features is the ability to limit allowed moderators to rooms in Jira Cloud. Other features include the Micro and Mini poker which is an extension to the Jira Cloud user interface for more convenient voting. And certainly the concurrent external user join requests handling is much improved.

New Features

There are many new features introduced, so we’d be glad if you provide feedback and bug reports to our support page so that we can address any issues in a timely manner.

Moderators restriction

Now for Jira Cloud users we’ve provided an extension to the add-on configuration page to restrict moderators for a room to only certain Jira Cloud users. This way not any registered user can become a moderator, but only those who are allowed by the instance administrator.

The instance administrator can navigate to the configuration page of Scrumpy Poker from the Configure button in the manage plugins section.

The configuration page has a specific yellow toolbar to indicate that this is an administrative area. When you navigate to the Rooms tab, you’ll see the list of projects in the system. If your instance has many projects, the list can narrowed down with a search criteria as displayed in the screenshot below.

When you expand the project, you’ll see one or more tiles which define the available rooms in this project. There can be more than one room in a project – one room for the project itself and one room for each board in this project. The rooms may not exist yet since they might not have been used yet.

The tile color indicates the existence of the project room. A dark color indicates that the room was already created and used. A light color means the room is not there yet. Even if the room is not there though, you can set the allowed moderators for this room.

When there are no moderators allowed, this means any Jira user in this instance with access to Scrumpy Poker can become a moderator. To change this, you can add at least one person as a moderator. When the list of moderators is not empty, only the users in the list can be moderators. The Become Moderator button and the Star button in the user interface will disappear to users who are no longer allowed to become moderators.

The moderator is added from the + button in the right middle of the tiles. When the button is pressed, a small user selector dialog box pops up where you can search for users in the instance by name. Clicking on the listed user will close the selector and choose the user to be a moderator in the room. There can be many moderators in each room. No moderators means any instance user can be a moderator.

When a moderator has to be removed from the room, the small (x) button displayed as a badge to the user can be pressed.

Each tile has some real-time status badges showing information like the current status of the room (e.g. none, preparing, voting, summary), the number of participants and the number of stories that are scheduled for estimation.

The information is updated in the admin page in real time as users enter rooms and modify them.

Micro poker

The micro poker is a small section in the issue screen that allows you to schedule a ticket for estimation and even start the estimation if you’re the moderator. The micro poker section is convenient when you need to see all Jira ticket information and extra fields and still be able to quickly vote without too much hassle.

You can use the micro poker section to only prepare the room by adding issues to the top or the bottom of the list when in the advanced query section in Jira or you can use it for ad-hoc estimation of any ticket in the backlog or the current sprint without leaving the usual Jira screens.

The Micro Poker room is displayed when pressing the poker icon in the Issue Toolbar. Pressing the button is usually once per Jira issue, but Jira Cloud can adjust the behavior, show/hide the button and the section at its convenience while monitoring the usage of the feature.

If the Micro Poker section is visible in the issue screen, it will show a POKER NOW button. Pressing either the button or the poker icon in the issue toolbar will open the poker section with all its bells and whistles. The reason for having the explicit button in the section is to not generate excessive needless traffic. Nevertheless, Scrumpy Poker prepares everything in the background so that when you press the button the Micro Poker content is displayed immediately.

If you don’t want to see the Micro Poker for this ticket, you can hide it from the Jira interface (the three dots in the upper right corner of the section).

The following bullets describe the interface parts that are different from the usual full poker user interface.

1. Schedule/unschedule story for estimation. A scheduled story is visible in the main poker room. Extra options for scheduling on top or on bottom of the list of stories is also available (see below)

2. Number of stories scheduled for estimation in this room. This is the number of tickets in the planned stories list of the poker room.

3. Open extra compartment for voting. To start voting, you can either press the play button or open this extra compartment and select a card or move the slider if a free-scale voting is configured.

4. Switch between the available rooms in this project. There is usually more than one room per project – one for the project itself and a separate room for each project board.

5. Shows connected users to this room. This is the list of connected users and their vote status/votes depending on the room state.

Before the story is scheduled for estimation, there are some extra option about the scheduling of the story and the story itself as described in the following picture:

6. Issue estimation history. If the issue has been estimated in the last month and the planning session has not been yet deleted, the issue estimation history is shown. The history shows what is otherwise available in the left pane of the regular poker room, but specific to the currently selected issue.

7. Add to top of issue list. This will add the story on top of the stories list of the planning session.

8. Add to bottom of issue list. This will add the story on the bottom of the stories list of the planning session.

After the story is added, there is an extra button that helps with switching the card preset for the story:

9. Switch story preset. When you have at least one preset defined, you can assign it to this story.

When voting, you can lower down the list of cards (or free scale) with the down arrow button (10) as described in the screenshot below:

The Micro Poker section can be completely disabled for the whole instance from the configuration section of the add-on. Go to the Configure button and then on the main page, at the bottom check the Disable Micro Poker checkbox as described in the screenshot below:

Mini Poker

The Mini Poker section is a bit bigger than the Micro Poker and that’s why it’s named like that. It occupies bigger vertical space and the same toolbar and rules appear for the Mini Poker as with the Micro Poker.

The Mini Poker has most of the features available in the regular poker room with some exceptions (like the options for example, the vertical history button, list of issues planned, etc.). This view is more designed for ad-hoc voting from inside Jira rather than a separate dedicated session.

1. Switch Room. This button is used to switch between project and board rooms for this particular project

2. Show connected users. This button brings in the right pane from the regular planning poker to see who is online and who has voted.

The rest of the buttons are the same as the ones available either in the full poker room or the Micro Poker room.

The Micro Poker room can be disabled from the configuration section:

Switch Room

A new Switch Room button is available both in the context menu for the regular poker room as well as the bottom action line. It allows you to switch to another room for the current project. Each project maps to a room, so does each board from this project. A project with two boards maps to 3 rooms that can be switched using this button.

The button is also available from the bottom action line

When the Switch Room button is pressed, a room selector is displayed at the bottom of the screen:

Query issues that are scheduled for estimation

You can now execute a JQL from Jira advanced issue search to locate issues that have been scheduled for estimation.

The query above shows all issues that are scheduled in any room. The ‘name’ property actually contains a comma separated list of room identifiers.

To show the issues that have been estimated, you can use this query:

issue.property[room].name = “”

To show issues that have never been scheduled for estimation, you can use this query:

issue.property[room].name is empty

Enable/disable extra cards

Now it is possible to disable the extra cards (coffee, brownie, etc.). When all cards are disabled, the extra card disappears and voters won’t be able to vote with the funny cards again until enabled.

The extra cards can also be enabled/disabled per preset – e.g. to have extra cards in one ticket and no extra cards for another ticket.

Copy Jira link

Now it is possible to copy Jira link instead of the regular guest (external) link. This way there won’t be any questions for the moderator to accept external voters in case the user has Jira registration and is logged in.

Please use the Copy Jira link option when sending to users which are registered Jira users in your instance.

Fixed bugs

Multiple simultaneous join requests

There were some concurrency issues when more than one external person tried to join the room at the same time. Only the first one was let in. The concurrency issues have been solved and now multiple join requests can be handled by the same time by the moderator:

Estimate not rounded

When the result of voting resulted in more than one digit after the decimal point, it was not rounded in Jira.

Now this is fixed and the result 2.3 would be set in the story points field.

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!

Optional external voters in release Aug 08 2020

Introduction

The new release contains two major improvements for Jira Cloud and Server users. Now the scrum master has more control on the external voters joining the planning session and the performance of the add-on for Jira Cloud is improved.

New Features

Disable external voters

For scrum masters who do not have teams outside of Jira or any mobile app users, now it is possible to completely disable the external voters feature. This way now guest voters would not be able to join in this room anymore. The option is in the Jira integration settings in the room.

Even if external voters (e.g. the mobile app) are allowed, the moderator has to first give a permission to the joining request.

Show the QR code on demand

Before, the QR code for joining through the mobile app was always visible on the screen and it is sometimes not wanted especially when the room is shared through a video call to third party users. That’s why, now the QR code is shown only on demand when clicking on the QR code icon and the QR code is visible for 60 seconds. To show the QR code one more time, the QR code button has to be clicked again.

Ask moderator for approval when joining from the mobile app

There is a series of improvements in the external voters subsystem that provides read-only access to the refinement stage of the room.

Step 1

When joining through the mobile app or external browser, to be able to vote and view the ticket being refined at the moment, an additional human check (recaptcha) is enforced.

Step 2

After the human verification step is successful, but the external voters are disabled or the room moderator has rejected your request, you’ll be sent back to the same page. You can contact the room moderator by any other means and request to enable the external voters or accept your request.

If the room’s moderator has not yet entered, or your request is not yet accepted, you’ll see a message box stating that your request is being processed by the moderator.

Step 3

If the moderator rejects your request, you’ll be sent back to the room’s initial page where you can fulfill the human verification process again and send a request again if you believe that this was a mistake.

If the moderator accepts your request, you’ll be sent to the room’s main page and you can participate in the voting process with the other participants. Certainly as before, moderator requests are not allowed (and not possible at all). Only users logged into Jira can be moderators.

On the other side of the barrier, the moderator sees the following request approval dialog box for each mobile app or external user:

Declining is not forever, the user can make a second attempt after passing through the human verification process (recaptcha).

Accepting the user is also not forever, it is for the lifespan of the current refinement session. The refinement session ends when all participants leave the room or after few hours of inactivity. On the next refinement session the external users must request access again.

Kicking out a user will enforce passing the human verification process for this user again. Disallowing external users will kick out all currently joined external users.

Jira Cloud add-on performance improvements

Now the Jira Cloud users will be able to access the system way faster than before.

Fixed Bugs

The clear all stories button is back

For a week the clear all stories button was not available. Now it is back and the currently planned stories can be cleaned in bulk.

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!

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!