14 posts tagged with "atlassian"

draw.io and our Atlassian integrations are the leading solution for web based sketching and diagramming functionality. The article describes the draw.io integrations for Confluence that we, draw.io Ltd., build, deliver and maintain alongside the online app.diagrams.net and the offline draw.io Desktop application.

Atlassian recently deprecated their Confluence Server range. As the software market evolves, accelerating the move to Cloud is the next natural step in Atlassian's strategy.

Users able to move to Cloud have seen an overall cost saving due to reduced maintenance and downtime, as well as benefiting from Atlassian's scalability and security record. There are various mechanisms in place to smooth the road to Cloud, including free Cloud licenses while you migrate away from Server.

At smaller tiers Confluence Cloud is the clear winner, at higher tiers the cost outlay is greater (excluding the benefits). You can see a comparison between Confluence Server and Confluence Cloud at various tiers below (pricing as per the July 2021 price list, annual renewal in USD):

Users	Conf Server	Conf Cloud
10	1,300	Free
25	1,300	1,250
50	3,000	2,500
100	5,500	5,000
250	10,900	12,500
500	16,400	18,500
2,000	20,100	61,000
10,000	25,200	256,000

For under 500 users, the cost is largely the same. But that isn't the whole picture, as you're likely to have apps installed, also.

Taking the top selling Confluence app, Gliffy, let's see how the price changes as you move to Cloud and compare it to draw.io on Cloud:

Users	Gliffy Server	Gliffy Cloud	draw.io Cloud
10	5	100	10
25	301	950	187.50
50	630	1,900	375
100	1,178	3,800	750
250	2,406	8,000	1,500
500	3,125	10,250	2,000
2,000	6,566	23,750	4,500
10,000	9,430	95,750	16,500

In fact, up to 4k users, you will save money on your Gliffy Server renewal by using draw.io on Confluence Cloud. With 10k users, you will pay 75% more for draw.io on Cloud compared to Gliffy on Server. However, if you have 10k users switching to Cloud and keep Gliffy, you pay over ten times (x10) the Server price.

There is a rich selection of apps in the Atlassian ecosystem and it's worth evaluating alternatives when migrating from Confluence Server to Cloud. Some apps, like draw.io with its one-click Gliffy mass importer, make it easy to switch whilst saving you money. Of course, you save that amount every year after you have switched.

Versioning is built into Confluence, and diagrams attached to pages using the draw.io app for Confluence takes advantage of this. When you edit a diagram, the draw.io app creates a new page version so you can easily restore an older version of your diagram.

If you are using draw.io for Jira Cloud, we recommend that you embed diagrams stored in your Confluence instance to take advantage of its versioning and real-time-collaboration tools.

If you are using diagrams attached to issues in Jira Server, these are now also versioned, but in a different way.

The draw.io app now adds a compressed zip file to your Jira Server issues containing multiple diagram files. When you open the attached diagram file from the right panel, you can access the revision history of your diagram via the menu.

Add a diagram to an issue on Jira Server​

Once you have installed the draw.io app into your Jira Server instance, you can create diagrams in your issues.

1. Click on More in the issue toolbar, then select Add draw.io Diagram from the menu.
   
2. The draw.io diagram editor will open. Create your diagram. When you are finished, click on the Save & Exit button in the top right.
3. Add a filename, then click Save.

Your diagram will be displayed in the right panel of the issue in the draw.io Diagrams section, and the file will appear in the Attachments section. You can immediately see which version the diagram is by the number in square brackets after the name of the file above the preview on the right.

Restore a diagram revision in draw.io​

1. Hover over the diagram preview on the right, and click on the pencil icon to edit your diagram.
   
2. In the editor, select File > Revision History from the menu to open dialog with a list of diagram versions.
   
3. Each revision shows you who modified it, and when it was modified. Click on a version to see a preview of the diagram. If you want to restore a particular version, click on it, then click Open.
   

This creates a new version of the diagram and adds it to the attached file - no changes are lost.

Tip: To delete a draw.io diagram from your Jira Server issue, hover over the diagram on the right panel of your issue and click on the trash can icon (delete).

See diagram revisions inside the attached file​

As the attached diagram is a compressed zip file containing multiple diagram files and some metadata, you can open it on your computer and look at each diagram individually. You can also open the attachment file or any of the included XML diagram files in our online draw.io editor.

1. Download the attachment to your computer and unzip it using your favourite decompression tool.
2. The most recent diagram version can be seen in the diagram folder, and older versions under the history folder.