Skip navigation
1 2 Previous Next


29 Posts authored by: velias

JIRA Agile plugin of JIRA has been updated to latest version 6.7.6.


Search by the Sprint field for JIRA's basic search had been introduced in JIRA Agile 6.7.2. In this release, the Epic Link and Epic Name fields has been added as parameters for the basic search. Just navigate to the basic search, click More and add the Epic Link and/or Epic Name field.



Release contains few bugfixes also. For more details see Release notes JIRA server running at provides streamlined functionality of "Start Progress" action now, which is in align with latest JIRA default workflow.


You had to manually assign issue to yourself to be able to perform "Start Progress" action before this change. Now, the "Start Progress" action is available to all Assignable users (potential developers). Status of the issue is changed and you are made issue's Assignee once you use it, so one less click is necessary and workflow is more user friendly.





Lots of projects hosted in JIRA uses original "Git Pull request workflow" created about four years ago. This workflow allow user to manually switch issue to "Pull Request Sent" status once GitHub PR is created, and manually insert URL of pull request into "Git Pull Request" issue field. This workflow allows projects to better track and process Pull Requests, but heavily depends on manual work.


New JIRA features like DVCS plugin and event based workflow transitions introduces in JIRA 6.3 series allowed us now to create better PR tracking workflow, which removes this manual work.

This workflow automatically switch issue to "Pull Request Sent" status once GitHub PR is created and issue key is mentioned in PR's name or description. Pull Request URL is not stored in "Git Pull Request" issue field, but it is visible in "Development" area of JIRA issue detail screen.

JIRA issue is automatically resolved once GitHub PR is merged then. If GitHub PR is refused then no any JIRA issue status change is done.



Project leads who want use this feature for their JIRA project can follow next steps:

  • GitHub repository must be owned by github "Organization", personal repositories can't be linked
  • jboss-jira-hook github user must be added into the organization's Owners group. Jira needs this to add webhooks into GitHub repository to track changes immediately.
  • then you have to email with request to add your GitHub repository into JIRA configuration and switch your JIRA project to use "GIT Pull Request workflow with automatic PR triggers workflow scheme". You have to specify which Github repositories do you want to add (all owned by some Organization, or few named only) and which JIRA project should be switched.


Thanks pilhuhn for Feature request for this improved workflow and his testing on Hawkular project.

We're proud to announce new feature 'Social Log In and Sign Up' for website released few days ago.


It allows you to use your Google, GitHub, LinkedIn, Facebook and/or Twitter account to create a new user account. You can also link these accounts to your existing account.

The linking allows you to login to website later without entering other password if you are logged in on Google for example. You can simply resolve "I forgot password" cases also, by logging in over linked account and changing password then.


You can find Social provider icons directly on login page and use them for Log In or Sign Up.



If social account is not linked with any account yet, you can do that via next screen allowing you to link it with your existing account or create a new one.

Registration form is prefilled by name and email obtained from your social account to save your work a bit.



Later you can manage your Social accounts links from user profile page.



Based on statistics this new feature is very useful since aprox. 30% of newly created user accounts are created over it now. Google provider is the most popular one, making over three quarters of all uses. Facebook provider is second well ahead of other providers.

"comment by email" feature has been enabled for jira running at during today's outage.

It means you can reply to a notification email received from jira, and your text will be added as comment for the issue received email was about.


"Add a comment from the non quoted email body" handler is used. This message handler creates a comment, but only uses the 'non quoted' lines of the body of the email message. A quoted line is any line that starts with a '>' or '|' symbol and such lines of text will not be added to the comment. The issue to which the comment is added is chosen from the first issue key found in the email subject. The author of the comment is taken from the address of the email message's From: field. Messages from unknown email addresses are ignored silently.


As part of this task we have to change email address JIRA uses as From in emails to

You have to upgrade your "from JIRA" email filters if they depend on it.



now you can send documentation pages from Confluence running at to your Amazon Kindle reader.



This feature was introduced over new Confluence to Kindle plugin.



during JIRA outage last week we introduced new plugin called JIRA DVCS Connector for Bitbucket and GitHub.

This plugin allows to directly show commits from Github repositories on JIRA issue page, with links pointing back to the Github directly. So it's not necessary to use FishEye at anymore for this kind of functionality.


New "Commits" tab is shown on issue detail page. It contains informations about GitHub commits with key of the issue mentioned in the commit message.


Plugin allows JIRA issue transitions directly from a Github commit message also.


JIRA DVCS connector plugin uses Github web hooks to propagate commits into JIRA immediatelly, which brings small restriction into process of connection.


Project lead, who wants to link his project's Github repository with JRA, must follow next steps:

  1. Repository must be owned by github "Organization", personal repositories can't be linked
  2. jboss-jira-hook github user must be added into the organization's Owners group. Jira needs this to add webhooks.
  3. then you have to send email to and ask jira administrators to add repository into JIRA DVCS configuration. You have to specify which Github repositories do you want to add (all owned by some Organization, or few named only), and if you want to allow automatic JIRA issue transitions from a Github commit messages.


Enjoy. JIRA instance has been updated last Thursday to bring you latest version of JIRA and GreenHopper, as you can see in release notes.


JIRA upgrade from 5.2.5 to 5.2.7 brings mainly few bugfixes, no any significant change for users was introduced here.


GreenHopper upgrade from 6.1.1 to brings few new features, for example:

  • Search for Issues by Epic Name
  • Search for Sprint by Name
  • Add more Fields to the Issue Detail View
  • Create Issue when viewing an Epic in JIRA

You can find links to complete release notes for all new versions in ORG-1616.


Two new plugins was introduced also. Separate blogpost will be published for both of them later to introduce what they bring for users.



a few weeks ago we configured JIRA instance ( to allow remote linking of issues with Hibernate JIRA ( and Apache JIRA ( This feature allows better linking of issues with upstream/downstream project issues. Linking with Hibernate JIRA is bidirectional, so you can link from Hibernate JIRA issues to issues too. Linking with Apache jira is possible from JIRA only,  linking is not configured on Apache jira side.


The feature is available from common jira issue Link action. Linking dialog now contains new field called "Server", where you can specify JIRA server you want to link issue from. Then you can directly type in issue key from selected server, or search issue against the server.


Details about JIRA remote issue linking are available in JIRA documentation. JIRA instance has been updated this Wednesday to bring latest version of JIRA and other installed plugins and some bugfixes as you can see in release notes.



JIRA point upgrade from 5.2 to 5.2.5 brings mainly bugfixes and performance improvements. One noticeable change is move of reports from dropdown menu to the panel on the Project Summary page, so they are more accessible now.



GreenHopper has been upgraded from 6.0.8 to 6.1.1 which brings few new features and enhancements. Main enhancement is introduction of Epics, which provide you with an additional hierarchy of story management, providing planning guidance for groups of issues within, or across, projects. For details see 6.1 and 6.1.1 release notes.


Balsamiq Mockups

Balsamiq Mockups plugin for JIRA has been upgraded from 2.2.2 to 2.2.4 which brings support for linking to web addresses (URL's) in all controls that support linking and other improvements and fixes. See relese notes for full list of changes.

Hi all,


new integration point for JBoss Community systems is here as I promised last week. It's based on feature request ORG-1560 and allows you to display build results from Jenkins instance running at the on the hosted JIRA dashboard or on some pages of

Displaying build status on JIRA Dashboard

If you want to display build status on jira dashboard, simply login to JIRA and display your dashboard (you have to create your personal dashboard if not created one yet and use only default dashboard). Then use "Add Gadget" button at top right, select "Other" group in "Gadget directory", and use "Add now" button for "Build Status" gadget.


Then you can close "Gadget directory" and configure gadget on dashboard to show selected build. Use small arrow button on top right of gadget window to open menu, and use "Edit" item here. Then you can put name of selected jenkins job into provided input field and "Save" it.


Page is reloaded and voila, build status for selected job is shown here.


Color around Job title is changing depending on status of last builds to provide you quick visual information. It can be green, yellow or red. Job title acts as link to the job page in Jenkins server. And there are links to the latest, latest successful and latest stable builds of given Job too.


If you want to monitor more jobs simply add other "Biuld Status" gadgets into Dashboard.

Displaying build status in

Very similar process can be used to display build status in some pages of system. It can be used on all pages with configurable layout as is Personal dashboard, Space main page, Group main page etc. 


Technical background

Build status displaying is based on Google Gadget technology, so in reality it can be used in each system/container supporting this technology. Gadget is hosted as plugin in JIRA, and uses Jenkins REST API to obtain build status information to be displayed.

If you want to use this gadget in another gadget container system, you can find URL to the Gadget definition xml file on JIRA "Gadget directory" page, it's .


And finally, source code for this gadget is available at





this week we performed upgrade of JIRA instance running at to fix some bugs and bring you few new features.

JIRA point version upgrade from 5.1.4 to 5.1.7 is about bugfixes only, but GreenHopper upgrade from 6.0.3 to 6.0.6 brings you something new as you can see in release notes:


We also continue to improve our community members experience, productivity and collaboration by better integration of distinct systems. Latest addition to this topic on JIRA side is automatick linking to the RedHat bugzilla, based on  ORG-1098 feature request.

Simly if you use something like BZ-12345 or BZ#12345 or Bug 12345 in JIRA issue descriptions, comments etc. it's automatically rendered as link pointing to the bug in RedHat bugzilla.

And we are working on more integrations in our systems, stay tuned ;-)



As you probably noticed, JIRA instance running at have been upgraded today to JIRA 5.1.4 and GreenHopper 6.0.3


This minor JIRA update patches few problems as you can see in Release Notes. Probably most noticeable for common user is better handling of text selection in fields on issue detail page, which do not force inline editing anymore.


GreenHopper has been updated from 6.0 to 6.0.3 which seems as minor upgrade too. But beside bunch of bugfixes it brings much more new feature than expected, as you can see in and Main enhancements and changes:

  • Multiple active sprints
  • Ability to rename future sprints
  • Burndown Report shows what didn't get done
  • Customisable Issue Detail View
  • Visual indicators for distinct types of board.
  • Easier management of Remaining Estimate



Hi all,


as you probably noticed, JIRA instance running at has been upgraded today to JIRA 5.1 and GreenHopper 6.0.


Beside  security patches which forced us to speed up this upgrade, there is bunch of interesting improvements in JIRA 5.1 as you can see in Release Notes. Probably most noticeable are:

  • Inline editing on issue view page
  • 'Autowatch' issues you create or comment on
  • Project administration and performance improvements


GreenHopper has been updated from 5.10 to 6.0 

Main enhancements and changes:

  • New Agile menu structure
  • Future sprint planning



Hi all,


as you probably noticed, JIRA instance running at has been upgraded this week to JIRA 5 and GreenHopper 5.10.


There is lot of interesting improvements in JIRA 5 as you can see in Release Notes. Probably most noticeable are:

  • Share issues when you need someone else to take a look at a JIRA issue or a list of issues
  • Mention users in Description and Comment fields
  • JQL enhancements to search for issues based on their history
  • Improved and more stable REST API


GreenHopper has been updated from 5.8 to 5.10, so you need to check two release notes:


Main enhancements and changes:

  • Improved Rapid Board
  • Scrum graduates from Labs



Filter Blog

By date:
By tag: