If measures for quality assurance and both internal and customer projects don’t run ideally and thus inefficiently, it is often due to a lack of established and binding workflows in task management. This article focuses on the use of JIRA and shows how JIRA can be used to convert all kinds of tasks into systematic and transparent procedures with the help of prototypical workflows. //SEIBERT/MEDIA is happy to provide you a JIRA test instance free of charge and without commitment, so you can learn about the following workflows and the diverse functions of JIRA.
Tag Archives: Jira
Real integration: The interaction of JIRA, Stash and Bamboo
During the most recent meeting of the Atlassian Enterprise Clubs by //SEIBERT/MEDIA, Jens Schumacher, the Group Product Manager of Atlassian Dev-Tools in Sydney, was our guest for a couple of days. In an interview, he directly demonstrates the close links between JIRA, Stash and Bamboo – from issues over branches, pull-requests and tests until the successful, quality assured shipment of a change in the main codebase.
Are Trello and Basecamp Jira Alternatives?
In this video podcast, Martin Seibert and Alex Boerger discuss Trello and Basecamp as JIRA alternatives in the enterprise. In the beginning, they give a brief introduction and overview of the functionality and best practice of each product. The discussion shows that each product has its own market and the usage depends on your use case. If you are a small team of up to 5 people, Basecamp and Trello might be a good choice. But for bigger companies, with different and more complex projects, JIRA is the only way to make you happy.
Atlassian tools used for internal organization at //SEIBERT/MEDIA: Confluence, JIRA, HipChat
//SEIBERT/MEDIA is one of the biggest Atlassian Experts Partners worldwide. And of course we intensely use Atlassian tools for our internal organization. In the following video our colleagues Martin Seibert and Alex Boerger demonstrate first conceptual and later directly in the system what roles Confluence, JIRA and HipChat play in our digital communication, how the tools are connected to each other and how they support coordination, teamwork and productivity.
Professional diagrams in Confluence & JIRA with draw.io – Interview with David Benson
draw.io is the leading diagramming plugin for Confluence and JIRA. draw.io enables you to collaborate seamlessly in creating diagrams that aid the communication of information in both Confluence pages and JIRA issues.
New pricing model for Jira Service Desk 2.0
Atlassian has responded to the feedback on its previous JIRA Service Desk pricing model. The pricing has changed to agent-based pricing plus the required JIRA user tier. Get started with three agents for $10/month. Teams with more than three agents pay $25 per agent per month. Each agent can serve unlimited customers. Whether you serve 100 or 100,000, customers are free.
Jira Agile 6.6 – Now available
The newest release of JIRA Agile provides richer data during the planning process by making agile cards more customisable than ever before. Read more about the new features in this post.
Tutorial: How to Create and Configure a Jira Project
In this video tutorial we will show you how you can create and configure a new JIRA Project. For an easy start, you should begin as simply as possible, thats why we chose the ‘Simple Issue Tracking’ as an example. To make sure that you have an uncomplicated JIRA experience, we will also give you a brief introduction in the different roles, permissions and the use of schemes.
Factors for the Success of Wikis 2: Organization is the Key
From dozens of enterprise Wiki projects, we know that the successful introduction of a Wiki into a company typically depends on three factors: technology; organization; and culture. In the first of these three articles we focused on the requirements of technology. This report will now focus on the organizational factors for a promising Wiki project.
Factors for the Success of Wikis 1: Technology is important, but not King
An enterprise Wiki is not only a new technology for many employees (at least within the company environment); it also requires a change in the normal communication- and collaboration patterns throughout the entire company. Through our experiences with dozens of company Wiki projects, we know that the successful introduction of a Wiki usually depends upon three factors: technology; organization; and culture. This article – the first of three articles on this topic – is dedicated to the challenges of technology.