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.
Understanding the Abstain Feature in Approval Path
When it comes to decision-making, there are times when we don’t want to give a definitive “yes” or “no.” Based on our customer’s request, we have launched a new feature in Approval Path: Abstain option. This option is working on both Approval Path for Jira and Approval Path for Confluence. The term ‘abstain’ means to stay neutral in a decision. This option allows you to opt out of a vote without siding with approval or rejection, which can be useful in several situations.
API Capabilities for Approval Path
Approval Path made the approval process so much easier. Still, there are ways companies can do more to improve business efficiency and connect with other tools. With our Approval Path for Jira or Approval Path for Confluence, you can easily generate API Keys from the global setting and customize to suit customer needs. API mechanism applies same to both, but the only difference is that in Jira, approval runs in the issue context.
The Notifications Feature and How to Use Them in The Approval Path for Jira
We’d like to introduce a great feature in Approval Path for Jira & Confluence designed to streamline your approval processes: additional notifications. This feature ensures that users are promptly reminded to take action on their approval steps, enhancing efficiency and accountability within your team. Here’s how it works with the example of Approval Path for Jira and how it can be used. You have a new notification How Notifications Work With the notifications feature in Approval Path for Jira, users can send reminders through either Jira or direct email notifications.
Make Approval Path for Jira Processes Easier with Automation
Previously, Automation required technical expertise and the use of APIs. Based on the feedback of our customers, we have launched a new feature called ‘Automation’ in Approval Path for Jira, which enables us to skip semi-tech steps to set it up. With just a few clicks, we can save your time and reduce human errors by using Automation feature! Automation step for Approval Path Introducing new features of Automation The newly added Automation step can be performed at the definition level, which means specific automation settings can be applied to any kind of project as long as rule applies to the project.
A quick Overview of PDF Export for Jira
PDF Export for Jira Efficiently sharing information from Jira is essential for maintaining clear communication and seamless project management. PDF Export for Jira addresses this need by enabling users to share their tickets in a signed PDF format. Whether you’re updating a client on project progress or preparing for a compliance audit, PDF Export for Jira ensures that all ticket details, including comments and history, are captured securely and comprehensively.
Approval Path for Jira vs Herzum Approval
For people running or being a part of a project, especially a bigger one, it’s obvious that each project is a multi-step process. Each step often requires approval (or various approvals) before proceeding to the next one. For example, when an advertising agency is preparing a campaign for a customer before graphic designers can create visualizations, concepts must be proposed, selected, and approved by the creative team, project manager, and client.
JES - Our Brand Hero
You may have noticed that we had a new friend among our ranks for the last few months. You may have seen him on our LinkedIn, in our extensions or during the events. His name is JES and he’s our dynamic robot mascot. With lightning speed and precision, JES embodies efficiency and agility, always ready to assist as your faithful companion in the digital realm. JES symbolizes collaboration, effortlessly integrating into workflows to streamline processes and deliver optimal results.
Enhancing Bug Reporting to External Developers with External Share for Jira
Today in JES’s Factory things are not going smoothly. The CNC machines have a hard time communicating with the server after a recent software update. The developers can’t figure out the issue on the Factory’s end, so the only option is to get in touch with the hardware company. Fortunately for them, the CNC provider uses External Share for Jira to swiftly communicate such issues. The Factory can report and fix issues faster by using a secured link with the JES Factory developers, bypassing the customer portal and waiting for a CS representative to create an issue.
Streamlined Financial Approvals in Jira
In the financial sector, where precision and compliance are paramount, approval processes have often been the bottleneck, stalling financial transactions. Enter Approval Path: the Jira extension transforms the cumbersome task of obtaining financial approvals into a streamlined, transparent, and swift process. The Challenge of Timely Approvals Imagine a scenario where a finance team is scrambling to get an unbudgeted software update approved. In a traditional setting, this would involve a series of emails, manual tracking of approvals, and constant follow-ups, leading to an agonizing wait - sometimes days - for a green light.
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.
Conditionals Feature in Approval Path
The new Conditions feature for improving workflow and approval management is here! The introduction of conditional approvals in Approval Path opens up a world of possibilities for project management. By integrating the power of Jira expressions and the Jira REST API, this feature offers a dynamic, adaptable approach to project management that fits perfectly with your unique operational needs. Tailored Approvals for Every Scenario The Conditions feature in Jira allows for a high level of customization in managing project workflows.
Reflecting on Our Platinum Journey: A Blend of Pride and Perspective
As we celebrate our ascent to Platinum Marketplace Partner status within the Atlassian ecosystem, the moment is ripe for both recognition and reflection. This milestone is a testament to our relentless pursuit of excellence and innovation in enhancing the Atlassian ecosystem. “Looking at the efforts our company invests in developing products that enhance Atlassian systems, we take pride in achieving the esteemed status of Platinum Marketplace Partner.” shares Kamil, one of our Founders.
Delegate your approval steps in Approval Path
Approval Path for Jira: Elevate Your Approval Game Gone are the days when Jira’s built-in approvals left you wanting for more. With the new feature for the Approval Path Jira extension, the approval process is now streamlined, intuitive, and packed with features that will redefine how you manage approvals in your projects. What’s New? The Delegation Feature! Picture this: You’re on vacation, but an important approval awaits your nod. With the Delegation feature, you can now delegate your approval responsibilities to another user.
Sharing Without Oversharing: Tailored Transparency for External Boards
Table of Contents Before We Dive In Configuring the Board to Exclude Backlog Adding Their Issues to the Active Board Scrum Board Automation Kanban Board Automation Conclusion Additional Resources Connect with Us on LinkedIn In the realm of agile collaboration, the devil is in the details. Balancing transparency with privacy is akin to a tightrope walk. Walk it with confidence. With External Share for Jira, we ensure that external collaborators see only the active tasks and their contributions, keeping the backlog discreetly tucked away in the shadows.
Introducing The New Issue Creation Update for External Share
In the world of project management, collaboration is crucial. Every day we face new challenges and issues we need to overcome. Now it’s easier for your external collaborators to communicate them to your team. We’re excited to present the latest enhancement to the External Share for Jira: the Issue Creation update. This update enables external users to create new issues on shared boards, timelines and filters, streamlining collaboration and project success.
Boost Team Collaboration with Jira's Smart Checklist + External Share Integration
“Coming together is a beginning, staying together is progress, and working together is success.” Henry Ford Effective teamwork and collaboration lie at the heart of any successful project. Acknowledging this truth, the tools available in the Jira ecosystem continuously evolve, providing new opportunities for seamless collaboration. Today, we are focusing on a particularly exciting development: the integration between Smart Checklist and External Share. This powerful combination is set to transform the way teams work together.
Mastering the Art of Selective Sharing
Sharing made simple: exclude content with ease Hey there, fellow Confluence enthusiasts! Do you ever find yourself needing to share a Confluence page with someone outside your organization, but there’s just that one piece of sensitive information you’d rather keep under wraps? Well, fear not! Today, we’re diving into the magical world of the “exclude content macro” in the External Share for Confluence add-on. Get ready to become a selective sharing maestro!
Enhance collaboration with External Share's Timeline Share feature
Collaboration is the key to success, and Timelines are the key to collaboration. Hey there, are you struggling to collaborate with your clients and partners on Jira Timelines? Well, fret not, my friend! Let me introduce you to Timeline Share, the newly introduced feature to External Share, the ultimate feature that enables Jira users to share their Timelines with external stakeholders without breaking a sweat. Create and Customize Timeline Share operates differently from your standard share feature.
Popular Confluence Macros That External Users Can See
Atlassian’s new public links feature lets you create a special URL directing to a safe, read-only version of a Confluence page, and share it with someone who doesn’t have a Confluence license. It’s similar to our Atlassian Marketplace app, External Share for Confluence, except its functionality and security options are much more limited. One big functionality limit with the native links feature is that you can’t share many of Atlassian’s own Confluence macros, and you can’t share *any *3rd party macros.
Making Sure Your E-signatures Are Legal Worldwide
Electronic signatures were in use long before the pandemic, and their legal standing has been defined in various statutes since around 2000. But they used to be a strategic asset: a flexible, fast, green, international relations booster. Then the lockdowns happened, wet ink signatures became unworkable, and e-signatures turned from an asset into a necessity. A survey of US business owners and individuals by airSlate showed that the use of e-signatures among businesses surged by 50% during 2020.
Approval Path start parametrization
It’s about convenience and more! What is parametrization? In this context, parametrization is a rather fresh feature of Approval Path, and we think it could boost user experience a lot! Well, at least for users that use Approval Path more excessively. Here is why! Functionalities Parametrization will allow you to re-use an existing path (definition) while you conveniently rename the approval just before you start it! Also it allows you to set expiry dates.
Jira projects templates
Jira is one of the most popular issue tracking and project management software. When released in 2002, it was designed as an issue tracking platform for software developers. It has become more popular, so Atlassian expanded the Jira platform and gave users a choice between Jira Software, Jira Work Management and Jira Service Management. Each product is targeted at a different group. Jira Work Management is aimed at non-technical teams. Jira Software is designed for software teams: developers, QA, scrum masters, project managers, etc.
Multiple approvals
You asked, we care, we listen and now we deliver! The time has come yet again for a new feature! A feature YOU asked for! If you are using the Approval Path, you have likely considered this feature at some point in your experience. Why can’t I just run multiple paths instead of only one?🤔 Well, that is no longer the case! What is Approval Path and why it matter?
Permission flexibility!?
We have a new and rather EXITING update!!! (on both Jira and Confluence) We’ve been working around the concept of approval path for quite some time, if you are a user of Approval Path, you probably work in an environment where permission hierarchies play a role, hence the need of approvals! So, what’s the update and how can it improve your experience!?! Permission schemes That’s right!!! You can now limit or extend the access of users to approval path capabilities, you can create more flexibility around the approval path by allowing more users to interact with the path or you may wish to limit access restrictions further to have a more focused group of users handle the approvals.
Add Signatures to Jira Issues with the New E-Signature App
Jira issues just got a LOT more exciting. These already awesome little tools for assigning and tracking work can now be transformed into quick legal contracts in a few clicks. Warsaw Dynamics’ newest app, Contract Signatures for Jira, makes it possible for internal and external users to add their signature to a Jira issue and formalize their agreement to the work described in it. And yes, you heard right. It’s possible for internal AND external users to sign Jira issues.
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.
How to Share Your Jira Agile Board with External Users
There’ll be times when you want to share a bunch of Jira issues externally without buying extra licenses. Maybe you’re working on a project with an external partner or contractor that has multiple issues requiring the external user’s attention. External Share for Jiraallows you to give external users secure, temporary access to those issues in three ways: Create External Share links to each issue individually Create an External Share link to a list of issues using Jira Query Language (JQL) Create an External Share link to an entire Scrum or Kanban board If you have a lot of issues to share, you probably don’t want to go down route one.
Custom Domains for Confluence and Jira: The Ultimate Workaround to End Your CLOUD-6999 Woes
The Atlassian Community has been hankering after custom domains for Confluence and Jira for absolute yonks. It’s difficult to offer continuity of service – not to mention disorienting for the customer – when you’re directing them to a website that’s not your company’s in order to view your resources and documentation. You’ve probably heard of the famous CLOUD-6999 Jira ticket. Behind it lies a tale of woe and despair. This simple request for custom domains for Atlassian Cloud products has been languishing in Atlassian’s backlog for so long it’s become a meme and sparked a range of merchandise.
Example uses of the approval process
With the growth of the company, comes a moment when standardization of the approval process becomes necessary. It could be a moment, when different people are responsible for the decision and realisation, or when reaching each approver becomes too time-consuming. The approval process can be carried out in an outdated way - with emails, PDFs, Word documents, or at worst, on paper… But luckily we can use approval management apps like Approval Path for Jira and Approval Path for Confluence to improve the process.
Approval Path vs Build-in Jira Approval solution
Jira’s only built-in functionality to set up an approval process is in the Jira Service Management. Approvals in Jira Service Management are associated with the workflow. While this is useful, it also creates some limitations. In this article, we will look into the differences between the approval processes in the Approval Path and in the Jira Service Management Approval Path Jira Project types Any kind of project Jira Service Management Number of steps As many as needed One approval - one step Step types User, Group, Issue Field- User, Issue Field- Group, Email, Webhook User, Group Approval definitions ✔ ✘ Path visualisation Clear, legible Illegible Project types The Approval Path app allows you to run the approval in any type of issue in any type of project, unlike Jira’s native approval process which can be used only in Jira Service Management, only in issues that have approval added to a workflow.
With Automation, Dark Mode, Custom Domains & More, External Share is Basically A New App
Our team have added so many new features and improvements to External Share for Jira and Confluence over the past few months that what customers are getting now is effectively a brand new app. Let’s walk through some of the additions. Automated Share Management We would all rather be doing things that are valuable. Things that make us money. Admin tasks don’t make us money. They make usbored. This is why we’ve added a new Automated Share Management feature to External Share for Jira.
Controlling Who Sees Your External Share for Confluence and Jira Links
Companies have been asking us for a way of restricting which users can see theirExternal Share for Jira and Confluencelinks. Previously, you could create a secure link to your Confluence page or Jira issue and share it with a chosen person outside your instance. That link was always safe from a randomer on the internet finding it, thanks to its unguessable 16-character URL. It could be protected further by adding a password, making the page or issue inaccessible to anyone without it.
How to Customize your External Share Email Templates
After creating an External Share link to a Confluence page or Jira issue, there are two ways to share the link with a user outside of your instance: Copy the URL of the External Share version of the page or issue and paste it into an email or instant message. Click “Send via email”, which will send your External Share link to the email address you enter using an email template.
How to Share Jira with External Users (Securely)
As Jira grows ever more ubiquitous, it’s increasingly necessary for larger and more diverse groups to communicate and collaborate on projects in real-time. The ancients’ rituals of emailing screenshots are embarrassingly outdated for software-enabled teams that bought Jira to avoid email-chain siloes and the disheartening disaster of discovering efforts have been duplicated due to a lack of real-time project management. Fear not! There are three options for collaborating securely with external users in Jira:
How to manage approvals in Jira – a step-by-step guide
Approvals in Jira have become as necessary as workflows and boards. This is thanks to increasing adoption among business teams like HR, operations, legal, and procurement, for whom approvals are an everyday function. And yet, there is no native functionality for approval management in Jira itself (apart from in Jira Service Management, and it’s not very good). This is why we have built Approval Path for Jira, an app that lets you create as many project-specific templates for approving a piece of work as you like.
Approval management is the missing piece of the Jira toolset
Approval Path for Jira Native Jira’s only approval management functionality is in Jira Service Management (JSM), and we’re being kind when we say it’s, urm, not the best. In Jira Software and Jira Work Management (JWM), a workaround is your only option for getting a process, proposal, or purchase approved within Jira. And yet, it’s something users are frequently asking for help with on the Atlassian community, specifically, how to add an approval step to a Jira Software or JWM project.
Wanna See Some More? Now Your External Users Can Become Watchers on Jira Issues
A new feature has just launched in the cloud version of our External Share for Jira app. We call it ‘External Watch’. External Watch lets your external users subscribe to the issues you’ve given them access to. That’s good for them because it saves them time. It’s good for you because it makes collaboration more immediate so that work can progress faster. For the uninitiated, External Share for Jira gives external users secure, temporary access to a live Jira issue by generating unique links with optional passwords and time limits, and easy-to-specify permissions.
External Share for Jira
External Share for Jira Share live links to your Jira issues and boards – with whoever you like Save on Jira license costs There are no “guest users” in Jira. Any collaborator from another organization will consume a Jira license, and you don’t want to buy a whole license if you’re only sharing the odd issue from time to time. Enter External Share, an Atlassian Marketplace app that lets you share secure links to live Jira issues with people who aren’t on your instance, such as partners, contractors, and customers.
Contract Signature for Jira
Contract signatures for Jira Say yes faster You shouldn’t have to leave Jira to agree or approve work. And now you don’t have to. Available on Cloud View in marketplace Get approvals from internal or external parties Turn Jira issues into quick contracts for work Everything’s recorded and tracked Try it now E-signatures for your Jira issues Jira issues transformed into signable contracts Automated emails to all parties, prompting action External parties can sign issues without a Jira license Status markers on the contract as it goes through the signing process Signees can reject a contract PDF and HTML versions of signed Jira issues automatically sent to all parties Audit certificate sent to all parties Link to verify the authenticity of the signed contract version of the Jira issue Audit trail created in Jira Sign with your smartphone Your single source of truth for approvals Approval functionality is Jira’s missing piece