Tag Archives: //SEIBERT/MEDIA

Microblogging for Confluence: An overview of its features

Microblogging for Confluence, developed by //SEIBERT/MEDIA, is the plugin that enriches Atlassian’s social collaboration platform with seamlessly integrated Enterprise-Microblogging features. This add-on is already available on the Atlassian Marketplace: Download the alpha version for free and evaluate it in your test environment just as you like.

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.

How to properly escalate issues with Atlassian

Every company has individual needs regarding its internal systems, wants special features and finds bugs, that are unnoticed by other organisations, due to specific workflows. Atlassian listens to its customers and offers a variety of possibilities to report certain issues to the developer teams and to take forward the implementation. What you can do, if you want to escalate an issue, is shown here.

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.

The Wiki Gardener: Tasks and Requirements

The idea of a wiki gardener is outstanding. There is hardly a company that is not delighted by this principle. But only a few companys actually transform this concept systematically and successfully. In doing so, it is generally no drama to recruit a gardener internally, and entrust him regularly with appropriate work. All you have to know is what a so called wiki gnome does, and why and who fits to the job profile.

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.