|
JIRA Evaluator Resources |
 The built-in Priority field in JIRA is customizable on a global level - meaning across all projects. However, you can create a custom field select list called 'Priority' and set your own values there, and associate that field with one or more projects. See the JIRA Quick Start Guide for help setting up fields and associating them with screens, issue types, and projects.
Currently it's not possible to have issues assigned to more than one user within the JIRA workflow. However, there is a slight work around by adding the custom field 'group picker'. This is mentioned here. Another way to do this is to set up a group email address (i.e. supportteam@abc.com) and assign that group email address as a 'user' in JIRA.
If you're trying to clone a list of tasks, the best way to do this is to set up a 'master parent task' with a list of 'subtasks' that you want to clone. You can then clone this master template (along with all the subtasks) and move it into your new project. You can also use the project export/import feature for JIRA 3.13.
There are a few things to note here, I'll list them point by point below for ease of reading. 1. Very Large Public Instances. https://issues.apache.org/jira is a large open-source JIRA with more than 86,000 issues, 25k users, 76 new issues per day, and 92 hits per minute. It's an out-the-box JIRA Standalone hooked up to Postgres configured with 750Mb of memory. That is a good example of high-usage JIRA that we have stats for. It's good because anyone can give it a poke to test performance. The other major public instance would be our own instance. http://jira.atlassian.com has over 49,000 issues and over 39,000 user accounts. Our system runs on a 64bit Quad processor with 4 GB of memory of which 1 GB is dedicated to JIRA. Take a look at our JIRA Installation Guide for hardware requirements and more information about # of issues, users, and concurrent users. 2. Atlassian Professional Partners. Atlassian Partners help implement, localize, configure, and support our products. Atlassian partners offer a wide range of software development skills, consulting expertise, and best practices experience to help customers leverage their investment. Our partners can also perform load balancing tests which can help you figure out what kind of hardware your company will require for it's JIRA instance. If you are interested in procuring a partner for any professional services please let me know and I'll get out Partner team to send you a list of local partners that we recommend. We also have a partner who has applied MultiSite and Clustering to JIRA - you can find out more here 3. Multiple JIRA Licenses/Instances. Although from the two example above JIRA can scale up to quite a large instance, your particular organization may not require this. Some companies find it more beneficial to have a separate JIRA instances spread through the company. The advantages of this are that there is less demand on the network and hardware and thus users will experience a faster JIRA instance. Also each instance can be customized more freely and items such as statues and resolutions can be more departmental specific. The other major advantage is not having all your eggs in the one basket. If there are several administrators then their actions may affect the whole JIRA instance rather than just one section of your company. Also, when purchasing more than one license at the same time you will qualify for our multiple purchase discount, this discounting is as follows:
This is an existing feature request, but we don't have it on the roadmap for JIRA as of yet. There are some workaround suggested in the comments, but they may break other features of JIRA - which is why we haven't been able to implement it as of yet.
The plugins installed on the demo instance include: Other suggested plugins during the demo were: Software Development specific To view the entire JIRA plugin library, broken down into categories, click here
There are 3: MS Project Import: User can import project from MS Project to the system after plug-in and portlet installation. The Jimex plugin allows to import Microsoft Project files to JIRA and adds extension of RPC JIRA plugin with useful tasks.
Some of the features shown today in the webinar are not initially enabled when you first install JIRA (i.e. issue linking, sub-tasks, time tracking, file attachments, and thumbnails for attachments, etc). Here is some documentation on turning those on.
All JIRA editions have LDAP integration, it's only JIRA Enterprise that has the LDAP configurer, which allows for a LDAP configuration via JIRA. In JIRA Professional and JIRA Standard, LDAP integration is configured by manually editing the WEB-INF/classes/osuser.xml file. The JIRA integration with LDAP is limited to password checking only, you will still need to add in your users to JIRA itself. I would suggest that if you want to integrate JIRA with your LDAP repository and also save you from having to set up users and groups in JIRA you should check out Atlassian Crowd. With Atlassian Crowd you can pull out your users from LDAP and assign them to groups in Crowd to be used in JIRA, all this without having to add in new usernames that already exist in your LDAP. You can see this here.
You can import any existing issues using our CSV Importer. Additionally, we have custom importers for Bugzilla, Mantis, and FogBugz. Additionally, we have some third-party scripts, suggestions for writing Jelly scripts and for RPC services to migrate your existing data here.
Yes. The JIRA add-on for HP Quality Center (JaM Plugin) allows developers in JIRA to display a list of available Quality Center test cases in a JIRA window.
Yes. See the JIRA plugin library to find existing plugins to integrate with many popular applications - including dev tools like Subversion, Eclipse, etc. Additionally, you can create your own integrations by viewing the Extending JIRA docs about creating a SOAP client, using the API, and more.
JIRA and Confluence (Atlassian's Enterprise Wiki) were designed to complement each other. If you wish to see how well JIRA and Confluence integrates together you may do so by reading the documentation We also have a great short overview video on the JIRA Evaluator Resources space (on the left under Useful Videos).
JIRA can be configured to automatically create issues or comments based on incoming emails. This is especially useful in a helpdesk or support scenario, where users send support queries via email, which you wish to track with JIRA. Subsequent emails about the issue, for example responses to Email Notifications, can be automatically recorded as comments. Additionally, any attachments in the emails can be automatically attached to the issue (with appropriate configuration). You will also need to first configure your SMTP server so that JIRA can send out emails. We have a short video of this here in two formats: avi and m4v. Additionally, there is an Advanced Mail Handler plugin which allows users to define many fields of the newly created issue (reporter, project key, type, priority, affected components, etc.) directly in the body of the email message, as well as an Extendable Mail Handler that takes the standard CreateOrComment handler and adds several enhancements. Finally, Pix Software has created another email handler that allows the user to select the project, issue type, priority, component, version, security level and assignee. It also works with custom fields and it supports localized issue type and priority names.
JIRA Suite Utilities - including a Transitions Summary Tab Panel: It shows the total duration of each executed transition, whichever times was executed, who and when was the last time that executed it.
Atlassian offers three training packages for JIRA. This training is designed to help you and your team get started and use JIRA successfully. The three training modules are: * JIRA Fundamentals If you or your colleagues are interested in any of these you can find out more details on the training home page. Purchasing training at the same time as a JIRA license will also give you a bundled discount. If you are interested in our discounting on multiple products purchased at the same time, this discounting is as follows: * 2 licenses = 10% discount This includes cross product licenses as well as pre-paid maintenance and any of our training products. You can purchase maintenance up to 3 years in advance. Please note that this does not include any of our hosted products.
Atlassian JIRA has over 12,000 customers. The current sample of JIRA customers can be found here. You may also be interested in our public JIRA testimonials. Also our case studies give you a good insight as to how other organisations use JIRA.
Atlassian has a range of local partners equipped to assist you with implementing and customizing your JIRA instance. You can browse their services listing here. Feel free to contact any suitable partners directly, or if you would like a recommendation then just forward your requirements to partners@atlassian.com and our business development manager will respond to you shortly.
You can contact me via this email address or call me directly during local business hours in: Thanks for attending my JIRA webinar! Christina |
