Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

When do you need to use permission schemes?When

  • Complex Environments and Approval Hierarchies: If your team operates in a

...

  • complex environment or

...

  • uses layered approval hierarchies,

...

  • When working with permission schemes can help you manage access and approval roles effectively.

  • Private Projects: For private projects, you might may need to limit control or allow restrict access for certain users, ensuring that only authorized personnel can view or act on specific approvals.

  • Large Projects with Extensive Issue Tracking: In a large project with a huge number of projects with numerous issues, maybe you may want to give a specific user permission grant specific permissions, such as allowing a user to delete approvals or allow the user to change modify parameters when starting a new approval so . This ensures tasks will move smoothly and efficiently.

  • Depends Organizational Compliance and Control Needs: Depending on your working organizationorganization’s structure, you may need strict access control . In this case, permission schemes help you meet compliance standardsto meet compliance standards. Permission schemes provide the necessary control to support these requirements.

However, if you are unsure about customization, Approval Path’s default permission scheme is still reliable. It provides a safe and balanced set of permissions that work well for most users.

...

Approval Path integrates with Jira Workflow. It allows global admins to manage approval processes by configuring Approval Conditions and Post-Functions in workflows. Through this feature, approvals can be efficiently handled and align with organizational processes.

...

...

Workflow Condition

In Jira Workflow, it is notable that Approval Condition prevents issues from transitioning to the next workflow status unless they have been approved. It means that whenever it’s needed, issues will go through the approval process before the next step.

As a global admin, carefully apply approval conditions to key transitions (e.g., from "In Progress" to "Done"). Make sure that the correct approval path definition is selected to avoid confusion in the approval process.

Info

Before applying these conditions, it’s nice to test in a non-production environment to see if they work as we expected. Find out more about Approval Conditions here.

...

Workflow Post-Function

Approval Post-Function automates routine tasks like starting, deleting, and archiving approvals after a transition without manual effort.

...

You can select Use the "Start Approval" post-function to automatically trigger the approval process after key status transitions. For instance, placing post-function after the “To Do” to “In Progress” transition, approval process should be started. This means approvals are always initiated on timeexample, adding it after a transition to "In Progress" will start approvals as soon as the status changes. Find out more about Approval Post-Function here.

Panel
bgColor#DEEBFF

(question) What would be the reason to use Jira Workflow rather than Automation Step?

You might want to use Automation Step to reduce manual effort and assign different procedures to each definition.

However, from an administrator's perspective, it is good to use Jira Workflow to manage the approval process of a project and control 'transitions' using conditions. Workflow provides a clear, visual image of issue progression, which helps you to understand the whole picture of it.

Depending on your specific needs, you may choose one over the other based on the operational scope. Definition automation steps operate within the specific scope of each definition, while workflow post-functions have their own scope of activity.

...

Privileges of Project Admins

...

Warsaw Dynamics adheres to strict privacy standards to protect user data. We are saving approval definitions and configuration information which includes user and group IDs, and external email addresses for notification purposes. All other data remains within Jira, ensuring minimal data retention and secure processing. The company maintains transparency and strict compliance with relevant privacy laws, providing clear policies on data retention, international data transfers, and user rights.

...

Additional information


image-20240924-171504.pngWarsaw Dynamics Official Website
image-20240924-171527.pngWarsaw Dynamics Official Support

image-20241113-152833.pngWarsaw Dynamics Youtube Channel

Expand
titleUseful Blog Posts & Documentation

[Blog Post]

[Documentation]

Expand
titleSecurity & Privacy

Privacy and Data Security Statement

EULA (End-user license agreement)

...