Voting views in launch Sep 18 2022

Voting perspectives in release Sep 18 2022

Introduction

After fairly a while of silence, we’re prepared with a serious new launch. It addresses the pile of most necessary options requested. Beneath is a listing of latest options and bugfixes out there on this launch.

Notice: When you expertise points, for instance you can not choose tales as moderator, please totally reload the web page (Shift + Reload browser button). This can make sure that all static assets are downloaded.

New Options

The brand new options are centered round extra usablity with the collaboration editor, extra intuitive interface for the asynchronous voting and Jira enhancements.

Voting views

The voting views present a unique estimation view on a ticket. In lots of instances it’s wanted to estimate tickets from totally different viewpoint, for instance complexity of implementation, testing effort, enterprise worth, system threat, rank, and many others. Within the earlier variations it was attainable to estimate a ticket solely from one viewpoint solely. Now it’s attainable to create a number of voting views and assign presets to them. This makes it attainable for sequential estimation of the identical story with a unique methodology and replace totally different fields for every perspective.

The views are managed immediately from the story view and new views might be added with out going to the room settings. They’re utterly customized and ad-hoc and might be named in any handy method. Every perspective has additionally a brief description that may be edited in-place. The outline is an effective addition to the identify to indicate the contributors what they’re voting for.

Notice: It’s preferable to maintain the attitude names brief in order that no horizontal scrolling is required when switching views.

Instance views: Common, Enterprise Worth, Threat and Time estimate

The benefit of views is you can estimate one single story from a number of views in a single shot. In horizontal story circulate when the common estimation in story factors is full, the attitude is routinely switched and the subsequent story from the brand new perspective is estimated. The method is repeated when estimation is full.

An alternative choice is to do swap to the vertical story circulate. On this mode all tales from the common perspective are estimated and when prepared the subsequent perspective is activated. When all tales from the brand new perspective are estimated the subsequent one is activated and so forth. This mode is handy for groups that distribute the planning session for various teams of people that estimate solely a selected perspective.

Every perspective can have a preset assigned to it. On this case, when a brand new story is added to the preset, the attitude preset is routinely assigned to the story. Since every preset can have a customized estimate area, which means estimating a narrative in every perspective will replace a unique area. This enables estimating a number of fields each Numeric and Time of a narrative. You possibly can actually have totally different fields, totally different description fields, totally different estimation playing cards and modes per preset making the out there mixture for estimation capable of match any want.

Similar story with totally different views present totally different kind of estimations

A handy solution to populate the tales for all views is row by row as if all tales are in a desk. There’s a context menu command that populates the identical story in all views routinely assigning the presets to it. The command is named ‘Clone story to all views’.

Clone story to all views

When the estimation session begins, tales shall be switched routinely and playing cards/estimation mode modified as the method flows. This manner estimating a narrative from totally different views turns into a clean expertise.

Instance setup

First, lets go away the default perspective unchanged (it’s unnamed, the primary icon within the checklist of views). It’s going to estimate our story with story factors as ordinary.

Let’s create a second perspective known as Threat that updates a area known as ‘Customized Quantity’. That is carried out by creating the Threat perspective from the ‘+’ button within the story checklist.

Create perspective ‘Threat’ with usable description

Subsequent comes assigning a preset that shops estimation in numeric area ‘Customized Quantity’.

Create preset

Set the ‘Customized Quantity’ (or no matter area you’re utilizing) as estimation area.

Assign the Threat preset to the Threat perspective

Lastly, create a 3rd perspective known as Time that may maintain time estimate. That is carried out by creating the Time perspective from the ‘+’ button within the story checklist and assigning a preset that shops estimation as time, e.g. it has story level to time mapping. Let’s additionally allow free scale in order that arbitrary time might be given.

Create a Time preset with time mapping and free scale voting

Assign the Time preset to the Time perspective

Notice: For estimating with time, please both use the default perspective in case Time is the default board estimation in Jira or set the sphere ‘Time monitoring’ because the estimate area for the Time preset. Within the final case please be sure the ‘Time monitoring’ is within the Jira edit screens for this situation kind.

Now let’s add a narrative and clone it to all 3 views (‘Clone to all views’ button). When the voting session begins the playing cards and up to date fields will differ in accordance with the preset assigned to the attitude. In a single shot the story may have 3 kind of estimates.

Now when scrolling by the views the identical story appears to be like totally different in every perspective.

Further fields modifying

Beforehand the Further Data part within the collaboration view confirmed few static fields. This was not very handy for extra complicated tales which requires the show of a number of fields, modifying fields whereas voting for the story, and many others. Now the it’s attainable to customize the checklist of fields displayed in a narrative primarily based on the story preset and make it simple to alter assignee, dash, add labels and lots of extra. Virtually all fields which might be seen in Jira might be displayed and the order and the checklist of fields which might be displayed is totally customisable so as to focus solely on the important data in the course of the estimation.

By default, the room begins with no extra fields displayed. The checklist might be edited from the settings. There’s a shortcut button although to rapidly get you began.

Add most typical fields with one click on

After urgent the button for including the most typical fields, edit bins for altering the difficulty kind, assignee, labels, and many others. are routinely added. When you’d like to customize the order and add different customized fields, this may be carried out from the settings. Actually, as an alternative of the default checklist of fields a person setup might be created from scratch from the settings field. Every area configuration is particular to the present preset if such is created. In any other case, as ordinary, the settings are modified globally for the room.

Settings for arranging the additional fields to show

After the fields are configured, they may change as per their outlined preset (if any) whereas scrolling by the scheduled tales for estimation.

Listing of editable widgets capable of change the writable story fields

Notice: Some fields could not seem for sure points. For instance fields particular to Challenge screens received’t be seen for Bugs. When you don’t see your area, despite the fact that you’ve added it within the settings web page, please test if this area is displayable for this undertaking and situation kind.

Notice: When you observe {that a} widget just isn’t correctly displaying or modifying a customized area, please report that to us with sufficient details about the sphere kind. We’d be blissful to repair it within the subsequent releases.

Extra description fields

To this point solely the outline area was displayable and editable within the collaboration view. Now any multi-line area might be added to the collaboration view within the description part. Such fields are the Setting, Acceptance Standards and others. They are often different plain textual content or wealthy textual content. The checklist of fields is managed from the room settings and is particular to every preset (if outlined). This enables switching to the proper description fields when specializing in various kinds of tales or voting views.

Customized description fields

When the outline fields are correctly configured with Wealthy Textual content and Plain Textual content to fields that needs to be displayed, they are going to be proven within the collaboration view.

Description, Acceptance Standards and customized description fields

Notice: Please use presets to assign particular description fields to particular situation varieties in any other case chances are you’ll get empty textual content or errors when modifying the descriptions.

Notice: Please be sure you put Wealthy Textual content to description fields that help styling of textual content to keep away from having unusual HTML tags within the description when modifying them each in Jira and in Scrumpy Poker.

Feedback

With this launch it’s now attainable to view feedback within the collaboration view. The feedback are displayed latest first and there’s an increase button to indicate extra. Often the highest 5 feedback are sufficient to show within the ticket to get sufficient context, however extra might be proven on request.

Listing of high feedback displayed within the collaboration view

New feedback might be added with the Add Remark button. The feedback can include wealthy textual content, e.g. might be formatted and styled as in Jira.

Including feedback to a difficulty

Extra intuitive asynchronous voting

To this point asynchronous voting was a bit awkward as expertise. The voting needed to be carried out by a button on the proper aspect of the story. This result in errors as a while the voting was activated as a card was pressed as an alternative of this button. Now this has been addressed and the asynchronous voting has 2 modes of operation.

Asynchronous voting mode

It is a new mode of operation. On this case no person besides the moderator can begin the voting session. When urgent the voting playing cards the vote is marked and statistics for voting is collected. The moderator can at all times press a card so as to add his/hers vote to the difficulty or to press the donut icon to solely settle for the opposite participant’s votes.

Asynchronous voting mode

This voting mode is appropriate for utterly asynchronous operation when there’s a crew in one other time zone contributing with votes.

Collaboration voting mode

That is the outdated mode of operation. On this mode of operation anybody can begin the voting when specializing in the at the moment chosen story by the moderator. It’s a regular voting mode with the slight distinction that there are voting statistics who voted earlier than and when the votes are accepted the at the moment taking part customers can see the votes of customers who voted asynchronously.

Collaboration voting mode (a.okay.a hybrid voting)

Use instances

There are a number of use instances for utilizing asynchronous voting. They rely on the provision of crew members, time zone distribution, and many others.

Workforce doesn’t wish to focus on votes. On this case Asynchronous Voting can be utilized. When the crew members full voting, the moderator will see which crew members have already voted and simply press the ‘donut’ button on every ticket to simply accept the estimate. Asynchronous modePart of the crew is in one other time zone and can’t take part within the dialogue of estimates. On this case a part of the crew members can vote prematurely. The remainder of the crew members who can seem on-line can vote the same old method in collaboration mode contributing on high of the already given early votes. On this case the Collaboration Voting can be utilized and this mode might be swap proper earlier than beginning the collaboration session to keep away from incidental begin of the voting by an early voter and permit early voting actually. When this mode is switched, the early votes can be found, however it isn’t attainable for the moderator to only settle for the votes. The at the moment on-line crew members should vote as ordinary. The early votes shall be added to the outcome. Collaboration mode

Search filters

Jira has search filters that may be assigned to boards to make situation itemizing simpler. Boards can share filters and in addition these filters can be utilized for some predefined queries to which the Jira customers are used to.

Now these search filters can be found in Scrumpy’s search field. The search filters are a simple shortcut to predefined JQL queries saved within the Jira occasion.

Jira filters

The starred filters in Jira seem as ‘Favourite Jira filters’ within the filters search field. It is a shortcut to the favourite/began filters which might be most incessantly used within the Jira occasion.

Favourite/starred Jira filters

Min & Max vary free of charge scale

Earlier than the restrict of the free scale was restricted by the utmost worth of all playing cards. Now this has modified there’s an possibility to extend the utmost vary or set a brand new min vary with a few sliders within the room settings.

Min/max free scale values

After the ‘Use free scale’ possibility is enabled for the room globally, or for a preset, there are 2 new edit bins that permit the modification of the minimal and the utmost vary of the free scale.

Tens Cube Fingers

To this point the playing cards confirmed exponential complexity of tales that had been estimated. Linear complexity estimation was attainable by a personalized T-Shirt card setup or by the free scale voting (slider). Now there’s an alternative choice to make use of small-range simple to make use of set of playing cards.

The brand new card units are selectable from the room settings. The cardboard units can be found for the settings globally and for presets too.

Fingers

It is a method of estimating tales from 0 to 10. It’s a digital illustration of voters utilizing no playing cards and as an alternative utilizing their fingers for voting.

Finger playing cards

Cube

Utilizing dices it’s attainable to simply estimate tales linearly from 1-12. It’s a digital illustration of voters rolling cube for estimation.

Cube playing cards

Tens

In some instances it could be helpful to measure complexity in proportion, say 0-100 roughly after which exactly regulate estimation within the abstract dialog. Tough estimation by rounding (relying on the chosen averaging algorithm) is the default. Exact changes like 23% might be carried out in the event you allow the ‘Present numeric labels’ possibility within the settings dialog. This manner within the abstract dialog the crew begins with the common unrounded and adjusts it exactly primarily based on the dialogue and crew suggestions.

Tens playing cards

Want extra playing cards? Please tell us in the event you can’t discover your favorite set of playing cards that you just’d like to make use of.

Bugfixes

There are a number of minor bugfixes that made their method by this launch.

Pin code in micro/mini poker

Earlier than you probably have set a PIN code to the grasp poker view (the icon on the left pane of the Jira board) it was not attainable to make use of mini/micro poker. Now it’s attainable and there’s a immediate to enter your PIN code if not but entered. It’s entered as soon as and remembered till modified. This unlocks the mini/micro poker views.

Enter PIN in Mini Poker

Board switching in Jira server

Beforehand the board switching characteristic was solely out there in Jira Cloud. Now boards might be switched from contained in the board room utilizing the identical button (with location icon). It opens board selector dialog field to open a brand new room.

Change room button

Urgent the room selector will open a dialog field within the backside a part of the display screen to seek out one other room to modify into. That is equal of navigating to a different board and deciding on the room.

Fast room swap selector

Attachments not displayed

Earlier than it was not attainable to view attachments as photographs, paperwork, and many others. Now contributors with entry to the story can see the attachments and scroll by them simpler.

Listing of attachments

Moreover, picture attachments might be watched as a carousel preview. When a picture attachment is chosen, a carousel view pops within the backside of the display screen.

Carousel view of picture attachments

Pause resume not at all times triggering instantly

Earlier than typically the pause resume didn’t calculate correctly the remaining time resulting in quick ending the sport after resume. Now the timers for the sport are centralised and pause/resume and the remaining time till the sport ends are correctly calculated.

Gitlab photographs not displayed

Earlier than the gitlab integration used unsuitable picture URLs within the description. Now the pictures are correctly proven. Moreover, attachments are actually downloadable and commenting is accessible (checklist, create delete feedback).

Blissful voting!

All these good options (and stuck bugs) have been accomplished due to our customers – they’ve requested and we’ve got applied them. Please assist Scrumpy Planning Poker turn out to be much more handy for you by submitting a characteristic request/bug to our Function Requests web page or up-vote an current characteristic that you just discover helpful. Thanks!

Author: Peter Garcia