Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleDecember (V 3.7.0)
Release date -

(tick) New features

  • Custom fields for Objectives & Key results have arrived. While in Beta, we are limiting the number of custom fields to 5 & will expand it later on.

    • It is also possible to use the filters on these custom fields.

    • History is also displayed for OKR custom fields.

  • Feedback summary tree chart now allows drill down to look at the distribution of feedback into various tags.

  • Objective & KR titles are now wrapped onto the next line to mimic how Jira issue titles behave.

  • There is now a refresh action available on Objectives & Key results to immediately recalculate progress rather than wait for the periodic job updates.

  • UpRaise admins & super admins can now enable/disable email notifications at the instance level.

  • Continuous feedback trends report is now available for users with ‘Continuous feedback’ → ‘View’ permission set to ‘Always’

  • Feedback summary page enhancements.

  • Introducing ‘Maintain’ type of key results.

🐞 Bugs

  • Minor bug fixes

Expand
titleNovember (V 3.6.0)
Release date -

(tick) New features

  • Explorer view now shows additional columns to make OKR consumption easier.

  • New feedback suggestions feature is now available to encourage interaction among different stakeholders.

  • Feedback summary page revamped to provide more insightful & actionable information.

  • We are introducing filters for custom user profile attributes, this feature will now pave way to User segments.

🐞 Bugs

  • Improved the experience on the UpRaise panel displayed within Jira issue details page.

  • Minor bug fixes

Expand
titleSeptember (V 3.5.0)
Release date -

(tick) New features

  • It is now possible to refresh progress percentage directly from the Objective & KR detail pages.

  • New ‘Alignment’ filter introduced to surface objectives that are of interest such as objectives with no alignments or objectives that only receive contribution from other objectives & so on.

  • Progress charts on Objective & KR details pages are now configurable. Some customers found the progress charts a little too confusing, so we have made them configurable. By default, these charts will be visible though.

  • Shared OKR views can now be managed by users that have the ‘Manage OKRs’ permission. This allows for decluttering of views in case they balloon up to a large number over a period of time.

  • App now allows you to set up reminder frequency while creating the KR.

  • Forms now save the responses every few seconds if the system detects any changes. This improves the experience since there were few instances when users lost their responses due to time outs.

  • New configuration introduced to cap max leave balance at any point in time.

🐞 Bugs

  • Minor bug fixes

Expand
titleAugust (V 3.4.0)
Release date -

(tick) New features

  • Flexible Calendar permissions are now available in the app

  • Resource availability view, our first step in the capacity management direction is included in this release

  • Introducing ‘Recent activity’ section for OKRs to keep an eye on ongoing activity on OKRs.

  • Brought in additional visibility configurations for OKRs to allow hiding of ‘All users’ option completely.

  • Similar to how metric type KR’s progress can be linked to other metric KRs, the same feature is available for To Do type of KRs as well.

🐞 Bugs

  • Form actions from UpRaise were visible on the Jira workflow post functions page, we have now removed them from the screen.

  • UI alignment bug on explorer view fixed.

  • Minor bug fixes

Expand
titleMay (V 3.3.0)
Release date -

(tick) New features

  • Ability to expand one level in the hierarchy view at once, with a single click is now live

  • Customisable UpRaise dashboards are here

    • Same set of dashboard gadgets will be available here as well as on Jira dashboard

  • Now KR based progress calculation shows the linkage both ways. Earlier it was only possible to see which KRs current KR depends on (from the KR details page). However, with this change - now you can even tell what other KRs current KR is linked with

  • Recently there were complaints that the Objective cycle statuses were not updated automatically based on dates. While that should still continue to work as expected, if there is a situation where it doesn’t - then the buttons are displayed on screen so that the action can be initiated by the user

🎁​ Enhancements

  • Complete flexibility with introduction of granular permissions for leave management module.

  • Performance improvements across the entire leaves management module.

🐞 Bugs

  • If you were using the KR based progress calculation, there was a corner case in which it became impossible to delete an involved KR - this is now corrected

  • Carry forward option is now displayed even for ‘Ready to close’ objectives. Earlier it was available only on ‘Ready for grading’ objectives

  • Minor bug fixes

Expand
titleApril (V 3.2.0)
Release date -

(tick) New features

  • New feedback permissions were introduced to implicitly allow direct & indirect managers to view the feedback even if not explicitly shared.

  • It is now possible to add/edit/delete comments on Team member & Reviewer type of forms, once distributed. Soon we will make this possible on other base templates as well.

  • Now objective level grades are calculated as weighted average against the earlier formula of simple average. This means the weight against KRs impacts not just the progress % but the grades as well.

  • New configuration introduced to control rounding off to nearest 0.5 for leave accrual calculations

🎁​ Enhancements

  • Jira DC compatibility

  • Performance improvement on the leaves listing screen

🐞​ Bugs

  • Minor bug fixes

Expand
titleMarch (V 3.1.0)
Release date -

(tick) New features

  • Support for quarterly KR reminders is here. Additionally, you can control the default KR reminder frequency as an UpRaise admin.

  • OKR progress chart dashboard gadget is now available. We are starting to make it possible to have customized dashboards based on UpRaise data.

  • User profile pages now have an additional tab to show forms the user is involved in. Helps in finding the relevant information quickly.

  • Similar to user history, we are now showing the team history on the team profile page.

  • It is now possible to export 360 template responses in an excel sheet.

  • Review forms UI is a bit cleaned up for further UX enhancements.

  • UpRaise panel on the issue details page is relocated in the right hand sidebar.

🐞​ Bugs

  • Minor bug fixes

Expand
titleFebruary (V 3.0.0)
Release date -

🎁​ Enhancements

  • Jira 8.22 compatibility

  • Performance improvement in leave application edit/view screens, especially when the leave duration was long.

  • Metric key results now allow progress calculation based on other metric key results. This improves the progress automation logic where KRs at lower level are helping achieve the KR at a higher level. What’s more, this linkage is also visible on the hierarchy/explorer views.

  • Clone action is now extended to allow for cloning of progress calculation logic that we have just introduced.

  • Jira dashboard gadgets for showing OKRs data in UpRaise in the form of a pie chart is here. It is super flexible and allows for grouping of OKRs in a view based on a bunch of different attributes.

  • Ability to export responses on 360 template distributions in an excel.

🐞 Bug fixes

  • Up until now, the dropdowns were not displaying any values by default. That is now corrected. All of them now display 10 possible values by default & more possibilities can be searched for by typing in.

  • Objective alignment at the time of objective creation used to fail, that is now rectified with appropriate permission check.

Expand
titleFebruary (V 2.9.0)

Version 2.9.0

Release date -

🎁​ Enhancements

  • Jira 8.21.1 compatibility

  • We are now storing the Team related changes in the database. While this history doesn’t show up anywhere yet on the UI, it will become available as part of the next few releases.

  • Some improvements in the Estonian language translations.

  • We are now storing the KR progress in the database instead of calculating it on the fly. This makes it easier for you to filter the OKRs based on progress percentage. Earlier, it was only the Objectives that were returned based on progress percentage filter.

  • We are making progress automation a central concept in the OKRs module. Thus, we have brought the progress calculation configurations to the fore on the create/edit key result pop-up itself. We plan to bring in some more automation-related options in the next few weeks.

  • Team type value, if not empty, is now being displayed at all places wherever team name is displayed. This makes it easier for end users to see what type of ‘team’ they are dealing with.

  • To allow reordering when there are more than 5 key results, we are now displaying a ‘show all’ toggle on the objective details page.

🐞 Bug fixes

  • Some corrections in the Estonian language version of the app.

  • OKR progress chart was displaying progress % as undefined, fixed.

Expand
titleJanuary (V 2.8.0)

Version 2.8.0

Release date -

🎁​ Enhancements

  • Jira 8.21 compatibility

  • Ability to export content from the Leave balance tab

  • Now you can export additional information about users involved in continuous feedback. This can help you map the users to different attributes and come out with cohort specific reporting.

  • It is now possible to clone OKRs from any other cycle into a selected active/scheduled cycle. There is also the option to include KRs, Alignments etc

  • Now exporting OKRs will only include those columns that are visible on the screen.

🐞 Bug fixes

  • Minor bug fixes