Category Archives: Jira

Ignition Sequence Start, Liftoff with Checklists for Confluence and Jira, the Ultimate Checklist App

Ignition sequence start, liftoff with Checklists for Confluence and Jira, the ultimate checklist app - thumbnail

During the Apollo 11 mission in July 1969, an error message occured. And when things go wrong in such a high-stakes mission, they can go horribly wrong. Astronauts wouldn’t be able to come back to Earth. But thanks to the fact that the ground crew had checklists to work through when the error flashed up, they knew exactly what to do. And that’s why checklists are so important. They make sure you don’t forget anything when the stakes are high.

Creative Thinking, How to Free up Your Brain’s Idea Generator with Checklists for Atlassian Confluence and Jira

Creative Thinking, How to Free up Your Brain's Idea Generator with Checklists for Atlassian Co`nfluence and Jira - thumbnail

It’s important to not fill your head with too many ideas and things to worry about, because as a Chinese legend teaches us, you can only generate fresh ideas when the “cup” of your brain is not filled to the brim already. Checklists for Confluence and Jira can help in this regard; they make sure you (and your colleagues) don’t need to memorize procedures, but can just check off items on a checklist that can be used again and again.

How Modern Cloud Software Makes Hybrid Work Models Possible

How modern Cloud software makes hybrid work models possible - cloud thumbnail

It would be premature and unwise to predict the imminent death of the physical office. Most people want to meet and interact with other people face to face, and physical constellations are where most innovations are born. However, Cloud technologies have made the entire globe a potential place to work. Companies that embrace this fact and embrace it as an opportunity are more attractive to top talent, who in turn enjoy the luxury of being highly selective in their job choices. Modern Cloud software supports Hybrid Work on three levels.

The Importance of Clear and Concise Communication in Jira and How Awesome Custom Fields Can Help

The importance of clear and concise communication in Jira and how Awesome Custom Fields can help - awesome custom fields logo

In 2011, Netflix made quite a mistake with a rebranding, which could have been prevented had they communicated properly. Which brings us to our favorite issue tracking system: Jira. This tool uses custom fields, which can be customized with Awesome Custom Fields to make sure no one ever oversees any important information, improving communication.

What Types of Checklists Teams Use and What They Expect from Checklist Tools (Spoiler: Atlassian Confluence and Jira Integration)

What Types of Checklists Teams Use and What They Expect from Checklist Tools (Spoiler: Atlassian Integration) - thumbnail

In every company, countless activities take place day in and day out that have already been processed many times in this or a similar form. And yet, in the same companies, many things go wrong. That’s why teams work with checklists. They explain how routine processes work. They map standardized processes that have been thought through beforehand so that they can subsequently be processed as efficiently and seamlessly as possible. But not all checklists are the same. And not all checklist tools are equal.

The MoSCoW Method: Intuitively Understandable Prioritizations – Also Visible in Jira

Awesome Custom Fields - thumbnail

No team can do without meaningful prioritization of its upcoming tasks and work, even if it only acts reasonably efficiently and doesn’t want to rush past the needs of customers when developing a release or project. The MoSCoW method addresses the actual importance and relevance of a feature or story to a release or project, regardless of the amount of work required.

Practical Workaround for Jira Cloud: Re-empty the Resolution Field

Practical Workaround for Jira Cloud: Re-empty the Resolution Field - thumbnail

When a task reaches its final state in Jira Cloud, its Resolution field is given a value and Jira assumes that the task’s lifecycle is over. But what if the task is reopened, perhaps because it was accidentally closed? Unfortunately, the Resolution field is not automatically cleared. A workaround based on Jira Automation from the Atlassian community provides a remedy.