Tag Archives: JIRA

Our new use case and app library for Atlassian apps

//SEIBERT/MEDIA's Atlassian app use case library

The Atlassian Marketplace is huge. There are hundreds of developers offering thousands of apps on the platform for all imaginable scenarios. And finding the right solution on it is not so simple when it comes to specific problems and applications. To provide you with an overview, we have selected and compiled well-developed app solutions for use cases which customers always ask us about. The result is the new use case library in our knowledge base.

Power Scripts for Jira: Automation and optimization made easy

With scripts, you can extensively customize Jira (screens, custom fields, and more), automate complex workflows, create custom listeners to react to specific events, and enhance Jira’s reporting and integration capabilities. However, many scripting apps that plug into Jira don’t give you access to the full API, or use horribly complex scripting languages. But Power Scripts for Jira makes scripting easy.

Atlassian Will Increase License Fees for Server Products from 2 October 2017

Atlassian price increase - invitation from Bastian Schmitt and //SEIBERT/MEDIA

From 2 October 2017, Atlassian will increase their license fees for their server product line by an average of around 10 percent. This price adjustment covers both initial licenses and support extensions for server products. Here are your options!

Good Emails, Bad Emails

Email continues to be the main medium for digital communication in many companies, and at the same time is one of the biggest time wasters and productivity killers. Email is fast, convenient, and normal – and is often abused to a greater degree than any other digital communications technology.

One of the biggest problems is that email communication is frequently ‘unofficial’, as the contents are not centrally documented, transparent, and available to the entire organization. This does not mean that I want to condemn email as a whole – there are good and bad emails.

JIRA Tickets or Confluence Tasks: What Makes More Sense?

Confluence tasks - An example

In JIRA, companies manage their projects, epics, user stories and detailed tasks. Requirements are translated into concrete tickets that can be assigned and processed. Dependencies are shown here. Project progress is measured and evaluated with JIRA.

Confluence has also had tasks and tasks lists for several years. On this topic, someone contacted us a while ago on Twitter:

I wonder when you should use Confluence’s task lists instead of JIRA?