Recently, Issue History for Jira app has transitioned to Atlassian Forge and earned the Runs on Atlassian badge. The update offers significantly enhanced app functions, particularly the data security and reliability.
In this article, we’ll explore in detail the reasons behind the migration, the changes it has brought for users, and how Forge compares to the previous Connect framework.
Atlassian is focusing on Forge platform for building cloud-based apps. It is intended to ensure that the apps are more secure, faster, and more integrated with Jira.
This is the reason why we have migrated Issue History for Jira app to Forge. It will help us follow changes and provide our customers with a more reliable experience.
Usage of Forge provides apps with several significant benefits. For example:
🔒Enhanced security. Forge apps are hosted completely on Atlassian servers. This means that all the data of the app users does not leave Atlassian Cloud.
⚡Improved performance. The apps based on Forge are faster and more stable.
✅ Approved by Atlassian. The transition to Forge and earning the Runs on Atlassian badge signifies that the Issue History for Jira app has met the most rigorous security and performance requirements set by Atlassian.
🔄 Future-proof. Atlassian will keep on improving Forge, and by migrating to it, we will be able to remain up-to-date and offer more support to our app users in the long term.
There are thousands of apps that you can find as a Jira Cloud user. Apps developed on Forge come with additional advantages that directly enhance your daily experience.
Here are the reasons why it is a good idea to pay your attention to Forge-based apps:
🔐 You do not need to worry about the security of your data. It remains completely in the Atlassian Cloud with Forge apps. No third-party servers; it simply works through default security.
🏷️ They are more trustworthy. The Runs on Atlassian badge means that the app has passed Atlassian's stringent quality, performance, and security checks.
🔄 You will have fewer compliance issues. Because data isn’t leaving Atlassian’s system, it is easier to comply with internal policies or industry standards.
📦 Easier support and updates. It is simpler to update Forge apps, and technical problems are usually solved quicker because of a closer integration with Atlassian tools.
Managing a small team or a large enterprise, you will have a more reliable, secure, and future-proof experience on Jira Cloud by selecting Forge apps. So, the next time you're looking for an app, just look out for the badge Runs on Atlassian or the Privacy & Security tab on the app page to find out whether it is running on Forge.
There are two primary platforms for developing Jira Cloud apps: Connect and Forge. Let's dive into the differences between the two.
The migration of an app to Forge does not alter the app's main functionality or the way users interact with it. The primary distinction lies behind the scenes, the way that the app is hosted, secured, and connected to Atlassian infrastructure.
As an example, having migrated to Forge, Issue History for Jira still provides the same functionality: it tracks the history of changes in Jira issues, when, and by whom, all in one place.
Users continue to enjoy the same interface and features, yet the performance is faster, the security is improved, and the operation is more stable due to the serverless architecture provided by Atlassian. Thus, the transition to Forge is significant in terms of improvements, but the user experience remains the same.
The migration to Forge is a step in the direction of more security, improved performance, and more integration with Atlassian Cloud. Although the functionality of the core app remains unchanged, Forge offers a more solid and future-proof base. To users, it is about trusting the tools that they are using day to day.
Natalia_Kovalchuk_SaaSJet_
Product Marketer
SaaSJet
2 accepted answers
0 comments