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
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.
SSO Verified Domains: External Share for Confluence
In this article, we are excited to introduce a new feature in the External Share for Confluence. This feature allows you to verify a domain by adding a TXT record at the DNS level, which is generated by our tool. After verifying that the record is set correctly on the domain, we are assured that the user who set up SSO also has access to the designated domain. This allows users to skip email verification when registering with Single Sign-On (SSO).