14 July 2014 to 18 July 2014
Workflow transition triggers rollout completed LABS
Workflow transition triggers is now available on all JIRA Cloud accounts that are connected to Bitbucket.
As a JIRA administrator, you can configure triggers in JIRA workflows that respond to events in your linked development tools. This allows you to set up your development tools and JIRA workflows so that, for example, when a developer creates a branch to start work on an issue, the issue will automatically be transitioned from 'Open' to 'In progress'.
Your workflow transitions can be triggered by the following events in Bitbucket (and GitHub):
- Pull request created
- Pull request merged
- Pull request declined
- Branch created
- Commit created
A JIRA administrator can configure a trigger on a workflow transition when editing the workflow:
Click Add trigger (on the Triggers tab, shown above) and choose an event type:
Repository branches, commits and pull requests are automatically linked to a JIRA issue if the JIRA issue key is included in the commit message, branch name or pull request title – see Streamlining your development with JIRA OnDemand.
Your JIRA instance must be linked to Bitbucket (or GitHub) using the DVCS Connector plugin – see Using the JIRA DVCS connector.
New chart type for the JIRA Chart macro
If you have JIRA and Confluence, reporting on your project is now even easier with the new Created vs Resolved chart. It's a line chart showing the difference between the number of issues created, and the number of issues resolved over a given period of time.
To try this chart go to Insert > Other Macros > JIRA Chart.
Column sorting for Tasks
You can now use the column headings to sort task reports and the tasks in your profile by due date, assignee or page. Find out more about task reports in Add, Assign, and View Tasks.
Restrict blog posts
By popular demand, you can now restrict blog posts. Restricting a blog post is useful when you want to be able to make a blog post only available for a specific group or people.
Notifications will be sent at the point a blog post is created - removing restrictions doesn't trigger a new notification.
Content indexing now restricted in OnDemand
Administrators are no longer able to access the Content Indexing page in the admin console. This change has been made to increase the stability of your OnDemand site. In normal use you should not need to manually reindex. If you do experience problems contact support who can investigate the issue and perform a reindex for you. We apologize for the late notification of this change.