![]() Your customers can only vote if they’re a member of your organization in Jira. When you set up a new Jira board for feature requests, voting isn’t really that easy. While it’s not the most important factor for determining what to build, it gives you some guidance on what your customers need the most. When customers vote, you have a crystal clear idea about their actual needs and desires. One of the most important things about feature requests is voting. If you have a small number of important customers, you can even categorize your requests based on the person who made the request. “Customers” is another one that you can use to categorize requests based on the type of customer that requested the feature. ![]() It’s a good way to put aside features that will take months to build from those which you can handle quickly. “Complexity” is a good label to use, where you make a ballpark estimate on how difficult it would be for your product team to build a certain feature. You may want to organize your requests by more than the default criterion (area of the product), and this is the solution. Jira offers a good level of flexibility here with custom labels that you can use on individual requests. Needless to say, this can get very time and labor-intensive, so if you get a lot of feature requests, this may not be the ideal way to manage and categorize them. The main idea is to have everything neatly organized in one place for your product team to find. As new votes, comments or labels come in, the designated team members should also add these to the feature requests board. Once you’ve given it a proper name, make sure to invite every user in Jira who needs access to this board.Īs new feature requests come in, the team members assigned this task should add new entries to the board. In order for the feature requests project to work, you need to determine which board will be used for this effort. Note that you’ll need to have administrator access for this to work. So, create a separate project and a board and title it “Feature Requests” or something similar. Those are the issues that you are working on, while your feature requests are issues that you’re merely considering working on. Your product (development, backlog, bug fixes) should go into a completely separate project for one simple reason. Those are then further divided into Boards for better organization. Within Jira, work is organized into Projects. Jira is intended for product development - building a new software product or maintaining/fixing an existing one. In short, you’ll need to go to your Jira administration board and create a new project and title it Feature Requests or something along those lines. If you want to share your feedback board or create a roadmap, you have to export the data and use it in some other app to make it public for your entire audience. In other words, whatever you create in Jira has to stay available to your team only. The main difference between a proper feature request and feedback software is that a feedback board in Jira is not public. While it’s not the primary use for Jira, the tool can be used for feature requests with a little bit of preparation in advance. Since these are related to the product anyways, Jira seems like a logical choice of app for the job.īut is it really? Today, we’ll find out how you can use Jira for customer feedback and feature requests and whether it’s the ideal tool for the job - and what to get instead.Ĭan you use Jira for feature requests and idea management? One of the things that you can use Jira for is to track and manage feature requests and ideas. From managing new projects to fixing bugs and tracking who’s doing what, Jira takes care of a giant chunk of daily operations for teams worldwide. For many developers, designers, product managers, and all sorts of IT professionals, Atlassian’s Jira is an invaluable tool that makes their lives easier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |