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 as part of JIRA Software Server 7.2, including a few that you’ve been patiently waiting on for some time. Thanks for helping us get to done!
1. Format content the way you want
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. So 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. As you format your content you can quickly see how it will be displayed. No more surprises – what you see is what you get.
[WPGP gif_id=”34998″ width=”600″]
2. Export issues directly to CSV
Exporting issues from JIRA Software to a CSV is nothing new, you could always export bulk issues through an HTML wrapped .xls file type, but that took a long time and often resulted in really large files. You told us that you wanted to export directly to a CSV file, and now you can with the latest version of JIRA Software.
Save yourself time and effort in post-processing with the flexible file type that’s compatible with just about every application. This also means less work on your end when exporting from one project and re-importing into another project as the import and export file types are now consistent. Trust that the data will be brought over successfully. Get the information you need from JIRA Software, faster.
3. Edit issues in context
We’ve made editing issue fields consistent so that you can edit descriptions, assignees, estimates, and drag and drop attachments without having to open the issue in a new window and jump into the issue detail view. So whether you’re a developer trying to reassign a ticket in your agile board or aproduct manager adding supporting details to an issue in your backlog, you can now edit issues inline and reduce context switching. Thanks for the feedback!
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 clone an issue without bringing over historical sprint details, saving you and your team head scratches wondering why your burndown charts included closed sprints.
Each of these features are included in our latest version 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. Learn more about what’s new in JIRA Software 7.2.