Usage FAQ

1. How do issue dependencies work in JIRA?

There is the 'subtasks closed' workflow condition which prohibits users from transitioning an issue which has 'open' subtasks.

Another basic implementation of issue dependencies can be configured via issue linking. You can configure any types of links that you'd like - blockers, duplicates, etc. However, there is no way to set up a functional dependency (i.e. blocker) between two parent issues in JIRA.

If you would like to build this functionality, you can use the conditions within a workflow to build dependencies. You can use the condition skeleton to create new custom workflow conditions.
 

2. How do I track time in JIRA?

When you log work on an issue, you:

1. Log the time you have spent, in weeks/days/hours/minutes (you can use fractions if you wish, e.g. '5.5h').
2. Enter a description of the work you have done
3. Adjust the 'Remaining Estimate' (i.e. the remaining amount of time you think the issue will take to resolve)

You can only log work on an issue if the JIRA administrator has enabled time tracking, and if you have the permission to 'log work' in the project to which the issue belongs.

3. Can I assign issues to multiple users or groups?

Currently it's not possible to have issues assigned to more than one user with JIRA, as JIRA is designed to manage accountability so issues don't fall through the cracks. The thought is that either a team lead or manager will assign issues out to individuals, or your users will pick from a list of issues that they have the option to take on. When you create or edit a project, you have the option to have the 'default assignee' be either 'Project Lead' or 'Unassigned'. However, you'll need to be sure that 'Allow unassigned issues' is set to ON in your settings under Administration > Global Settings > General Configuration.

In the situation where you'll have a group of users picking from a list which issues they'll work on, you can set those issues up to be Unassigned, then give your users a filter on their dashboard showing them the issues they can take or add that group to the notifications so they get an email that a new issue is available for them to take. See the Defining a Project for more details.

Another option is to add a multi-user picker custom field called 'cc' or something similar, and add the users in that custom field to your notifications. 

4. How do I request an RFI or RFP?

Atlassian is a little different than many software companies when it comes to how we sell our software. Our key desire is to build incredible software and make it as accessible as possible by keeping the pricing low. And one of the ways we accomplish this is by relying on a different sales model.

We do not have a traditional sales force who would normally be available to complete RFIs and RFPs. However, for those of you who do need some RFI/RFP help in your sales process, we have gathered and published the top RFI/RFP questions in a MS Word document, which you can download here.

Can't find what you're looking for? Find one of our Experts who can help you in our Expert Directory. Atlassian will be glad to offer you a direct referral as well. Just tell us what you need!

5. Where can I learn more?

The full, searchable JIRA documentation is located here.

6. How is Atlassian evaluated in the ALM landscape/market?

In Gartner's most recent Magic Quadrant for Application Life Cycle Management, Gartner placed Atlassian in the Leaders quadrant. Click here to read the full report.

This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Atlassian.

Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.