Although this demonstration was from several years go, it is still relevant today. And in fact, Atlassian’s expanded tool suite have only been more tightly integrated! Atlassian’s tools ensure they work well together, achieving a seamless integration of ticket and tracking systems, continuous integration servers and repository management systems.
Back in 2014, we hosted Jens Schumacher, then the group product manager for Atlassian’s development tools in Sydney for a few days. We captured this demonstration where he showed us how Jira, Stash and Bamboo work together – from issues to branches, pull requests and tests, to a successful quality-checked release of a change made to the main code base.
Let’s have a look at how Atlassian’s tools were integrated all those years ago!
In addition to an introduction, we believe it would be useful to actively exchange information with the existing community. So, last November we organized a community and user meetup for ERPNext at our head office in Wiesbaden, and were delighted to host Rushabh Mehta, the founder of ERPNext.
There are quite a few intranet systems that include native instant messenger solutions with integrated chat functions. At first glance, an all-in-one package like this might seem attractive. But looking a bit more closely, it might not be such a good idea.
It is clear there is only so much synchronous communication a person can participate in. There is a natural limit to the amount of time you can spend coordinating with others in real-time, and ultimately, the rhythm of your workday defines the upper limit. In this post, we look at how to make active and conscious choices on when synchronous communication is effective and when it’s not.
Collaboration with partners is an important factor in the continuous development and improvement of our products. Here is a video interview with Brandon Huff from one such partner company, cPrime – a leading Atlassian expert. We talk about our software solution for the implementation of SAFe with Atlassian tools – Agile Hive – its potential from the viewpoint of a US partner, regional differences in scaling agile methods, the importance of comprehensive software integration, among other things.
In this post, we look at the prioritization process used by Atlassian to determine when a new feature will be released for which of its two deployment options – Data Center and Server. We consider the criteria used in the decision-making process to make the decisions more transparent and understandable for customers.
The end-of-support dates for Atlassian’s IM and group chat products HipChat and Stride have been announced as well as a new strategic partnership with Slack, a previous competitor in the IM and group chat market.
We were delighted to have the opportunity to interview Nick Muldoon and Teagan Harbridge from Easy Agile about two very useful Jira apps, as well as the GDPR and other very topical issues in the technology sector.
A modern, collaborative social intranet to replace a classic, static intranet brings many changes with it but also presupposes a number of changes to ensure its success. One key aspect is transparency as actively fostered by Atlassian Confluence and Linchpin.
With //SEIBERT/MEDIA’s support, the “We, RoBITs” team has had great success in qualifying for the World Robot Olympiad final!