How to Manage Product Feedback in Jira

August 31, 2023
12 min

For a product manager, dealing with customer feedback is essential for driving product success. However, managing feature requests from different teams and channels can be overwhelming. This article explores how Jira can be transformed into more than a bug-tracking tool, becoming a solid foundation for product feedback management.

Collecting Feedback in Jira

Imagine the feedback management journey as follows:

Feedback Collection → Centralized Storage → Categorization → Prioritization → Validation → Implementation.

The first crucial step in this journey is collecting customer feedback. Jira offers several ways of doing this.

Jira Issue Collector

The Jira Issue Collector is a feedback collection form that can be embedded on a website page using HTML. It allows users to submit feedback directly to Jira without logging in or navigating the Jira platform. This method is particularly useful for gathering feedback from external users or customers who may not be familiar with Jira.

Jira Issue Collector for gathering feedback

Jira Service Management

Jira Service Management (JSM) is a well-known solution for working with customer support requests. But did you know it can also be a powerful tool for managing customer feedback? Let’s explore how you can leverage this functionality.

  1. Kickstart the process by creating the Jira Service Management project.
  2. Define a specific issue type or use the default feature suggestion types.
    Jira Service Management for feedback
  3. Assign feature suggestion types to a separate queue. This makes categorizing and filtering feedback a breeze.
    Jira Service Management queue for feature suggestion
  4. Tailor the workflow to mirror feedback management stages such as “Submitted,” “Under Review,” “In Progress,” “Planned,” “Completed,” and “Declined.”
  5. Finally, set up the Jira automation rules. Automate duplication of issues in Jira Software for delivery when a feature suggestion enters the “In Progress” stage. Or close linked ideas when feature delivery is completed.
    Jira Automations for product feedback

If you’re eager to learn more about setting up Jira Service Management, the Atlassian website is a treasure trove of information.

Customer Case for Jira Cloud

Sometimes, it’s inconvenient to mix product and service requests within one Jira project. Feedback requests, after all, necessitate their own workflow, handling processes, and a team to address them. Moreover, this approach inadvertently leads to extra JSM agent licenses.

Customer Case for Jira Cloud allows creating a feedback portal from any Jira Cloud project, which helps to keep product ideas backlog separate from a support one. Unlike the solutions mentioned, all the ideas on a feedback portal are visible to all visitors. They can comment on ideas, vote for them, add new ones, and engage with other users about their use cases, thereby forming a user community.
Customer Case for Jira Cloud

What’s more, the feedback forum can be used seamlessly with Jira Service Management. Simply map the Customer Case portal to the external resources in your service project to make it visible to your customers.
Related Resourses Jira Service Management
Read more about use cases with Jira Service Management and Customer Case.

One of the standout features of the Customer Case app is that even stakeholders without Jira licenses can post and act on feedback in Jira via the portal or track the progress of a project by filtering ideas by status.
Customer portal for Jira Cloud

Best Practices for Storing Omnichannel Product Feedback

Once you’ve decided on the tools for feedback collection, the next step is to make centralized storage. Having all feedback in one place makes it easy for the entire team to access and reference it. This reduces the chances of feedback getting lost or overlooked.


Slack might not be specifically designed for storing feedback, but it is certainly a powerful ally in this task.

Establish a channel dedicated to feedback, for example, #product-feedback or #feature-requests. If your customer-facing team members share all the valuable feedback in this space, you’ll never lose a single nugget of insight from customer interactions.

Slack can be integrated with Jira to convert Slack messages into Jira tickets. It simplifies capturing feedback and ensures it is logged and tracked in Jira. 


While Slack is about immediate feedback and real-time conversations, Confluence shines in structuring and organizing feedback. Confluence offers spaces, pages, and templates, which allow you to categorize and store feedback for easy retrieval. You can also integrate Confluence with Jira to link feedback directly to development tasks.
Confluence for feedback management

Go further and connect project documentation and resources in Confluence with Jira using the Project Pages feature. Project Pages can be linked to related pages, documents, or external tools, creating a cohesive knowledge ecosystem right in Jira. It means you don’t need to leave Jira to access project docs.
Jira Service Management Project Pages


Miro is a collaboration platform that allows for the visualization of complex ideas through diagrams, wireframes, and mind maps.
Miro feedback collection

With Miro, you can create a feedback board with idea cards to capture customer feedback, including the creator’s information, idea description, attachments, and other relevant details.
Miro board for customer feedback

Then, share the board with customers to allow them to comment, react, and engage in the feedback process.

Miro’s integration with Jira provides a smooth transition between the two platforms. Ideas chosen for implementation can directly link to Jira tickets from Miro, giving developers immediate access to the necessary context and simplifying the development process.

Here we go again: Jira

If all the ideas eventually end up in Jira for development, why not adopt it as a hub for omnichannel feedback? Here are a few reasons for that:

  • Seamless Workflow: No need to switch between other feedback solutions and Jira. The entire feedback workflow, from collection to implementation, can be managed within Jira.
  • Integration with devtools: Jira allows linking feedback to code changes and ensuring the development process is aligned with feature requirements.
  • Jira Automations: Swiftly categorize and respond to customer feedback, follow up with customers, and even generate insightful reports to identify emerging feedback trends.

💡A good practice is to dedicate Jira Product Discovery to collecting all ideas and feature requests. Make a deal with a team to feed all the user stories and hypotheses into the Jira Product Discovery project. Then, collaborate, prioritize, and build a roadmap for validated ideas.

Each tool mentioned is perfectly capable of handling omnichannel feedback. But we believe when they work together, each one contributing at the right stage, it creates a more effective and cohesive workflow for managing product feedback.

Recap on Product Feedback Management in Jira

While our focus has been primarily on gathering and storing feedback, we did touch on the potential of some tools that could streamline further stages. Understanding the strength of each, we can recommend the following workflow for feedback management in Jira:

  1. Use Jira Issue Collector, Jira Service Management, or the Customer Case app to collect customer feedback directly. Or combine these channels.
  2. Adopt Slack to streamline idea-sharing across your company.
  3. Use Jira as centralized storage for omnichannel product feedback.
  4. Use Miro boards to convey complex ideas and link them to Jira issues.
  5. Take advantage of Jira Product Discovery to prioritize and validate collected feedback.
  6. Connect Jira Software to Confluence with the Project Pages feature to provide context for development.
  7. When it’s time to bring those validated ideas to life, Jira Software is here and all set.

Best Practices for Organizing a Jira Issue

August 8, 2023
#Document management#How To#Jira
8 min

Atlassian Jira Software is a global solution. Thousands of people use it at work, creating many tasks daily. For many teams, Jira dashboard is a place to start their day and to look at in the evening. In this blog post, we share the best practices for creating a Jira issue and organizing projects in Jira.

Tune up your Jira project

Have you ever wondered how much time we spend on creating issues or finding missing information? We aim to be more and more effective. That’s why companies are looking for techniques and solutions to optimize the process of working with issues in Jira and minimize team efforts.

When you start with your Jira project, you can enter additional descriptions of Jira fields, components, and workflow states. This action is not required. Many admins would tend to skip it to save time. However, you can lose many more in the long run.

Setting detailed descriptions where possible in Jira, you can minimize your team’s onboarding with the project later. This way, you help users understand the rules and specifics of this particular field, saving your team’s time in a long perspective. So try not to get tempted by one-minute benefits and stick to best practices instead.

Add links and references

Jira itself is a great solution for project management. With proper organization and description, working with Jira issues can be easy.

You can facilitate the team workflow with the help of additional informational resources. Jira allows us to do it in a moment in a few ways.

Add project shortcuts

All additional data is beneficial. Is it true? Well, almost. The truth is we are pressed with time and have limited resources to study all the information we face daily. So think twice before adding another link to your Jira issue.

For data used regularly by many team members, Jira has project shortcuts. You can add links to the team space in Confluence, Bitbucket repository, or project website here. Whatever matters most for your team in this project and lives outside Jira fits well in Jira shortcuts.

Add project shortcuts

Link to Confluence pages

Confluence is another Atlassian product that synchronizes with Jira easily. You can create a knowledge base with detailed instructions, records, and tutorials in Confluence and reuse it in your Jira project. This way, you get well-structured documentation that is reader-friendly. At the same time, you avoid duplicating information by linking Confluence pages to Jira issues instead of copy-pasting information.

Connect several Jira issues

Your projects will look much more organized if you link related Jira issues. For example, your team can have many tasks to do, and one task requires another to be done in advance. You can simply specify it in the Jira description. The problem is you can miss this information while browsing across the project.

In Jira, you can link issues and identify their relations. After that, everyone will see the association between two existing issues on either the same or different Jira instances.

Connect several Jira issues

Issue linking allows you to indicate different connections. For example:

  • An issue may relate to another.
  • An issue may duplicate another.
  • An issue may block another.

Jira has default relations for issues, but Jira administrators can customize them to fit the project better. This functionality makes issue linking flexible.

Add files to Jira issues

Sometimes you may need to add files directly to Jira issues instead of including links. Jira allows you to store files and documents related to tasks and always have them at hand.

By default, you can attach files up to 10 MB, but your Jira administrator can update these settings. All attachments will appear in the corresponding Jira issue in one list.

The out-of-the-box Jira capabilities can be handy, but not for every case. Here comes the Atlassian Marketplace. Lots of vendors offer their apps for almost every possible challenge. The same is true for working with documents. Just type the word “Attachments” in the search field on the Atlassian Marketplace, and you instantly get an advanced solution for file management in your Jira issues.

Smart Attachments for Jira

With Smart Attachments for Jira, you can perform more complex operations on files in your Jira. The app has lots of functionality for various business types.

With Smart Attachments, you can create categories for different file types and locate them in your issue faster. You can select any category name based on your project specifics. For example, it can be categories named after the attachment type (i.e., screenshots, designs, videos, etc.) or the review stage (i.e., draft, work started, ready for review, approved, requires work). For more complex cases, you can add access restrictions based on user groups or project roles. This way, your teammates get a well-structured file system within Jira, and project leads can be sure that sensible documents can be viewed or modified by relevant people only.

Create categories for different file types


Jira Software provides multiple ways for project organization. Consider adding shortcuts, links, knowledge base, and attaching files to ensure your team’s productivity. If you work with many files in your Jira project, Smart Attachments for Jira will help you organize them. Still, you are to choose what’s best for your business.

Why Jira is Hard for Product People

June 20, 2023
15 min

Jira is a part of almost every product manager’s daily life. But rumor has it Jira is hard for them.  To dig deeper, we’ve surveyed more than 20 product people worldwide. In this article, we share the most common pain points with Jira and suggest solutions to optimize product work with it.

How Product Managers Use Jira 

It’s easy to accept that no two сompanies are alike, and the same goes for the Jira instances. You don’t need to look too closely to spot the differences between two projects in the same instance. Despite that, you can easily find product managers who use Jira to:

  • Write and update epics, stories, and other issues that define the work to be done.
  • Plan upcoming sprints or work phases – depending on the flavor of agile or delivery approach they use.
  • Track work-in-progress as it goes from ‘to-do’ to ‘done.’
  • Refine the backlog.
  • Grapple with changes in scope, hopefully before, but sometimes after work has started!

On top of this, product managers need to manage stakeholders. A colorful cast of individuals and teams from sales, marketing, legal, senior management, and, let’s not forget, the customers and their users. Each person has their wish list, priorities, likes, and dislikes.

Product Managers need to manage stakeholders

While Jira is essential, it doesn’t provide all the tools product managers need to get the bigger picture on objectives and roadmap, collate customer feedback and feature ideas, and effectively communicate to all sorts of customers and stakeholders. Atlassian introduced Jira Product Discovery and Atlas as steps toward managing these activities. However, too many tools scatter information, decreasing productivity and decision-making.

Why Product Managers Struggle with Jira

Steep Learning Curve

As mentioned before, every Jira instance is a unique beast. For a product manager trying to get to grips with the team’s Jira, it can feel like learning to ride a bike at an Olympic velodrome while everyone else happily speeds around.

Every aspect of Jira can be tweaked and tailored – instance and project configurations, permissions, workflows, automations, apps, and more. When you learn most of them, you see how complex the software is under the curtain of a simple interface. So it can be challenging for new users to understand how everything works.

Some product managers who described themselves as not very tech-savvy find the Jira terminology confusing. With many ways to define and organize work – projects, issue types, boards, backlogs, sprints, and reports – it can be challenging to find what they need.

Other respondents talked about their frustration with the Atlassian documentation, finding it ok for troubleshooting but less helpful for understanding best practices in how to set up and use Jira effectively.

💡The Atlassian user community is a great place to ask questions, even if you don’t know the right words to use. Give plenty of detail, share what you have tried and what you expect to see. Finally, remember that the people answering questions generally do not work for Atlassian and are volunteering their time to help you and others. 

Agility Bottlenecks

Once our product manager starts to understand the ‘happy path’ of a project’s workflow in Jira, they need to manage the work and set the direction for others. At first, they can focus on the fresh issues, but sooner or later, they’ll have to confront the pile of older ones.

However, this is not always simple. Imagine a large project with thousands of issues – different types, statuses, and creators, all added at different times with different levels of detail. Inevitably some are duplicates; others are stuck in limbo or even irrelevant to the project. Each is a distraction to our busy product manager.

Jira backlog meme

So, they start to tidy them up, but it turns out they can’t transition an issue from its current state to the one in the ‘happy path.’ They check with a team member who, surprisingly, can see the transition option, but neither understand why they see different things. Eventually, their Jira admin finds that the transition is limited to a custom group of users. But think for a moment about how much working time was wasted in just this one example.

We’ll cover the administration and configuration below, but the key message is that processes and tools are put ahead of individuals, which goes against the core value of Agile. As a result, product managers spend more time driving the tool and less time focused on their customers and outcomes.

Jira Permissions Hell

A product manager’s frustrations with Jira don’t stop there. Once they’ve begun to see Jira’s potential, they found themselves blocked by permissions having to interact with an issue multiple times to complete a single update. Or these are the required fields that seemingly have no purpose that slow them down.

They gradually form an idea of how they want Jira to work, but again they are blocked. They don’t have the Jira administration permissions to do so. Even if they did have those permissions, they don’t know what needs to change.

Jira allows you to do certain things that you’re not aware of. But a user doesn’t have ‘permissions/privileges’ set up to perform those actions. So a user thinks it is a limitation of Jira. Moreover, because the option simply does not appear, a user doesn’t know that such functionality (or button) is something that exists and that they just need to ask someone for permission or higher privileges.

Vinit Karandikar, Principal Product Manager

💡To have a better idea of what Jira is capable of, you can check out the Atlassian University or Linkedin Learning courses. It helps you talk to the Jira admin on the same wavelength, express your requirements more clearly, and understand how to improve team processes with Jira.

Persuading team members and the Jira admin about the benefits of their proposed changes is the next hurdle, especially when those changes touch on existing projects and issues.  

One product manager told us how they inherited a Jira workflow with a ‘To Do’ state, and a ‘Ready’ state and an ‘Open’ state, and no one in the team understood the difference or why it was that way!

Jira simplified workflow meme

Convincing the team to change it required multiple meetings, and then they needed to wait for the Jira admin to find time to implement the changes.

The problem multiplies when there’s no ‘Jira superman’ (as one respondent described their admin) who knows the Jira instance like the back of their hand and can quickly make changes or help stuck team members. Atlassian’s move towards ‘team-managed projects’ is a step forward, but it only increases the need for more team members to become savvy with Jira.

Customer Collaboration Dilemma

Once a product manager is comfortable with the Jira’s setup, they typically need a way to record customer inputs and give their customers visibility of the product backlog. After all, customer engagement is crucial to steer the product in the right direction. They can use the Jira issue comments to capture customer insights, and users can vote for issues and ‘watch’ them to be notified of updates.

But many organizations do not want to give customers or internal stakeholders full access to Jira. There are three big reasons why.

  • Firstly, the cost. Jira bills per user but not everyone needs the full capabilities. It can become costly, especially for smaller teams with a large customer or stakeholder base. This is particularly the case for teams that want to provide a customer support portal with Jira, where the Jira Service Management price per agent can be too high for some teams.
  • Secondly, there is the admin overhead. Managing dozens or hundreds of extra users can be tedious. Users need setup, permissions, and deactivation once they leave the organization or no longer need access.
  • Finally, many customers and internal stakeholders don’t want to touch Jira. The same challenges of learning Jira still apply. Plus, many don’t have the time to search the bottomless pit of the Jira issues just to add a comment or track progress.

It poses the dilemma of finding a viable and cost-effective way to collaborate with customers.

💡Many teams use the Customer Case app’s portal for Jira Cloud to capture customers’ ideas and bugs. The app transforms any Jira project into an ideation platform or helpdesk, which allows collaboration with your customers or teammates via the ‘Jira mirror.’ It helps you tackle the collaboration dilemma since it both provides a cleaner overall experience and exempts you from

  • Extra costs for the customer’s Jira licenses
  • Extra efforts for the Jira user account management

Take our client’s word for it👇.

We are glad of your support solution because it is much simpler than Jira solution. For a small consulting company like us, this would be overhead. As well as costs. For us your solution is perfect for our own company size.

Marco Vögeli, Senior Consultant & Partner at Expris

Customer Case app forum

🚀Soon, the app will be integrated with Jira Product Discovery. It enables mapping a customer forum to the Jira Product Discovery project and capturing client feedback directly.

Jira Can Be Easy

We found that many product managers’ pains are common experiences. It’s key to remember that you don’t need to ‘bear the burden’ alone. Share your hurdles with team members and collaboratively strategize to overcome them. As it turned out, all the pains have treatments. Utilize the rich resources of Atlassian – the user community, solution partners, and marketplace apps. They can help you understand the possibilities, customize the platform to your needs, streamline your workflow, and efficiently deliver value to your customers. When you make Jira work for you, it won’t take long to say, ‘Jira is Easy.’

Jira is easy meme

What are your hurdles with Jira? Let us know what you think.


Pricing Adjustments for TeamCity Integration for Jira

June 30, 2022
4 min

We would like to inform our community and the customers of the TeamCity for Jira Integration app of the upcoming price changes that will affect all hostings (Cloud, Server, and Data Center).

Since the first release of the app, we have extensively invested in the development of new features, provision of timely and effective support, and, of course, collaboration with you on improvements and adjustments within the app. 

Our operational costs have greatly increased since that time, and at the moment we are heavily developing the Data Center infrastructure to ensure the reliability and high performance of our app under any circumstances.

Over the years, we were working to improve services for you and provide the best quality for your satisfaction. Thus, we’ve decided to normalize the existing prices and, in particular, make the Cloud version of the app more cost-effective.

For all hostings, the price change will go into effect on August 1, 2022. Below are the new pricing models.

Cloud Pricing

Data Center Pricing

Server Pricing

Buy at today’s price

You can buy TeamCity for Jira Integration at the current price till August 1, 2022. To save up even more, go with 2 or 3-year licenses — the price will remain the same for the whole maintenance period.

But even after August 1, 2022, existing customers with commercial licenses get a 60-day grandfathering period (till September 30, 2022), so you’ll have 60 days more to renew your license for the old price.

Have questions?

Please, feel free to contact us if you have any questions or need our assistance.

7 Must-have Apps for Managing Jira Projects Like a Pro

June 25, 2020
15 min

Project management is complicated. That’s why many PMs rely on software like Jira to plan and coordinate projects more efficiently. However, built for software teams, Jira isn’t a one-size-fits-all solution for most organizations. With each company having its unique set requirements, Jira’s default capabilities may not be sufficient.

Fortunately, the Atlassian Marketplace offers thousands of project management apps to help you manage projects in Jira like a pro. You can power up your Jira with these seven must-have apps for successful project management:

  1. Easy Agile User Story Maps for Jira by Easy Agile
  2. WBS Gantt-Chart for Jira by Ricksoft
  3. Smart Attachments for Jira by Stiltsoft
  4. Custom Field Option Synchroniser by Bitvoodoo
  5. Pivot Report by Colined
  6. Jira Workflow Toolbox by Decadis AG
  7. User Profiles for Jira by Communardo

Let’s discover more about these Jira solutions.

1. Easy Agile User Story Maps for Jira by Easy Agile

A story map is a visual representation of your customer’s journey with the product or service you are developing. It includes the actions taken by customers and their desired outcomes summarized through a user story.

Thanks to Easy Agile User Story Maps for Jira, your team is able to visualize their project backlog in a story map format. That way, everyone is aligned on a shared project vision.

Story maps transform the way your traditional backlog is presented. (Source)

Compared to flat backlogs, story maps add context to your issues. With a groomed backlog, your team can execute projects by putting themselves in the customer’s shoes. Thus, your project development efforts will be focused on providing value to your customers.

The app will auto-populate epics when it’s opened from your agile board. You can then arrange epics in chronological order, or in any order that suits your customer journey.

Hosting options: Cloud, Server, and Data Center.

Pricing: USD 10 per month for up to 10 users.

2. WBS Gantt-Chart for Jira by Ricksoft

Jira and Gantt charts bring out the best of agile and waterfall approaches for any project.

WBS Gantt-Chart for Jira transitions your existing Jira issues into a Gantt-based timeline, allowing you to break down issues into manageable tasks, track project progress, and allocate resources more intuitively. That way, you can gauge your team’s capacity and assign issues accordingly, so work is distributed evenly across your team members.

Need to view your linked issues in a Gantt-based timeline? This add-on lets you visualize and manage dependencies, so you can identify bottlenecks that impede your project’s execution.

Gantt charts are vital in visualizing high-level roadmaps of a project’s plan. Some of the key features that are highly rated by PMPs include milestone tracking and a critical path view. The app essentially turns Jira into a powerful MS Project alternative.

Break down projects into sequential issues and monitor their progress through Gantt charts. (Source)

Hosting options: Cloud, Server, and Data Center.

Pricing: USD 2.50 per month for up to 10 users.

3. Smart Attachments for Jira by Stiltsoft

To ensure all your project stakeholders are aligned on the project scope, it’s crucial to make attachments such as requirements, risks, and resources accessible.

While you can attach files directly from the issue screen, there’s still a lack of attachment management capabilities. For example, it’s a hassle to track the latest updates with multiple documents shared in a single Jira ticket.

The Smart Attachments for Jira apps addresses this issue by giving your team a better way to search and manage project attachments so that they can easily retrieve and refer to essential project documents.

Team members can add labels to documents, thus improving content discoverability in Jira Cloud. You can then group these labels into categories to sort files in a particular way. These categories are accessible from the Attachments section of your issue screen. That way, you can upload files directly to designated categories.

Tagging documents with labels helps users filter and access the right files.

A valuable feature of this app for Jira Server and Data Center is version control. This is especially useful for revised versions of contracts and change request management documents. You can upload revisions and map them to the original file. It then groups together all versions for you to keep track of it all.

Multiple versions of the same file are organized into groups.

Hosting options: Cloud, Server, and Data Center.

Pricing: USD 1 per month for up to 10 users.

4. Custom Field Option Synchroniser by Bitvoodoo

Custom fields allow you to modify your Jira fields to suit your project needs. Since every project is different, you may need to track information that is unique to your organization.

Jira gives you the flexibility to create custom fields, but there are limitations. While it provides standard fields such as issue titles and statuses, it doesn’t retrieve custom fields (e.g. customer requirements, budgets, and performance metrics) created from other databases.

Oftentimes, you have to get your Jira Administrator to manually create custom fields that are tailored to your project’s needs. Unfortunately, this is a time-consuming process – especially if you have numerous fields to be replicated, delaying the smooth start of your project.

Here’s where Bitvoodoo’s Custom Field Option Synchroniser comes in. It lets you retrieve custom fields created in other databases such as MSSQL, Oracle, MySQL, and PostgreSQL.

By synchronizing custom fields in existing databases, it saves you the hassle of recreating them on Jira.

Synced custom fields ensure consistency across systems used in your organization. This helps avoid potential discrepancies caused by free-form text errors.

The Custom Field Option Synchroniser also supports other multi-value custom fields on Jira such as checkboxes, radio buttons, and lists.

Maintain the consistency of your multi-value custom fields with Bitvoodoo’s Custom Field Option Synchroniser. (Source)

Hosting options: Server and Data Center.

Pricing: USD 180 per year for up to 50 users.

5. Pivot Report by Colined

As a project manager, it can be challenging to keep up with all the projects under your supervision. Pivot Report is a handy tool to gain a quick overview of all your Jira projects. It shows you the big picture of your issues in a pivot table format.

Stay on course with your projects by having an overview of its progress through a pivot table. (Source)

Having your issues presented in this format makes it easier to analyze core data pertaining to your projects. So you can gain better visibility over a project’s progress, from the estimated time taken to the remaining time to completion.

The reports are customizable using JQL to view progress displays according to assignees, sprints, issue types, and more.

Pivot Report even has a warning tab to flag flawed issues (e.g. overdue items or issues with no assignees). This way, you’ll be able to identify blockages in advance and take the necessary steps in overcoming them.

Hosting options: Cloud, Server, and Data Center.

Pricing: USD 5 per month for up to 10 users.

6. Jira Workflow Toolbox by Decadis AG

Workflows tie your project components together. In fact, establishing a workflow is one of the first things you should do before executing your project.

On a basic level, Jira workflow maps your issue statuses and transitions, which is reflected on your scrum or kanban project boards. For example, after an issue is completed it transitions from In Progress to Done. This, however, is done manually. Given the number of different projects under your belt, you may find updating issue statuses a repetitive task.

The solution is workflow automation. The Jira Workflow Toolbox does exactly that and more.

The Jira Workflow Toolbox’s automation feature reduces the time taken in creating workflows by executing transitions directly from your issue card. With flexible conditions, triggers, and validators, you’ll be able to automate customized processes based on your project management requirements.

On top of that, you can automate custom post functions to tailor to your project completion needs. For instance, notifying the issue reporter by adding a simple comment once the issue is marked as done.

It also caters to more complex workflows that can be configured using parser expressions, which you can then save and replicate for future project processes.

Jira Workflow Toolbox enables you to configure your workflows with specific transitions, conditions, and triggers from your Jira issues. (Source)

Hosting options: Cloud, Server, and Data Center.

Pricing: USD 5 per month for up to 10 users.

7. User Profiles for Jira by Communardo

With multiple team members collaborating across different project stages, internal communication is key to ensure a smooth workflow. But for larger organizations with distributed teams, this can be a challenge.

Your team may not know who to get in touch with immediately, which may delay task coordination.

Communardo’s User Profiles for Jira app provides teams with a faster way to get in touch with one another.

The app displays dynamic contact information when you hover over your team member’s names in a workflow.

The click-to-call feature makes it even more convenient for team members to collaborate synchronously and solve time-sensitive blockages.

Get in touch with anyone within your organization instantly with User Profiles for Jira. (Source)

Along with customizable fields such as languages and personal skills, team members are able to quickly find experts and identify reporting chains.

If your organization currently uses an existing employee directory, this tool can be synced to Active Directory and LDAP.

Hosting options: Server and Data Center.

Price: USD 10 for 10 users.

Take Jira Project Management to the Next Level

Jira on its own does wonders for project management. But it’s even better with the addition of apps to further streamline your project management processes.

Discover our comprehensive list of applications to boost your project management capabilities here!

Best Practices for Creating a Jira Issue With Templates

June 9, 2020
#How To#Jira
13 min

This is a guest blog post written by the Globo Solutions team. In this blog post, they highlighted the best practices you can use to create Jira issues with templates.


Jira indeed is a global solution. Thousands of people around the globe not only use it at work but also cannot imagine their lives without Jira. Users create so many tasks on a daily basis!

Have you ever wondered how much time we spend on creating issues or collecting missing information in issues? While it is minutes on a scale of one issue, but hours within a project, and even days for the whole Jira instance.

Various respected companies tend to find solutions that would help them optimize the issue creation process and minimize time costs. In this blog post, we will describe three ways to get this done:

  1. Out-of-the-box Jira capabilities
  2. Apps from the Marketplace that allow you to create issues with templates
  3. The Field Templates for Jira app

1. Tune-up your project in Jira

Buying an app is easy, but not all companies can afford it. So, the first option is exactly for them.

Jira allows setting descriptions for each of its fields individually out of the box. By adding field description or just inserting a link to documentation, you help users understand the rules and specifics of this particular field, saving your team’s time.

You can also use direct links to create issues. For example, if you click the link on a Confluence page, it will open the issue create screen. Some of these links may have prepopulated fields. It works the same as if you clicked on the Create button in Jira, but its fields already have all the information right where it belongs. You can read more details about this feature here.

2. Сreate issues with templates

The out-of-the-box Jira capabilities can be handy, but not for every case. Here comes the Atlassian Marketplace. Lots of vendors offer their apps for almost every possible challenge. Just type the word “Templates” in the search field on the Atlassian Marketplace, and you instantly get a variety of add-ons for creating issue templates. That would be the second option to pay attention to.

These apps have similar features as they let users save time on populating issue fields with the help of issue templates. You just need to pick the right template from the list. It is quite handy when you create lots of similar tasks.

In addition to that, other apps can create templates based on other tasks. These issues will have the same content as the original one. Similar to the native Jira Copy action but in a smoother way. It helps users optimize processes and save time, but it has its drawbacks. Setting up such templates is not a trivial operation. At first sight, it is not clear how to use it and how it all works. Note that you cannot combine the values of different fields. You have to create a separate template, thus multiplying them endlessly. Each time you need to combine field values from different templates. Any plugin will make you create a new template. This particular method gives you no other option.

3. Сustomize your templates for different needs

Yet the third option every user has at their disposal is the Field Templates for Jira app. This add-on is an alternative solution for issue templates. With its help, you can create templates for both system and custom text fields. Splitting templates visibility by project roles, issue screens, and types makes it more adaptive to every process and team.

You no longer need to reinvent issue summary or spend time on how to create issue description. All you need to do is to select the template for the current situation and fill in the rest if necessary. Combining templates is not only possible but welcomed.

As a result, it greatly speeds up the issue creation process for reporters. The ability to create comment templates not only on the project level but for each user individually is a nice bonus of this solution.


These are just three solutions out of many that we decided to describe for you. Still and always you are to choose what’s best for your business as every method has its advantages and disadvantages.

Here is a brief summary of all the above-mentioned solutions:

Solution Intuitive UI Flexibility Rich functionality Easy to set up Easy to use Personal templates Field types support Free
Native Jira tools


(minus) (minus) (minus) (plus) (minus) (plus) (plus)
Issue Templates apps (plus) (plus) (plus) (minus) (plus) (minus) (plus) (minus)
Field Templates for Jira (plus) (plus) (plus) (plus) (plus) (plus) (minus) (minus)