Since our early days, we’ve encouraged customers to share feedback and suggestions for improving JIRA Software through our feature request site. The JIRA Software team recently closed out some of the highest voted requests (more than 1,200 votes in total!) as part of the latest JIRA Software 7.2 release, including a few that you’ve been patiently waiting on for some time. Thanks for helping us get to done!
1. Edit issues from your agile board or backlog
Does this sound familiar? During sprint planning your team is going through the backlog at rapid fire pace. Ideas are rampant, tasks are being distributed, and estimates are being nailed down. But each time you need to update an issue in JIRA Software, someone has to stop everything and open the issue in another tab to make changes. Then they jump back to the backlog and repeat the process all over again.
Not anymore. You can now update your issue fields directly from your agile boards. Edit descriptions, assignees, estimates, and drag and drop attachments without having to open the issue in a new window. Whether you’re a developer trying to reassign a ticket in your agile board or a product manager adding supporting details to an issue in your backlog, you can now edit issues inline, allowing your team to spend less time updating tickets and more time focusing on what needs to get done. Thanks for the feedback!
2. Export issues directly to CSV
There are several formats for exporting issues from JIRA Software – Excel, XML, RSS just to name a few – but many of you told us that you wanted a raw CSV file so that you could more easily import into other tools or back into JIRA Software. We listened, and now you can.
So whether you’re importing issues into a reporting tool to build custom reports, or exporting issues from one project and re-importing into another, you can now get the information you need from JIRA Software in your preferred format.
3. Rich text editor
Adding thorough descriptions to tickets helps communicate the importance of an issue while setting the right expectations and giving the team the context they need. With the new rich text editor, you can now create, edit and format issue descriptions and comments the way you want.
If you’re copying and pasting text from another application, or just want to add tables to your issue description, you can easily do so without using Wiki markup. For members of your team who don’t know Wiki markup, they can jump in and provide rich content without any hassle.
As you format your content you can quickly see how it will be displayed. No more surprises – what you see is what you get. More than 400 of you told us that rich text editing would make your lives easier. Enable it in JIRA Software Labs today!
4. Clone an issue without sprint details
We know it happens from time to time that an issue doesn’t get completed in its original sprint. In order to make sure it doesn’t slip through the cracks, you probably want to make a copy of the issue and carry it over to another sprint, board, or even a different project. Until now, cloning an issue meant cloning all of the details associated with it, including sprint history. Based on your feedback, you can now can clone an issue without bringing over historical sprint details, saving you and your team head scratches wondering why your burndown charts included closed sprints.
Plus, improvements to JIRA Software at scale
When teams scale JIRA Software to hundreds or thousands of users it quickly becomes mission-critical and application response times can’t get in the way. With the latest release we’ve made improvements to how JIRA Software handles response times under high load and are excited to report that JIRA Software is now more stable and better equipped to handle thousands of concurrent users than any other version.
We’ve also made significant improvements to how larger customers – think thousands of issues and users – rebalance issues and look up users. We’ve heard from some of you that rebalancing could take several hours to complete and that searching for users could take several seconds, causing some serious frustration. JIRA Software 7.2 fixes these lag times and in our testing we’re seeing up to 10x improvements for both. For more details on these and other improvements, take a look at our documentation.
Each of these features are included in our latest release of JIRA Software which also includes improvements to Versions and Components configuration and a simplified onboarding experience for new users and admins. And, JIRA Software Server is now available in Portuguese, Korean, and Russian to help teams all over the world ship the next best thing.
Did you find this post useful? Share it on your social network of choice so your fellow JIRA software server fans can learn about 7.2 availability, too!
The post 4 features you asked for from JIRA Software appeared first on Atlassian Blogs.