Approval Path Approval Path for Confluence Approval Path for Jira Company Contract Signatures Contract Signatures for Confluence Contract Signatures for Jira External Share External Share for Confluence External Share for Jira JES PDF Export PDF Export for Jira Warsaw Dynamics
Feature
Keep External Stakeholders Updated: External Share for Jira
Keep External Stakeholders Updated: External Share for Jira When working with clients or third parties who don’t have direct access to your Jira workspace, it’s important to be transparent about project progress. However, it’s also crucial to protect the sensitive information. With External Share for Jira, you can securely share updates and manage access for external stakeholders. We would like to introduce some helpful features, including Exclude Content Macro, setting up Single Sign-On (SSO), configuring a custom domain, and sharing project boards.
Introducing Success & Rejection Steps
Introducing Success & Rejection Steps At Warsaw Dynamics, we are continually refining Approval Path based on our customers’ feedback, so we can make their workflow flawless. We have introduced Rejection Step previously, and now we have released the Success Step for both Approval Path for Jira and Confluence. In this post, we will explain what these steps are, with some use cases, showing you how they can help Approval Path process more efficiently based on the application version for Jira.
How-to: create your own financial approval with the Conditional feature
The Conditionals feature for the Approval Path creates many possibilities for more complex automation. With it, you can control processes without wasting time and energy analyzing what should happen next. You can set it up once and forget about manual management of approvals. One of the setups we know is often used is financial approval. Let’s look at a scenario: The marketing team needs a new camera and photo editing software budget.
Navigating Feature Deployment with Approval Path for Jira
OrbTech, a hypothetical mid-sized tech company, is deploying a new feature. The recent development of a new functionality takes many steps and requires cooperation from multiple departments. Let’s dive into their journey, highlighting how the Approval Path for Jira played a pivotal role. Creating the feature Maya, the dev lead, initiates the first approval request using Approval Path within their Jira system to ensure the new feature meets OrbTech’s initial standards and requirements.
Approval path with external user participation
Usually, an approval process takes place within the organisation. However, in some cases, a decision from someone outside your Jira or Confluence is needed. There is no point in adding this user to your instance when there is an easier and faster solution provided by the Approval Path apps, which is the email step. All you need is a decisive person’s email address, on which will be sent a call for action message.
Big update pack
We are constantly developing our apps to make them more useful. Lately, we added some improvements to the Approval Path for Jira and the Approval Path for Confluence. Let’s walk through some of them. Parallel group In response to customer requests, we added the parallel group to both the Approval Path for Jira and the Approval Path for Confluence. It allows all users added to the group to approve or reject parallelly.