2014 年 2 月
2014 年 2 月 27 日
JIRA AGILE Enhanced Control Chart: Click and drag to zoom
The enhanced Control Chart (Labs only) now allows you to zoom into a time period using your mouse. Just click and drag over the desired time period. You can zoom out by resetting the Time Scale to its default value or manually setting the Time Scale.
JIRA AGILE Enhanced Control Chart: default time scale changed to three months
We've taken your feedback on board and changed the default time scale for the enhanced Control Chart (Labs only) from two weeks to three months. If you have less than three months of data, the time scale will be automatically set to the time period that encompasses all of your data.
Note, if you manually change the time scale, the time scale will be saved and shown the next time you view the chart, as per current behavior.
JIRA AGILE Enhanced reports clearly indicated in the user interface
You will have a mixture of enhanced reports and old reports, if you have enabled enhanced reports (Labs only) for your JIRA Agile instance. The enhanced reports now have NEW lozenge next to them, to distinguish them from reports that have not been enhanced yet.
2014 年 2 月 26 日
CONFLUENCE QUESTIONS Ask and answer questions on the go
We've made it easier for you to search for, ask, answer and vote on questions - all from your mobile device.
2014 年 2 月 10 日
JIRA SERVICE DESK New features available in JIRA Service Desk
Several new features have been introduced in JIRA Service Desk 1.2:
- Customers can now log in directly through the Customer Portal to submit requests - they won't even know they are using JIRA! You can hide the information your team uses (internal statuses, fields, and SLAs) so only you and your service desk team members will see it. Your customers never will.
- With this release, JIRA Service Desk makes it easy to set up your team to work in your service desk. You can now assign your users to JIRA Service Desk-specific roles, which are designed to support the way most service desk teams are set up: administrators, service desk team members, and your service desk customers. When you assign people to these roles, JIRA Service Desk will automatically grant the permissions they'll need for their tasks.
- 最重要リクエスト要件について、SLA 目標を計測値を含めて簡単に作成できるようになりました。
You can migrate to the standard JIRA Service Desk permission scheme by going to the new People tab and following the prompts. Your JIRA Service Desk projects will not be migrated to this permission scheme automatically.
Visibility into the status of builds and deployments related to a JIRA issue
We've added build and deployment information to the Development panel for issues in both JIRA and JIRA Agile.
In addition to the information about branches, commits and pull requests that recently became available, you can now see the status of recent Bamboo builds and deployments related to the JIRA issue. To narrow in on the build and deployment information, simply click on the item in the panel.
If you're using FishEye 3.3 or Crucible 3.3, or later versions, information about commits, branches and reviews will also be displayed in the Development panel. Existing application links to FishEye and Crucible will need to have 2-legged authentication enabled.
TEMPO Tempo upgrade
Tempo will be upgraded from 7.8.1 to 184.108.40.206. This version fixes an issue with the previous deployment of Tempo, where the Tempo button would incorrectly show on JIRA Agile boards when Tempo is not licensed (https://tempoplugin.jira.com/browse/TT-371).
2014 年 2 月 3 日
New user management experience now available
The new user management experience is now available for all eligible instances . The new experience and features have been designed to make it simpler for you to manage your users from one central place in OnDemand (no matter which application/s you use).
User management is accessible from the > User Management menu. You can then use the newly redesigned features to manage users, groups, and application access. For details on the new features, see User Management FAQ - January 2014.
JIRA Recent JIRA highlights
Over the past few months, we've released a number of features and improvements to JIRA OnDemand. Here's a recap:
New code integration features for issues
The new Development panel, which is shown on every issue, helps you to evaluate the development status of an issue at a glance. If you need to investigate further, click any item to display more details, or drill down into the development tool.
Connect to one of these compatible applications to enable the following:
GitHub/GitHub Enterprise: view branches, view commits, view and create pull requests
Enhanced workflow designer
The workflow designer is now faster and easier to use. We've added a range of new features and made the user interface cleaner and less cluttered. You can now click to create transitions, reuse existing transitions, zoom (with the 'alt' key or the +/- controls), drag and drop to retarget the destination of a transition, and more!
In fact, the workflow designer can do everything that we supported in the old 'classic' workflow designer, so we've given the 'classic' designer a well earned retirement and removed it from JIRA.
Simple issue type configuration
We've simplified issue type configuration in this release. Don't hunt around in JIRA administration to find the workflow or screen for an issue type. The issue types associated with a project are now tabs on the project's administration screen.
This approach makes it easier to understand how your projects are set up. Each tab also provides access to the and screen designer , so you can configure an issue type without leaving the project.
New status lozenges
We've introduced new "lozenges" to represent statuses in JIRA. We've switched from the old icon+text representation to make it easier for users to locate and identify statuses. The new status lozenges also conform to the Atlassian Design Guidelines (ADG). This blog post explains the background behind this change.
We no longer support custom images for status icons. However, you will be able to configure statuses to use any one of the slick new status colors (categories) in JIRA.
JIRA now tracks and records a range of configuration changes in an audit log. This can help you diagnose problems in JIRA or can be used for security purposes. Find out when a user was added or removed, when a workflow scheme was modified, and more. Note, auditing is disabled by default — you will need to enable it to start tracking changes in JIRA.
This is the initial release of auditing. We're still working on a number of improvements that you'll see in future JIRA upgrades.
- Creator of an issue is now automatically recorded for every issue. This is particularly useful, if you need to know the creator of an issue for compliance reasons. The creator is distinct from the reporter (which can still be configured to be an optional field).
The creator can be seen in the issue history. If the creator is the same as the reporter, the name of the creator will be shown in the Reporter field on the issue.
New 'creator' JQL field — Find issues by their creator by using the new 'creator' JQL field. Learn more...
New 'attachments' JQL field — Find issues that have attachments or issues that do not have attachments with the new 'attachments' JQL field. Just add the clause "attachments IS EMPTY" or "attachments IS NOT EMPTY" to your advanced search query. Learn more...
Filtering for User Picker custom field — You can now limit the users that can be selected in a user picker custom field, to specified groups and/or project roles. Just configure your user picker custom field and choose the new Edit User Filtering link. Learn more...
JIRA CONFLUENCE Support for Internet Explorer 11
Both JIRA and Confluence now support Internet Explorer 11.
CONFLUENCE Hide previews in the Attachments macro in Confluence
You can now choose to show or hide previews in the attachments macro. You can also choose to sort the list by last modified date or created date.
CONFLUENCE Sort JIRA Issues macro
We're continuing to improve the JIRA Issues macro. You can now sort the macro using column headings.
CONFLUENCE Create issues in projects with required or custom fields
You can now create JIRA Issues in the Confluence editor (via Insert > JIRA) in projects that have required fields.
There are still some limitations, but we currently support:
text based required custom fields (number field, text field (single line and multi-line) and URL field types only)
Required fields when creating issues when viewing a Confluence page (highlight text > Create JIRA Issue) will be available soon.
CONFLUENCE Add a custom favicon in Confluence
Administrators can now upload a custom favicon to your Confluence site. Favicons are the icons that appear in your browser tab.
JIRA Reuse transitions in the JIRA workflow designer
You can now reuse existing transitions in the workflow designer. Just add a transition and choose the Reuse a transition tab.
You will only be able to reuse transitions that have the same destination status as the new transition you are adding — the values in Transition to reuse field will change depending on the value of the To Status field.
JIRA Filtering for User Picker custom field in JIRA
You can now limit the users that can be selected in a user picker custom field, to specified groups and/or project roles. Just configure your user picker custom field and choose the new Edit User Filtering link.
TEMPO Tempo upgrade
Tempo has been upgraded from 220.127.116.11 to 18.104.22.168.
More improvements to the workflow designer
You can now scroll over the workflow editor with your mouse. Zooming in only occurs when you press the keyboard shortcut for zooming while scrolling.