Child pages
  • Common Questions from the Webinar
Skip to end of metadata
Go to start of metadata

We are still working on the recording. We'll update this page as soon as the recording is available.

You can find the slides at

Only the owner of the dashboard can change the content (portlets). If you are interested in using a shared dashboard and you would like to customise the content please take a look at copying an existing dashboard:

The tabs there are links to our other demo instances - the banner at the top is your 'Dynamic Announcement Banner':

The Charting Plugin is needed to add the charts you are referring to. This plugin provided various charts and reports for JIRA.

The JIRA migration/upgrade process is essentially:

  • create an XML backup of your existing JIRA instance
  • download and install the new JIRA instance
  • create a new database for the new instance
  • ensure the new JIRA is using the new database
  • restore the XML backup into the new JIRA

You should read the complete documentation on this process here:

The 'create shared objects' is a global permission - so by default all users can create them, but you can restrict that to specific groups through Global Settings > Global Permissions.

If it's your dashboard, all instances will be affected. But, you can copy a shared dashboard to make your own which you can change independently.

Atlassian conducts free web-based seminars for JIRA. These webinars are intended to demonstrate JIRA's functionality live and also field questions from participants.
The presentation is streamed live to your browser while you participate in a teleconference with our presenter.

For information on upcoming JIRA demonstrations, please visit:

Atlassian offers training for Confluence and JIRA. This training is designed to help you and your team get started and use our products successfully.

Atlassian currently offers the following training modules:

  • JIRA Fundamentals
  • JIRA Administrators
  • JIRA Workflow

If you or your colleagues are interested in any of these you can find out more at:

Instead of using a 30-day evaluation license, it is better for you to use one of our 12-month developer licenses.
Holders of commercial licenses can create a free developer license for use in a cold standby, development or testing server.
The license is perpetual, with access to software updates for the maintenance period of the commercial license.

The technical contact for the commercial license can generate a developer key by following the directions at:

A good place to start learning about how JIRA can be used for helpdesk or support needs can be found at:

A JIRA helpdesk or support system sample file that will help with understanding how a helpdesk or support system is used is:

Yes, if you're planning to start using JIRA, the newest release will give you the most features and functionality. You can download the latest version at:

The plugin mentioned was the IDE Connector - developed by Atlassian. This is an extension to the IDE and is installed separately from JIRA out of the box installation. The current support for Eclipse is limited, but improving. You can see more info on the IntelliJ and Eclipse integration at:

JIRA and Confluence were designed to complement each other. If you wish to see how well JIRA and Confluence integrates together you may do so by reading this documentation:

There is a general overview video of this which you may wish to see:

It is a .mov file which can be played in Quicktime. If you do not have Quicktime you can download it from here:

A list of upcoming Atlassian User Groups (including Europe) can be found at:

JIRA's Project Import tool allows you to restore a single project from a backup file into your JIRA instance. This feature is particularly useful if you do not wish to overwrite the existing projects or configuration of your JIRA instance by importing the entire backup. Your backup file must have been created using JIRA's backup tool. You cannot import a project from a backup using your native database tools. For complete info on the limitations of the project import please go to:

Yes - we currently have webinars for JIRA, Confluence, Bamboo, Clover, FishEye, Cruicble, and JIRA Studio. You can see the entire schedule and sign up at

Yes. We have a solution tour and helpful setup tips.

To see the limitations of the project import please go to:
A section on custom fields can be found there.

You'll have to check each individual plugin page to see what versions of JIRA the plugin is compatible with.

There is a new feature request were you can find out any updates and add comments:

You may want to make yourself a watcher to this new feature so you can be notified of any updates or changes.

We plan on having the webinar in late October, but no date has been set at this point. Keep your eye on Atlassians blogs for upcoming information:

You can also email and we can put you on a mailing list.

The integration makes it easy to get an update on the status of each project. Are your projects going to be on schedule or held up? What issues are causing the most problems? Which issues have been resolved most easily? These are the types of questions that Bamboo 2.1 + JIRA help solve.

For example, when you integrate JIRA with Bamboo 2.1:

  • Bamboo will still automatically link an issue to your build when you specify it in your commit message, but it will now also pick up related JIRA issue keys that have been included in build comments and labels.
  • You can flag when a particular JIRA issue is fixed in a project version and make the build artifacts available (and downloadable) right from the JIRA issue.
  • Real-time tracking of the builds for a project or version has been included in this release of Bamboo.
  • Get a detailed view of which issues are linked to completed builds and which issues were worked on recently.

Check out the latest info at:

Use Application Links (AppLinks) to link your JIRA, Confluence, FishEye, Crucible and Subversion applications. You can even choose to associate individual projects, spaces, reviews and repositories with each other. You can then use shortcut links within each application. The application will 'know' automatically which space, project or repository the link is referring to.

Yes. FishEye and Crucible are separate products from JIRA.

If you are using JIRA for software development, and your team is using CVS, Subversion or Perforce FishEye and Crucible are tools for you.

FishEye provides a web based view of your existing source code repository that helps teams monitor, search, share, and analyze your source as it changes. Email, RSS, changesets, charts, annotations, enhanced diffs, and lots more -

Crucible makes it easy to review code changes, make comments, and record outcomes in an efficient, distributed, and process-neutral way. Not only is it very productive, your SOX auditor will love you -

For JIRA users, the killer feature is the FishEye plugin for JIRA. It gives you FishEye info & Crucible access inside JIRA. It is free and open source -

  • Powered by Atlassian Confluence 2.10-m3, the Enterprise Wiki.
  • Printed by Atlassian Confluence 2.10-m3, the Enterprise Wiki.
  • Bug/feature request -
  • Atlassian news -
  • Contact administrators
  • No labels