2023 - Data center UpRaise People

Now there is a default calendar for all the users that is available out of the box. Makes life easier for the first time users so that they can see some relevant data even without creating a calendar on their own.

Overall experience of setting up & editing a calendar is updated for ease of use.

Manage tab under the ‘Leaves’ screen is now revamped for better & consistent user experience.

Almost all screens in the app now support the dark theme.

Performance improvements across the app.

Compatibility with Jira 9.12.1

Minor bug fixes.

360 degree review form templates are enhanced to import users through a spreadsheet.

• Not only that, it is also now possible to add users to an existing 360 template distribution if it is not yet closed.

The bulk user update feature that we had launched recently has become more robust. It will now surface the errors encountered during bulk update.

Updating Units (if you are using the Units feature) is now easier than before.

OKR & Feedback labels are now managed similar to how feedback tags are managed. Meaning, one can now Disable these labels if you want to retire them. Deleting labels won’t be allowed if the label is in use & so on.

User profile attribute based custom reports now allow creation of reports based on user segments.

Importing objectives in the form is now flexible than before. Earlier, the system forced you to choose objectives that were either Ready for grading or Closed and assigned to the team member in that form. Now, we have taken out these restrictions and theoretically, any objectives can be imported into the forms.

Minor change in the ‘Edit team’ pop-up to ensure the ‘Unit’ functionality experience is appropriate for teams using that feature.

Custom reports that are based on user profile attributes already support ‘User segments’. We have improved the configuration experience for such reports to keep it simple.

Now hide the OKR punch-ins that are inaccurate, end up skewing the progress chart. This was a long standing request. However, instead of letting you ‘delete’ the wrong punch-ins the app allows you to hide some of them. This keeps the progress tracking transparent.

OKR grading screen is redesigned for improved information architecture & ease of use 

It is now possible to add a comment on the key result directly from their parent objective details page. 

Default progress calculation for Jira issues linked as Key results is now dependent on the status category instead of resolution. 

Ability to abandon a key result is now here. 

JQLs are now displayed as links for ease of navigation. 

We now allow individual user pairs to be removed from distributions. This serves the use cases where a wrong combination of users was included in the distribution and need to correct it & so on. 

Right hand panel is revamped for better experience in case of form responses.

Before, it was possible to modify the weight even for an abandoned objective. That is now corrected & the app won’t allow updating the weight once an objective is abandoned.

Other minor bug fixes.

Now Metric KR progress calculation can be configured to depend on any type of key results - be it metric, to do or even Jira issues.

Deletion and Deactivation flow for OKR custom fields is now improved to keep the data integrity in place.

There is a new section on the feedback summary page for managers. They will be able to see the feedback their direct reports have received in the given duration as well as see when they had given feedback to those direct reports. Will help managers quickly understand how their direct reports are doing.

New way to visualise continuous feedback is now live with this version. Also available on the user profile page.

Part 1 of the OKR summary page revamp is now available & will be enhanced with a few more sections in the upcoming release.

Similar to Metric KR progress calculation, To Do key results can be configured (for progress calculation) to depend on any type of key results - be it metric, to do or even Jira issues.

New permission option introduced to prevent certain roles from being able to access profiles of inactive/deleted users.

Form templates can now be shared with other users so that they can use these templates in their own distributions. Up until now, you either had to be creator or a super admin to be able to do this.

Beta version of the ‘Roadmap view’ for OKRs is here. Right now, it only supports display of first level of nesting. However, based on the feedback we receive - we will enhance this feature further.

Number of key results that can be configured for progress calculation is now 50. Earlier, this number was restricted to 10.

Distribution user limit is now brought to 500 users from the earlier limit of 200.

Now it is possible to find out Jira issues via JQL that are linked as key results or key result actions to UpRaise objectives & key results respectively.

Create & edit view UI improved for better user experience.

Archival functionality on OKRs is now rectified to be analogous with project archival in Jira.

It is now possible to move an objective cycle into ‘Ready for grading’ (or ‘Ready to close’ depending on its grading configurations) manually. This will allow situations where teams want to grade/review their OKRs before the cycle due date.

OKR custom field delete & disable flows have been updated so that only unused custom fields could be deleted. Used custom fields can only be disabled.

Browse OKRs screen performance improved for better UX even with high amount of data.

Latest comment from Jira issues (which are linked as KRs or KR actions) now appear on the Browse OKRs page (if the relevant columns are displayed on the screen).

User segmentation initial version is being released to lay down the foundation for People automation that is to come in the next few months.

Company directory now allows user segmentation with the help of default & custom profile attributes.

Roadmap view for OKRs is now enhanced to show all the nested elements. It also offers support for zooming in & out along with the ability to choose a starting month.

All form templates (except 360) now offer the possibility to add user(s) in a distribution as long as the distribution is not closed. This will help in containing number of distributions created only for a handful of users who were missed in the initial distribution.

OKR weightage impact is now visible in the form of percentages. Before, it was only in the form of actual weight numbers.

• It is now also possible to look at all the relevant weights in a single click rather than look at them one by one.

• And the weightage can now be configured with any number between (including) 0 and 100.

Now you can import users in a form distribution using an excel sheet. Makes your life way easier.

Minor remaining pieces of OKR weight display in percentage are now addressed.

We have renamed some of the actions on form templates/distributions to make them more inutitive.

It is now possible to create 3 dimensional charts based on user profile attributes within the reports section. This lets you dig deeper into user profile attributes and draw the desired insights.

We have also extended the reports to now support number type of user profile attribute.

It is now possible to bulk update users along with their default & custom profile attributes. This is a three step process analogous to Jira issue bulk update action.

We are now introducing OKR trends report to keep an eye on different patterns across multiple objective cycles.

HRMS sync now supports the Excel file formats (both xls & xlsx) for importing user & teams data. What’s more, one time import is also now possible in these formats. Read more here.

Bulk user update action now shows progress percentage on the screen while the update is in progress.

There was an error while accessing UpRaise when the Jira instance had an oAuth related app (developed by miniOrange) installed. This is now fixed.

There were a handful of errors when UpRaise app was being upgraded from some of the older versions. We have now addressed that.

Search results are now ordered in pickers so that the closest result appears at the top. This solves the problem for some organisations which had more than 25 teams starting with the same name.

Objectives whose due dates are in the past were being displayed in the Active OKRs bucket in the User & Team profile pages. It was happening since the app was also taking into account the due dates on key results. That is now fixed.

When a cycle’s status was moved to ‘Active' from ‘Scheduled’ manually, it didn’t change the status. Now fixed.

Using current month on the Roadmap view for OKRs did not accurately reflect on the screen. Resolved.

Minor issues related to custom field filtering on OKRs & User profiles.

Exporting form responses did not return responses but returned scores in some cases, now addressed.

Performance improvements in case when the browse OKRs view includes the latest comment column.