2013 年 11 月
2013 年 11 月 26 日
JIRA Agile and Confluence — Better together
If you use JIRA Agile and Confluence together, you can now create and/or link Confluence pages to JIRA Agile epics, stories and sprint reports. Try doing the following in JIRA Agile:
- From an epic: Create a new requirements document in Confluence (via the Product Requirements blueprint), or link to an existing page.
- From a sprint: Create new meeting notes in Confluence (via the Meeting Notes blueprint), or link to an existing page.
- From a sprint report: Create new retrospective notes in Confluence (via the Retrospectives blueprint), or link to an existing page.
Color change for the "To Do" status in JIRA Agile
The color red is currently used to indicate the "To Do" status in JIRA Agile. This has been change to blue in this upgrade, in line with the Atlassian Style Guidelines. You will see this color wherever a status is used, e.g. status lozenges, sprint health gadget, columns in Work mode, etc.
Improved board configuration UI in JIRA Agile
We've updated the board configuration user interface with a number of improvements. You'll notice that the tabs have been moved into a menu on the left. We've also made a number of tweaks to clean up the Columns configuration screen.
Status lozenges in JIRA Agile
JIRA Agile will use status lozenges to represent issue status rather than text/icons. The new status lozenges make it easier for you to see an issue's status at a glance, and look great! The lozenges also conform to the Atlassian Style Guidelines.
2013 年 11 月 21 日
Create JIRA issues from within Confluence the easy way
If you use Confluence and JIRA together it is now even easier to create JIRA issues right from your Confluence page. Highlight any text on a Confluence page and you will see a Create JIRA Issue option near your selection. This triggers a dialog where you can enter all the info necessary to create the issue in JIRA. The highlighted text will populate the issue summary.
If your highlighted text is in a table, you can choose to create multiple issues at the same time, using the text in the same column of your table. For example if you are using the Product Requirements blueprint - highlight some text in the Story column, choose Create JIRA Issue and follow the prompts to create all your stories in one easy step!
There are some limitations: If the project or issue type you select has required fields or custom field configuration you will not be able to create the issue from within Confluence.
Product Requirements blueprint improvements
This blueprint now includes a new prompt for you to create a JIRA issue to track your requirements. We have also renamed some headings on the requirements table, to make it clearer when you highlight text to create your stories in JIRA.
New instructional text type for templates
We have introduced a new type of instructional text that can be used in any template that, when clicked, triggers the JIRA Issues macro dialog allowing users to search for or create an issue. You can now see it in action in the updated Product Requirements blueprint.
The Page Properties Report macro has been improved to allow more sorting options, and better access to results on long pages. This macro is used in a number of blueprints, including Product Requirements and Decisions.
Changes to the Confluence byline
- The View Change and Show Comment links have been removed - click the edited date on the byline to see the most recent change to the page, and any change comment that has been entered.
Linked JIRA issues visible at a glance
Confluence page bylines now feature a JIRA Links button. This button gives you quick access to issues, epics, and sprints linked to the Confluence page.
2013 年 11 月 18 日
Improvements to the JIRA workflow designer
We've added the following features 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.
- トランジション ツールを使用して簡単にトランジションを作成することができます。
Tempo has been upgraded from 7.6.3 to 220.127.116.11.
New features in JIRA Service Desk
A new release of JIRA Service Desk will introduce some new, highly-requested features:
- SLA calendars - Create SLA calendars to track SLAs around working hours, holidays, weekends - whatever criteria you want!
- Request types - If you have many request types, you can use the new "Group" option to organize request types into groups that will help customers find the request type they need
- Localization - JIRA Service Desk now ships with language packs for Spanish, French, German, and Japanese.
Great new features now available in Bitbucket
- Now you can use the repository header in Bitbucket to quickly create a branch and take advantage of feature-based workflows that Git opens up. See the Bitbucket blog for more information.
- Status.bitbucket.org は一新されました。メール、SMS、Twitter、さらにはカスタム ビルドのシステムへの webhook POST でも、サイトからの更新をサブスクライブすることができるようになりました。メンテナンスなどのスケジュールされたイベントもポストされます。
2013 年 11 月 11 日
A new way to comment on a page in Confluence
Highlight any text on a Confluence page and you will now see a Quote in Comment button appear near your selection. This will add the selected text to the comment field, with the Quote style applied - much faster than copy and paste.
You will need 'Add Comments' permission in the space to do this. Users can also choose to disable this function in their Settings.
New JIRA Report Blueprint for Confluence
If you use JIRA and Confluence, creating Change Logs and Status Reports is now simple with the new JIRA Report Blueprint. Choose Create > JIRA Report and follow the prompts.
The Status Report uses the new JIRA Chart macro, which enables you to display information from JIRA as a pie chart on any Confluence page.
As with most blueprints, the templates used for both the Change Log and Status report can be edited to make these JIRA reports work for your team or project.
JIRA Issues Macro improvements
Bamboo Branch Deployments
Bamboo now offers branch deployments that allow you to create a deployment release from any plan branch in their version control system.
You should consider using branch deployments whenever you want to keep your in-progress development code separate from the master code, but want to test it within a deployable environment.
Simply select an alternative plan branch for deployment when setting up a deployment project:
Gliffy has been upgraded to 6.0.2 on Confluence. Please note that Gliffy 6.x does not support Internet Explorer 8. Read more...
2013 年 11 月 6 日
Any issue (or issues) created during a sprint on Work mode can now be added directly to that sprint.
See board type (Scrum or Kanban) on the Manage Boards screen
You can now determine the type of each board when viewing them on Manage Boards screen.