Blogs

Introduction If you're using Jira Software's classic project setup, you're likely enjoying the features like managing your backlog, creating sprints, estimating issues, and ranking tasks. But what happens when you want to use a custom issue type and estimate it with story points?

Agile project management has revolutionized the way teams deliver high-quality work efficiently and collaboratively. JIRA, a powerful tool from Atlassian, has become a go-to solution for managing Agile projects. However, to fully harness its potential, it’s essential to understand how to use it effectively. In this blog, we’ll explore the best practices for Agile project management using JIRA to streamline your workflows and boost team productivity.

When it comes to managing projects and workflows, Jira is a widely-used tool offering powerful features for tracking tasks, bugs, and more. One of the fundamental aspects of Jira is its issue types, which act as the building blocks of project organization. Understanding these issue types can greatly enhance your team's productivity and ensure streamlined communication.

Hello everyone, and welcome to today's blog post! Recently, after returning home from some work, I decided it was the perfect time to share my thoughts and experiences on a powerful tool for Jira administrators and developers—ScriptRunner. If you follow my content, you’ll know I frequently create videos and tutorials on Jira automation, REST APIs, and other customization tips. Today, we’re diving into ScriptRunner and how it can enhance your Jira instance.

When it comes to configuring Jira for your projects, one common question arises: how many issue types should you create? The answer is not as straightforward as one might hope. However, with some thoughtful consideration, you can streamline your issue types to improve project management without overcomplicating your workflow. The Importance of Reusing Issue TypesJira provides a variety of default issue types, such as:

Capacity management is a challenging yet crucial aspect of project planning, especially when using tools like Jira. It is not just about managing resources effectively; it involves meticulous planning, tracking, and adjusting to ensure successful project delivery. Here, we explore the intricacies of capacity management in Jira, using real-world examples to highlight its complexity and best practices. 

Jira offers extensive customization options that help tailor workflows to your team's needs. Two commonly used features are Validators and Conditions. While they may seem similar, they serve distinct purposes. Let’s explore when to use each and how they can enhance your Jira workflows.

Introduction In this blog, we’ll discuss the roles of Jira Admins and Jira Consultants. Whether you're making hiring decisions or transitioning from one role to the other, this post should provide valuable insights. The Role of a Jira Admin Jira Admins are primarily responsible for customizing and configuring the Jira instance. Their tasks include setting up projects, maintaining the health of Jira, and making necessary configurations such as workflows, fields, and issue types. These are critical for ensuring the tool functions efficiently.

Sparxsys is doing good, we have regular work coming in and we are growing our team. We are now more than 10 people in our team and we operate from India and the UK. We are currently hiring a Jira Consultant and developer. Reach out to me on Linkedin.I could have written a long job description in this post but let me try to share the key things.

We have been doing Atlassian Consultation for almost two decades now and we must admit that not all consultations are 100% successful or go as planned. To be honest it is fine.We recently started sharing those Failed Consultations in this playlist.