Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview 

The Wittified Product Team is excited to release version 2.0 allowed the administrator to enable more of their trusted power users to manage their own project configurations and free up their time to focusing on scaling the system. With 2.1 we're helping to enable the power users to group project configurations together and free up their time to do other more important stuff outside of Jira.

With 2.1 Wittified is excited to share 2 new features: Project Groups and Locking Mechanisms.

...

.1 of Delegated Project Admin Pro for Jira. Based on feedback from some of our amazing customers, this release is all about enabling trusted users to manage multiple projects more efficiently and consistently, which saves time and ensures projects remain accurate and in sync.   

We made a quick video to walk through the two new features — Project Groups and Locks.

Widget Connector
width533
url https://www.youtube.com/watch?v=a680nihWjzg
height300

Release Highlights 

The 2.1 release includes two main features that make it easier to manage multiple projects' settings with efficiency and consistency. 

Project Groups

For project admins that manage multiple projects with the same settings, we've added a new feature called Project Groups to make it easier to keep all those project setting adjustments in sync. With this feature, simply add two or more projects to a Project Group and any changes made to one project's settings will be automatically applied to all projects in the group. A project can be easily added to or removed from a group and changes can be rolled back at any time. 

Locks

As part of our DataCenter and Jira at Scale support, we noticed

...

a few cases where we needed to expand the native Jira locking mechanics

...

we were relying on

...

, so we've introduced our own with Locks. These enhanced locking capabilities will ensure project settings are modified correctly and data stays in sync by allowing admins to configure Locks to temporarily prevent background processes from performing the same action at the same time. For example, if a user tries to switch the workflow scheme for a project, the Lock will only allow one "switch" per project in a given period of time. Admins can break the locks

The new looking mechanism will guard against users triggering the same action multiple times at the same time, however the administrator can at any time "break" these locks.

To ensure project settings are modified correctly and data stays in sync, we've added enhanced locking capabilities for admins. Configure Locks to temporarily prevent multiple 


For more information about these new features, see our Administrator's Guide - 2.1 and User's Guide - 2.1. To see the new version in action, upgrade now or visit the Marketplace to download the app. 

Resolved Issues 

In addition to this, we solved a couple of bugs related to Jira 7.10 compatibilityadding new features, we also resolved the following issues:

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId14c546bb-3a07-399f-9d5b-ade2eafb3ae3
keyDADMIN-425

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId14c546bb-3a07-399f-9d5b-ade2eafb3ae3
keyDADMIN-424
As well as fixed an issue where the project administrator could add the same transition multiple times:

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId14c546bb-3a07-399f-9d5b-ade2eafb3ae3
keyDADMIN-420