Delegation of permissions has long been a missing part of Jira. Today, OBSS is solving this problem with the introduction of “Keychain – Delegation for Jira”.
Jira is powerful and Jira is everywhere. It is used for all kinds of processes and it provides configuration options to set which users can see, create, edit, delete, approve, etc. But when somebody goes on vacation for two weeks, defining temporary permissions is quite cumbersome.
Most of the time, Jira permissions are hard configured into Jira workflows. Changing them requires Jira Admin to alter workflows, which is something you don’t want to do often. Even if you configure permissions through project roles or user groups, adding a new user to a role/group gives that user all the permissions that were defined through that role/group. You don’t want that either. It is also up to you to manually remove the delegates from roles/groups when the user returns from vacation.
Some organizations try to solve this by binding all actions to “assignees” on issues and simply defining automation rules to assign issues to delegates. This introduces its own problems. First, when you assign the issue to another user the original user is no longer the assignee so loses his/her permissions. Second, you have to do something to return issues to their original assignees when that person is back from vacation. These problems get worse as the numbers of users, projects, and workflows on Jira increase.
Enter, “Keychain – Delegation for Jira”…
Keychain allows any user to delegate his/her permissions to one or more users that will be valid for a given time window.
The app introduces new Jira components (workflow conditions, post functions, JQL functions, and custom fields) to your system. These components will allow your Jira admin to configure delegation points in Jira workflows, issue screens, permission & notification schemes, and even Jira Service Management Customer Portal approvals.
Jira admin makes the configuration once. After that, defining a single delegation entry will be effective all around the system.
Even better, Keychain allows you to delegate permissions in Categories. That means you can define your own categories for delegating permissions and configure Keychain Jira components according to these specific categories, then delegate permissions only in some of the categories or delegate different categories to different users.
We built Keychain to be the most comprehensive delegation solution on Jira. Instead of being a makeshift solution, Keychain integrates into the workflow and scheme infrastructure of Jira. This provides high granularity and great flexibility for delegating permissions. Of course, its use is not limited to vacations or out-of-office scenarios. You can use Keychain as part of your daily operation too.
- You don’t have to delegate every permission. The initial configuration done by the Jira admin pinpoints where and which permissions will be delegated.
- Categories allow you to delegate permissions in different categories to different users.
- You don’t have to modify workflow configurations or user roles/groups in every project every time you delegate permissions.
- You don’t have to wait for the Jira admin to define or remove delegations. Each user can define delegations for himself/herself.
- All delegations are defined with a time window. When that window expires, the delegated permissions are automatically revoked.
You can find more information about Keychain through Keychain’s Atlassian Marketplace page: https://marketplace.atlassian.com/1225037
For any further questions about Keychain, take a look at Keychain documentation or visit OBSS support portal.
